Loading...
> >

Itirations keep resetting to 1

aedonixaedonix Posts: 30
in Daz Studio Discussion

So. I set a render off and it will progress as expected until it gets to the iteration number which I have set the denoiser to kick in. (for the sake of argument let's say that has been set to 100)

Upon reaching 100 and running denoise on that current iteration, the next iteration resets all the way back to 1 and then will continue going around and around, resetting back to 1 after each time it gets to 50.

Now I have found that sometimes I can trick Daz by switching the caustics optimization from memory to speed or visa-versa and it will progress through properly but this doesn't always work.

This new "Feature" came with Daz 4.20 and I wish I knew what was causing it, and a permanent solution to the issue. (The only other fix i have found is turning denoiser off completely which of course is not preferred)

Has anyone else been experiencing this? and does anyone have a fix or workaround to prevent all that lost render time?

Comments

  • RayDAntRayDAnt Posts: 1,135
    Are you rendering scenes close to the VRAM limit of your GPU and/or are you using CPU rendering as well?
  • aedonixaedonix Posts: 30

    I don't allow Daz to use CPU. I have that al;l turned off in the advanced settings.  As for the Vram limit. tough to say as 4.20 removed the memory usage stats from the render history window.

  • RayDAntRayDAnt Posts: 1,135
    edited April 2022

    aedonix said:

    I don't allow Daz to use CPU. I have that al;l turned off in the advanced settings.  As for the Vram limit. tough to say as 4.20 removed the memory usage stats from the render history window.

    In that case, it sounds like to me you may be experiencing the same issue as discussed in this thread. 

    In short, the AI denoiser uses a signifcant amount of vram beyond what rendering itself takes. Each time your render gets to the point of activating the denoiser, the combined memory requirements are beyond what your card has - resulting in Iray temporarily dropping the GPU from helping in the rendering process. However, since it is the only rendering device allowed under your current system config to contribute to the render, the entire render process fails and Iray retries the render again from scratch (iteration 0.) Since denoising doesn't kick in yet at that point, the retry is initially successful - up until denoising comes back online. Resutlnig in the endless loop you're seeing.

    One way to test this theory out is to temporarily renable your CPU for fallback rendering and see what happens. If I'm correct, what you should see is cpu fallback being triggered when denoising is supposed to start and denosing and/or GPU rendering either intermittently functioning or failing completely. But no reset of iteration count.

    Post edited by RayDAnt on
  • aedonixaedonix Posts: 30

    ok am trying re-enabling CPU. lets see if that helps or not. (I was always told that allowing CPU in Daz was a bad thing and should never be used.)

  • PerttiAPerttiA Posts: 10,024

    aedonix said:

    ok am trying re-enabling CPU. lets see if that helps or not. (I was always told that allowing CPU in Daz was a bad thing and should never be used.)

    Checking CPU with the GPU as rendering device may actually slow down the process due to CPU being so much slower (way much) than the GPU, but there is no reason to disable fallback to CPU in case the GPU runs out of VRAM.

    Those are two different selections and two different things. 

  • SpaciousSpacious Posts: 481

    This is a known, but not much talked about issue with the NVIDIA Iray version included in Daz Studio 4.20.  Basically if the scene you're trying to render uses close to the vRAM of your GPU, Iray will try to render on GPU, not be able to, in your case because of the denoiser, so it switches to CPU, thus causing the render iterations to reset to 1.  At that point Iray realizes that there is GPU vRAM available, so it tries to switch back to GPU, where it encounters the same problem.

    Since you seem pretty sure that the denoiser is causing the problem, why not just render without it, and use an AI denoiser on the final render?  Here's a link to a GUI for both the Intel and NVIDIA denoisers.  The GUI was made by a DAZ forum user.  The NVIDIA denoiser is the same one built in to DAZ, but i think the Intel denoiser preserves more detail.

    https://taosoft.dk/software/freeware/dnden/

  • aedonixaedonix Posts: 30

    Re-enabling CPU fallback seems to have fixed the issue.  Hopefully this issue will be addressed in the next release.

  • MILT40MILT40 Posts: 16

    It had this problem, I searched all over and I came across this thread . After reading, I followed (RayDAnt) advice to re-enabling CPU fallback and now it's fixed.Thanks all. 

Sign In or Register to comment.