A potential solution: from https://forum.unity.com/threads/legacy-blend-shape-normals-missing-on-modelimporter.1166324/#post-8903016
so...

public static void ForceLegacyBlendshapeNormals(ModelImporter importer)
{
    string pName = "legacyComputeAllNormalsFromSmoothingGroupsWhenMeshHasBlendShapes";
    PropertyInfo prop = importer.GetType().GetProperty(pName,
                                                        BindingFlags.Instance |
                                                        BindingFlags.NonPublic |
                                                        BindingFlags.Public);
    prop.SetValue(importer, true);
}

public static void ForceLegacyBlendshapeNormals(ModelImporter importer)
{
    string pName = "legacyComputeAllNormalsFromSmoothingGroupsWhenMeshHasBlendShapes";
    PropertyInfo prop = importer.GetType().GetProperty(pName, 
                                                        BindingFlags.Instance | 
                                                        BindingFlags.NonPublic | 
                                                        BindingFlags.Public);
    prop.SetValue(importer, true);
}

I didn't realise you could do that. (I keep forgetting about reflection)
And it seems to work, I can set all the normals to import and finally see the back of this problem.

I have a problem with wrinkles in Unity URP. Everything works nicely in the Editor outside of Playmode, but in Playmode, the wrinkles do not show. The following things do work though:
- ValueSets in WrinkleManager continue to update correctly
- headMaterial.GetVector("_WrinkleValueSet1AL") returns the correct values
- The wrinkles show correctly if I manually change values in the Inspector, e.g., on "Wrinkle Value Set 1A Left"
It's really just the the values set in "headMaterial.SetVector("_WrinkleValueSet1AL", valueSets[0]);" etc. never actually do anything in PlayMode. I have tried changing every option in the Material's advanced options, with no effect. 
What could the problem be here?

Here's a situation I'm finding myself in, but I'm not sure if there's a way for the importer to gracefully handle this. I have a few different characters who share common outfit. (A special suit that many characters wear.) The textures for the suits are identical between the different characters, but the textures are all effectively duplicated as they come into Unity.

I'm not expecting to be able to prevent those textures from being added to the project, but ideally all of the materials would use the same textures, to avoid the memory usage of duplicating the textures. I can manually drop/drop textures, but there are a lot of them, and they'll get cleared out if I ever reimport the character.

Again, I'm not really sure how the importer could cope with a situation like this, but I figured I'd mention it in case the topic had ever come up before.

On second thought, nevermind all that. I should just write my own little editor script for doing complicated things like this. I should expect the importer to handle every weird use-case I can think up.

It could be the material instancing on some build platforms. I think the inspector might be updating all instances of the material and runtime hasn't got the correct material instance.

Can you replace the Start() function in the WrinkleManger.cs script to:

void Start()
{
    updateTimer = 0f;
    CheckInit();

    if (Application.isPlaying)
    {
        SkinnedMeshRenderer smr = GetComponent<SkinnedMeshRenderer>();
        if (smr != null)
        {
            foreach(Material mat in smr.materials)
            {
                if (mat.IsKeywordEnabled("BOOLEAN_USE_WRINKLE_ON") &&
                    mat.IsKeywordEnabled("BOOLEAN_IS_HEAD_ON"))
                {
                    Debug.Log("Using runtime head material: " + mat.name);
                    headMaterial = mat;
                    break;
                }
            }
        }
    }
}

void Start()
{
    updateTimer = 0f;
    CheckInit();
    if (Application.isPlaying)
    {
        SkinnedMeshRenderer smr = GetComponent<SkinnedMeshRenderer>();
        if (smr != null)
        {
            foreach(Material mat in smr.materials)
            {
                if (mat.IsKeywordEnabled("BOOLEAN_USE_WRINKLE_ON") &&
                    mat.IsKeywordEnabled("BOOLEAN_IS_HEAD_ON"))
                {
                    Debug.Log("Using runtime head material: " + mat.name);
                    headMaterial = mat;
                    break;
                }
            }
        }
    }
}

See if that fixes it.

Brilliant, that did it!

Hello,
- Is it possible to export a character "instaLOD" version --without the original -- But import it in unity with automatic created colliders ?

70% of original size (was 720x409) - Click to enlarge

I dont want to discard the original at all cost, but it give a result file of 150-180 Mo / Per character, - with lowest textures resolution possible. And i try to decimate this.
(not looking for cloth physics, but for the embed colliders)

Thanks for help !

Yes. Press this button:

70% of original size (was 720x409) - Click to enlarge

It will add the colliders to the lod character.

Edit: But you will need to make the lod character using the Optimize and Decimate function from the Character Menu in CC4. The Instalod export just junks all the collider data but the optimize and decimate keeps it all.

Hi,
Is it worth getting the skin-gen tool in CC4 and does it work with auto-setup? I have a number of Daz characters that I import, some of the skins I've noticed loose detail, like freckles etc. They are there just a lot less "pronounce".  Adding 16+ skin layers wouldn't be great for unity I'm guessing, so I assume I'd need to flatten the materials. I assume that the export flattens materials anyway? I'm mainly worried the importer is dropping details from Daz to CC. Or is the skin details lost from the baking process ? I was also thinking I could re-add the skin effects using skin gen. or add better ones.

I assume it's not possible to export the Daz body/face Morphs?  - What I found strange was that clothes kept the ability to have morphs, but not the body. In game, I swap the exported models - I use Daz exported models if they need body morphs applied, but otherwise use CC because the characters look better.

Also, just wanted to say that this exporter is awesome and thanks for all your hard work!

The skingen layers are flattened on export, so it's safe to use for the export pipelines, and is useful for improving the details on Daz characters.

Daz details are tricky. You may need up the resolution of the baked skin textures as some Daz characters use really high res textures. The FBX exported from Daz only contains the diffuse, opacity and normal maps. If you want to include the roughness, emission and bump map details you would probably need to generate and edit an import profile that lists all the textures to be sure of baking them all.

A lot of Daz characters also have HD morphs that add extra details and mesh adjustments to the heavily subdivided mesh (which is entirely unsuitable for real time rendering performance). As the topology of the character is remapped from Daz to CC3+, all those HD morphs and blend shapes are lost. Clothing topology is unaltered which is why they can keep the morphs.

"Daz details are tricky. You may need up the resolution of the baked skin textures as some Daz characters use really high res textures. The FBX exported from Daz only contains the diffuse, opacity and normal maps. If you want to include the roughness, emission and bump map details you would probably need to generate and edit an import profile that lists all the textures to be sure of baking them all."

https://www.reallusion.com/character-creator/skingen-premium/uv-transfer.html

Could the UV transfer tool transfer the extra maps over after a bake ?