Hi,

I'm wondering how I'm supposed to use the generated LODs of a character with animations in Unity.
Each LOD variant on a character has its own Animator component as well as a separate Avatar.
My issue right now is that when the LOD Group component (attached to the parent game object) changes the LOD variant the current animation stops.
It seems like I would have to "manually" transfer the current information to the now activate Animator component which appears quite tedious to me.

So my question is how is this setup meant to work with animations and LOD Group?

I'm using the latest CC3 and Unity Auto Setup plugin.

Thanks,
andgeno

Hello andgeno,

Thanks, I'm looking forward to it because it's really important for my current project.

For those who get all material pink and purple. Remember to change the 
Edit -> Project settings-> Player -> Other Settings -> Color Space 
Change to "Linear"


Before


After

can you please expand on what this means?
What is a "material ball"? and how do we click on them?

Known Issue: Unity Auto Setup does not refresh materials upon completion.  One must click on the individual material balls in order to refresh the visuals.

Hello,

To be specifically, clicking on the "Materials" folder. 
You can see the difference on hair before and after the click.  (It's the LWRP template)

Hi, I like the script, it speeds things quite nicely in 2019.2 HDRP. Appreciate it a lot.

But I just want to point out this won't work in Unity HDRP 2019.3+ versions (which use HDRP versions 7.X+). Referring specially to "CC_and_IC_Auto_Setup_for_HDRP.dll" file.

It throws error upon character import: "TypeLoadException: Could not resolve type with token 01000049 (from typeref, class/assembly UnityEditor.Experimental.Rendering.HDPipeline.HDEditorUtils, Unity.RenderPipelines.HighDefinition.Editor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null)"

This is probably because the syntax in Unity HD pipeline namespacing code syntax has changed, since the Experimental status of HDRP seems to be removed.

I don't know what your code looks like, but if it's just the namespace like I suspect, it should hopefully be a quick fix to do in the code. Unfortunately I can't try it myself, as you compiled to a dll.

Most likely you have one of these bits in the code causing the error:
using UnityEngine.Experimental.Rendering.HDPipeline;
using UnityEditor.Experimental.Rendering.HDPipeline;

The syntax for them has changed to:
using UnityEngine.Rendering.HighDefinition;
using UnityEditor.Rendering.HighDefinition;

etc.

You can easily check this yourself from one of the new scripting APIs for HDPR:
https://docs.unity3d.com/Packages/com.unity.render-pipelines.high-definition@7.1/api/UnityEditor.Rendering.HighDefinition.html

Would it maybe be possible you release a Unity 2019.3+ HDRP version with a fix, to exist alongside the older versions? Alternatively, you could consider releasing the code itself, without compiling it. This way it could be easily kept up to date by the community itself.

Steelsky: This will be a perpetual problem because Unity updates so quickly with their 1000-strong development team. This can be a non-issue, though; all you have to do is set up a project in the last-working version to be your import/export stage. For example, I have set up a very simple 2019.1 project just to import and apply the auto-setup, and then I export the prefab as an .unitypackage. I can then use it in 2019.3 with no problems at all. It should work the same for you with HDRP.

---

CC3 & Daz Tricks | CC3 to Unity workflow

Hi Scyra,

Thanks for the reply. Respectfully, I know that can be done, but it is slower and messier to export between versions, with possible issues down the road. You don't want to build your pipeline around exporting and importing stuff between several Unity versions on a regular basis.

In my opinion, Reallusion updating the script to be functional with Unity's HDRP going forward into its release would be the professional and clean solution. Or like I said, releasing the script itself would accomplish the same thing, as then it would be guaranteed to be kept up to date.

Gotcha. I do see your point.

---

CC3 & Daz Tricks | CC3 to Unity workflow