How to fix problem with 3Delight message #45 - Severity 2 - S2069 ?
Niki_Art
Posts: 50
Please how to fix problem with 3Delight message #45 - Severity2 - S2069 (see the attach image)? I often have a problem with this "shaders/brickyard" on different images and don´t know why it is happened and how to fix it.
DAZ3D Bug.jpg
1280 x 976 - 812K
Post edited by Niki_Art on
Comments
Please how to fix problem about 3Delight message #45 - Severity2 - S2069 (see the attach image) due rendering? I often have a problem with this "shaders/brickyard" on different images and I don´t understand what is the problem and how to fix it.
Go to your folder listed in the warning (that's a sub-folder of the Temp folder (you may need to enable the display of hidden files and folders to see it) and delete it's contents, DS wil then recompile the Shader Mixer shader.
4.9 is still doing this? :( I'm on 4.8, and was hoping this issue would be fixed by 4.9. That would give me a reason to upgrade, as this issue comes up pretty often in 4.8.
I get this quite a bit when using Genesis 2, or when I render a scene on my other computer. I've always assumed it happens because it can't find a texture or shader (in the Appdata file, I think).
You can either:
1. Reload all of the textures again.
2. Exit the program, right click on the Daz3D desktop logo and "run as administrator".
3. Restart your computer, use and use the run as administrator option again.
I don't know if anyone has a simplified way of doing it, but those are the methods that I use.
Merged duplicate threads
Hi Richard Haseltine
I have done exactly that you wrote and delete "shaders" sub-folder (no "brickyard" sub-sub-folder inside) in "temp" folder. When I then restarted DAZ3D I found "brickyard" sub-sub-folder in "shaders" sub-folder (in "temp" folder). After that I have successfully rendered problematic picture without problems. So I hope that now this issue will be removed in the future forever.
Thank you very much for your advice!
Closing DS clears the Temp folder anyway - my steps were to be applied while DS was open, as an alternative to having to close and restart. Unfortunately this is something that happens from time-to-time, so you may well encounter it again.
Thanks, Richard!
Thanks devilsatdusk15
Richard, I have found in the past that this tends to happen when opening a scene and then going staright to render before all the "Tdlmake" processes complete doing their thing in the background for a loaded scene. This is especially true with computers with lower core counts or threads available. It seems when you click render 3Delight tries to pickup the optimization and corrupts a file or two it may already be optimizing in background process heading to the brickyard folder. Waiting until these processes complete before rendering usually prevents this.
It's a problem that's been there since the Shader Mixer was first added to DS, and it doesn't matter if you're using textures or procedural shaders as it happens to both.
Richard, you're the gift that keeps giving. This problem was driving me moderately crazyish. Now it's fixed and I'll know how to deal with it next time.