I'm going to bet that both those figures have a skin tetxure that uses the AoA SSS shaders.. I'm also willing to bet that this is happening after a save and load cycle of the scene.
I'm going to bet that both those figures have a skin tetxure that uses the AoA SSS shaders.. I'm also willing to bet that this is happening after a save and load cycle of the scene.
I see this happening when the compiled shaders get corrupted.
Did you get an error message about a shader having an invalid interface? When this happens, look in the log file for errors during the render.
When you do a render, DAZ Studio compiles shaders and optimizes images for the 3Delight render engine. These file are placed in a temporary directory. If you run two DAZ Studio windows at the same time, they can both write into the same temp directory and corrupt the data, even if you are only doing a render in one of the directories. DAZ Studio will remove these temp files when you close the window.
Running multiple DAZ Studio windows at the same time can cause this. Even if you never run more than one window at a time, when you close the DAZ Studio window, the DAZ Studio process can continue to run for some time after the window has closed. How long it runs for depends on how big the scene was loaded. A small scene with one character seem to quit very quickly on my machine. A large scene with 10-15 characters can take a minute or two for the DAZ process to quit after the window has disappeared. If I start another DAZ window before process quits from the previous window, this sometimes happens.
When this happens, save your scene and quit DAZ Studio. Use the task manager to wait for the DAZ Studio process to actually quit. Then start DAZ Studio, load the scene again and try the render. That usually fixes this for me.
Thanks all you guys. I didn't apply any shader in this scene. To add something even worse, I purchased Keshi lately and had it rendered white from start as shown in screenshot. What weird is, this white Keshi happens on MacBook Pro but appear normally on iMac (both machine are 2013 and run on Mavericks). I dedicate the machine to DAZ while rendering.
Thanks all you guys. I didn't apply any shader in this scene. To add something even worse, I purchased Keshi lately and had it rendered white from start as shown in screenshot. What weird is, this white Keshi happens on MacBook Pro but appear normally on iMac (both machine are 2013 and run on Mavericks). I dedicate the machine to DAZ while rendering.
What are the characters that rendered white in the first image. A number of the G2 F/M ones will load with the AoA shader already applied!
The runners render looks kinda cool as is.... export the png before you fix it.
To thank to you all, if you like it, I will post the final rendered in this thread today after I fix the problem. Actually the intended view is not as seen in screenshot. It was just Perspective View.
Comments
What are the differences in the surfaces, does the two white figures have a different Shader? Are there any lights in the scene?
I'm going to bet that both those figures have a skin tetxure that uses the AoA SSS shaders.. I'm also willing to bet that this is happening after a save and load cycle of the scene.
I see this happening when the compiled shaders get corrupted.
Did you get an error message about a shader having an invalid interface? When this happens, look in the log file for errors during the render.
When you do a render, DAZ Studio compiles shaders and optimizes images for the 3Delight render engine. These file are placed in a temporary directory. If you run two DAZ Studio windows at the same time, they can both write into the same temp directory and corrupt the data, even if you are only doing a render in one of the directories. DAZ Studio will remove these temp files when you close the window.
Running multiple DAZ Studio windows at the same time can cause this. Even if you never run more than one window at a time, when you close the DAZ Studio window, the DAZ Studio process can continue to run for some time after the window has closed. How long it runs for depends on how big the scene was loaded. A small scene with one character seem to quit very quickly on my machine. A large scene with 10-15 characters can take a minute or two for the DAZ process to quit after the window has disappeared. If I start another DAZ window before process quits from the previous window, this sometimes happens.
When this happens, save your scene and quit DAZ Studio. Use the task manager to wait for the DAZ Studio process to actually quit. Then start DAZ Studio, load the scene again and try the render. That usually fixes this for me.
The fix, if it is due to the AoA SubSurf shader, is to make sure each figure has a unique subsurface Group ID
Thanks all you guys. I didn't apply any shader in this scene. To add something even worse, I purchased Keshi lately and had it rendered white from start as shown in screenshot. What weird is, this white Keshi happens on MacBook Pro but appear normally on iMac (both machine are 2013 and run on Mavericks). I dedicate the machine to DAZ while rendering.
What are the characters that rendered white in the first image. A number of the G2 F/M ones will load with the AoA shader already applied!
Keshi already loads with AoA Subsurface shader.
The rendered white in the first screenshot are Michael 6 HD and Logan. I will try what you suggest, mjc1016. Thank you.
I believe both of those use it, too...
And if ALL AoA Subsurf items are rendering white, then there's a chance that it is installed incorrectly...
The runners render looks kinda cool as is.... export the png before you fix it.
To thank to you all, if you like it, I will post the final rendered in this thread today after I fix the problem. Actually the intended view is not as seen in screenshot. It was just Perspective View.
Looks like its the shoes helping him win the race..... or are those last 2 guys barefoot zombies chasing them:)
Silly question but do you Have the DAZ Studio Default Lights and Shaders content package installed? Its free with the other starter content.
I occasionally ran into the same problem.
Just save the scene and exit DS, and then restar the DS and reload the scene, the skin texture will be back.