What causes white skin renders?

ScavengerScavenger Posts: 2,674
edited December 1969 in The Commons

About 5 hours into an all night render (which would eventually take 11 hours total) I found one of my characters was rendering with the white skin/no texture. (3 Delight)

Far too into the process to kill it and start again, I let it finish, hoping it was just that one character and I could do a spot render to file and fix it all in photoshop. That's what turned out to be the case, but what causes the problem in the first place.

The log from 3DL has

3DL ERROR S2051: cannot load shader 'brickyard/{407f8e5c-3a9b-4708-b5e5-799ff1fe7c1d}/shader_Surface', will use 'defaultsurface'

Which is clearly where the problem is...but why does it happen?

Comments

  • srieschsriesch Posts: 4,243
    edited December 1969

    There is an issue out there, the exact cause still unknown, that causes things to be rendered white every so often, and that may be what you are seeing. You should also be able to simply exit and restart DS and re-render and it should work normally again so you haven't lost anything, it's just an annoyance. (there's also a way to clean it up without exiting I think, I haven't bothered to write it down though since the exit/restart/rerender has always worked for me.)

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    There is an issue out there, the exact cause still unknown, that causes things to be rendered white every so often, and that may be what you are seeing. You should also be able to simply exit and restart DS and re-render and it should work normally again so you haven't lost anything, it's just an annoyance. (there's also a way to clean it up without exiting I think, I haven't bothered to write it down though since the exit/restart/rerender has always worked for me.)

    Stop the render...

    Then go into the Studio Temp folder and then empty it and the brickyard folder (should be in the shaders folder inside the temp), just the files, not the folders. This will force a recompile of the shaders AND force a reoptimization of the textures. You can sometimes just clear the brickyard or the textures....but I've found that most of the time the save the scene/shut down Studio/restart is the quickest route (no having to hunt down WHERE your temp directory is...or remembering that, either, then having to drill down to the right folder). And since I save 'serious' scenes before starting a render, it's even quicker...just close Studio and restart.

  • Ken OBanionKen OBanion Posts: 1,455
    edited December 1969

    I have encountered this issue on a number of occasions, and the explanation I got was that it was a known "issue" (I've always called them "bugs") with the AoA subsurface shaders; something about a "brick" getting corrupted, which causes the whole shader to blow up -- DS doesn't know how to deal with it, so it doesn't even try.

    The solution that was suggested -- and I can attest that it works -- is exactly what Sean Riesch mentioned: save your scene, close DAZ Studio, restart, and reload the scene.

    A weapons-grade pain in the never-mind-precisely-where, I grant you, but....

  • Stryder87Stryder87 Posts: 899
    edited December 1969

    mjc1016 said:

    Then go into the Studio Temp folder and then empty it and the brickyard folder (should be in the shaders folder inside the temp), just the files, not the folders. This will force a recompile of the shaders AND force a reoptimization of the textures. You can sometimes just clear the brickyard or the textures....but I've found that most of the time the save the scene/shut down Studio/restart is the quickest route (no having to hunt down WHERE your temp directory is...or remembering that, either, then having to drill down to the right folder). And since I save 'serious' scenes before starting a render, it's even quicker...just close Studio and restart.

    I've had the same thing happen.

    Where is this Temp folder and Brickyard folder you mention? The only Temp folder I could find was in (Win7 - 64bit) C:\Users\\AppData\Roaming\DAZ 3D\Studio4. There is a Temp folder there with 4 empty subfolders and no files. I couldn't find a Brickyard folder anywhere, C:\Program Files, C:\Program Files (x86), C:\ProgramData... etc.

    I'd like to make a batch file that will clear those areas and then launch Daz just to stop that issue from happening.

  • Richard HaseltineRichard Haseltine Posts: 108,068
    edited December 1969

    C:\Users\\AppData\Roaming\DAZ 3D\Studio4\Temp\Shaders\Brickyard is the one you want, assuming you are using 4.7 (the public beta uses C:\Users\\AppData\Roaming\DAZ 3D\Studio4 Public Build).

  • Stryder87Stryder87 Posts: 899
    edited December 1969

    C:\Users\\AppData\Roaming\DAZ 3D\Studio4\Temp\Shaders\Brickyard is the one you want, assuming you are using 4.7 (the public beta uses C:\Users\\AppData\Roaming\DAZ 3D\Studio4 Public Build).

    Hmmm... I see the Shaders folder, but there's nothing in it. I wonder if that folder only populates when you start a render, then clears itself out when it's done?

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    stryder87 said:
    C:\Users\\AppData\Roaming\DAZ 3D\Studio4\Temp\Shaders\Brickyard is the one you want, assuming you are using 4.7 (the public beta uses C:\Users\\AppData\Roaming\DAZ 3D\Studio4 Public Build).

    Hmmm... I see the Shaders folder, but there's nothing in it. I wonder if that folder only populates when you start a render, then clears itself out when it's done?

    Yes, it should self-clean when Studio is shut down. And not fill up until you start to render with a shader that needs the brickyard (a ShaderMixer based one).

Sign In or Register to comment.