Daz Studio ignores Render "Advanced" Choices
Hello,
I have the latest DAZ!Studio version installed (4.9.3.166) and it works fine, so far.
I have two GTX 980Ti running and I render with the GPUs in IRAY my pictures... I set in the Render Advanced TAB under "Photoreal" that ONLY the GPUs shall render and not the CPU. This works fine for the first picture. On every continuing picture the CPU is rendering as well, even when it is not tagged. This reduces the render time a lot and seems to be an issue?! Actually I can solce this problem only by closing DAZ!Studio and starting it new. Then the first picture will be rendered again right and all following with the CPU (that isn't tagged). *sigh*
And I have another question: Isn't it possible to tell "Aux viewpoint" to render with GPU and not the CPU?
Thanks
Andreas
Comments
Reduces the render time or increases?
It sunds to me, if it's increasing the render time, as if the scene won't fit into the 6GB of RAM on the cards so it drops to CPU and then won't use the GPUs until you restart. The log file (Help>Troubleshooting>View Log) should have the messages from Iray including any out of memory reports.
The render times becomes longer when the CPU will be chosen (even when it is an i7 with 6cores at 3,300 mhz)
The scene size takes around 350 Mb and the "first" render will be done with the two gpus without problems. Then I change the camera angle or the pose and render again. Itvis the same scene. And now the render times becomes longer because the CPU renders as well but is not tagged. This happens not everytime but very often.
With the prior version of DAZ Studio I had this problem never.
Interesting ... I may have fallen foul of this and just assumed scene size exceeded VRAM, though I did wonder just how that may have happened! I'll keep an eye opne on this.
Did you leave the previous render window open? If so it will still be using RAM. Have you checked the log for the second render? It may give soem indication of what the issue is even if it isn't memory.
I will give it another try and post the log here.
It looks like as if the "OptiX Prime accelaration" is creating this problem!
Any idea what to do? Or shall I untag "OptiX Prime accelaration" forever?
The latest drivers by nvidia for the graphic cards are installed.
I gave my PC much more data for rendering today and "Optix" had no problem with it. So, a memory problem it can't be, or?
When I rendered it now a second time, the issue shows up: