I've experienced the same issue.
The way I resolved it was to uninstall CC3, and reinstall it via Reallusion Hub.
I doubt if the update file v3.2 does not include the other required component updates for pipeline extension or iray render plug-in.

First of all I applaud RL for the latest updates and a headshot generator. Job well done guys!

I have a little chance to play with the everything.
Thus far I have one complain about linked media.
So the question: Why are we going back to IC6 era?
I am sure it was asked during beta, but can someone tell me why we have linked media for Digital Shaders?

If you tell me that is because embedding those large images into the project is not practical, I will not take it as an answer.

There are dozen files linked to the character Digital Shader for different parts of the body.
It would be a pain going through each and every one of the them and clicking embed, If I would want to do it.

Aside from that, there are plenty of room for optimization.
Take a look at that monster Micro normal map for body. A whooping 24 Mb PNG file!
Of course If I embed that to every character (even given that it would be linked for each body part), it would be a huge waste or disk and project space.
It is highly impractical to store normal map of this type in PNG format anyway.

I converted Micro normal map to 70% compressed JPEG format and the size of it now is 1.3 Mb
Below I compare the two - one is 24 Mb PNG and another 1.3 Mb JPEG with 200% zoom (no one ever going to observe the skin that close anyway). But can you tell me which is which?
(screenshot itself is 32 bit PNG so there is no quality loss).




I believe other texture files in that shader folder could be optimized and embedded as well.
This is also problem for developers where shared media on the client might be stored in different path.

Problems above need to be addressed in the next update IMO.

The one on the right is clearly compressed! (sorry)

It is strange about the Micro Normal — if you save out the texture it is only 7.45 MB, which is closer to what you would expect from a 2K PNG. Comparing it to the embedded file....ohhh, I see...it's 48-bit instead of 32-bit. That really is unnecessary.

---

CC3 & Daz Tricks | CC3 to Unity workflow

The one on the right is clearly compressed! (sorry)

lol fine, but can you honestly tell the difference when it is applied?

BTW it is 64 bit! Damn!

A mouth ambient occlusion - a TGA 4mb file.... Really?

Well, I'm kind of messing with you...I am unusually perceptive for these kind of differences. The darkest blue color represents how deep the normal cuts into the mesh, and I see that the compressed one would result in a more shallow cut. But when saving a Photoshop JPEG at setting 10 (of 12 — Maximum), I can't tell the difference, and it results in a 1.17 MB file.

---

CC3 & Daz Tricks | CC3 to Unity workflow

I am unusually perceptive for these kind of differences.

I thought I was

But my bad, the jpeg file was 1.03 after 70% saving for web (which I usually do not do) and with  level 10 is 1.17 Mb - totally acceptable.
They should go through the whole folder now, optimise and embed texture.

The eye whites were black  when CC3 opened after the initial install, but not so once I fixed the resolution issues and reinstalled the third time.

For anyone that had the same issues as I had and are trying the same fix I posted on the first page of this thread, after I set my resolution back to the default state everything, (as in web pages, explorer windows, ect.) were still displaying out of sync, ie: still to large for the screen. 

To fix this I went into windows display settings and reset the default settings to 125%, then back to the default 150%, and everything came back to normal.



Dell XPS 8900, Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408 Mhz, 4 Core(s), 8 Logical Processor(s), 16 GB RAM, - 4 GB GeForce GTX 745, NVIDIA compatible.
Acer Aspire V Nitro Laptop,  2.5GHz Intel Core i5-7300HQ processor with 6MB cache,  256GB solid state drive, 16GB Ram,  4 GB NVIDIA GeForce GTX 1050 Ti graphics.

Webp support would be optimal in this regard!

I would think 24-bits is enough, because you don't need the alpha channel.

---