rl sould take a look at the female athletic texture ( I tried out a few, sofar this one is a fail )
Ow and thanks for the resonders to my first post, it workt out :)
76% of original size (was 665x19) - Click to enlarge

...................................................................
My Youtube Channel

I also noticed that the daz roughness map seems to be inverted.
76% of original size (was 665x19) - Click to enlarge

I just imported hair from DAZ, but I cannot select the hair shader in CC.

76% of original size (was 665x19) - Click to enlarge

Thanks for the hint. I've thought to do that, but the error was misleading (MSVCR120.dll) and I thought if it was working before it shouldn't be that the reason and in fact it was.
Now Ia have CC3 working again.

Thaks for the tip,
Facr

Not a bug. Just poor design of merging all default and paid morphs into the same slider folders. Please read my post for examples. For the everyday user, i can see that this is great. But for a content creator, this is just bad. We can no longer distinguish between what is a default slider or a paid slider.

https://forum.reallusion.com/451721/Default-and-Paid-sliders-in-new-CC33-Update

I'm really hoping this gets addressed. Or at least we are given the option to display default only sliders and hide the paid sliders without needing to uninstall reinstall uninstall reinstall everytime we want to create something and everytime we want to use the products we have purchased for fun. I am both a "user" and a "content creator". Merging the morphs has made a huge mess and nightmare for me. And I'm sure for many other content creaters/users also.

Reallusion Marketplace Store
Content Store Featured Developer Page

76% of original size (was 665x19) - Click to enlarge

Thank you, I'll give that a go and hopefully it works. Really looking forward to using the new version and SkinGen add on

Hello I had same issue as facr73 and darth_angelus (blank area where character should be). Uninstalling / reinstalling and driver update didn't help.
Then opened NVIDIA system control and reset all 3D-settings to "factory" - default since I remembered I had done several changes on them some time ago.
After doing that CC3 seems to work (so far). Just strange that previous CC3 was running great with old NVIDIA settings.

Updated my 3.2 trial to 3.3. I get the splash and "please wait..." which never goes away. Before the update, CC3 starts in a few seconds.

I expected you guys are going to rectify FBX export with a key for editing.
Instead, you made it mode difficult.

Before, I was able to use Current Pose (after switching to Custom and selecting First Frame in T-pose), then switching back and using a Current Pose.
All you had to do is made that check box available with Current Pose Selected. 
But now that check box is reset when switching back to Current Pose.

Most of the time I do not want to have a large Calibration Clip exported. And while I have my character in T-pose already all I want is to export it in that Current Pose with the key.
Or I have to use Custom Pose, browse for some pose which I do not need at all, and then check First Frame in Bind-Pose.
Does not make sense.

Bottom Line: Please make "First Frame in Bind-Pose" available for "Current Pose" FBX export.



Update: Please explain what Bind-Pose is. It seems when I take it Blender, both Pose position and Rest position are some sort of hybrid pose between A and T poses and character is above the floor.
Only at frame 60 character seems to be going to the T-pose. Why was it done?

Update: OK so I checked the manual :Whistling: - Bind-Pose is new default pose for modeling and returning character back to CC (yet to see how it's going to work out).
Still my *yellow* message is valid. We should not go through the trouble picking a pose if we do not want to use Calibration Clip.
Sometimes I do a number of going back and forth. So exporting should be plain and simple.

Good Day
I upgraded the software via the hub and started the program. The program loads and then and a second later the computer crashes and I get the Blue Screen of Death.  I updated the Nvidia Drivers and the problem reoccurs.
I am in a crucial stage of a project and I desperately need this to work