Loading...
> >

Huge difference of Renders (time and quality) with the same render settings.

ChettChett Posts: 0
in Daz Studio Discussion

The following scenario happens a lot to me. Maybe someone can enlighten me here. 

Render Settings: Full HD 1080p

300 Iterations, Denoiser kicks in at 250. Rest is default. (Its a 5 sec. animation)

 

I rendered Pic. 1 (Showcase1) in ~ 80 seconds. Quality is top, everything is fine. (which is not the case 99% of the time, next Pic (showcase2) is what i get normally, when i dont reboot every 30 Minutes!)

Then i decided to move the Sailboat on the left a lil bit more in and rotatet it slightly. Thats all i did.

Then i rendered Pic2 (Showcase2) in  !!! ~ 7 minutes !!!. Quality is trash. Lot of red dots all over the place. Look at the Sail. First Pic - very smooth. Second Pic - meh!

That all happened inbetween 10 minutes, no other actions were taken.

 

Then i booted my Computer, cuz i realized, that DAZ messes up thing of various types and its always a good idea to boot, to (maybe) get rid of errors.

I rendered Pic3 ( ~ 80 sec.) which i do not upload, and it has the Quality of Pic1. All is smooth, everything is fine.

 

As i mentioned, the Scene is a 5 sec. animation, all 3 pics were taken as "still images". To look how the result is going to be, before rendering for hours.

 

Pic1 and Pic3 (the good ones) look like Pic2 (red dots and bad quality) before Denoiser kicks in. So i guess the Denoiser is buggy?

But what i dont understand is the huge difference in render time. 7 Minutes and a bad result, compared to 80 seconds and a good result.

What is going on here? 

 

 

 

 

 

 

Showcase1.png
1920 x 1080 - 3M
Showcase2.png
1920 x 1080 - 3M

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,217

    Longer render and no denoiser sounds as if the second render had dropped to CPU. The log file (Help>Troubleshooting>View Log File) will tell you which devices were used, and how many iterations each carried out.

  • ChettChett Posts: 0

    OK, i have CPU off, only the "Fallback to CPU" is on. I try and turn it off, to see, if it fixes my issue. Rebooting every 30 minutes sucks.

  • Saxa -- SDSaxa -- SD Posts: 872

    Sounds like you need at least 2x the memory. DS uses a pile of memory and to reset you need to exit/relaunch DS.  Disabling fallback to CPU is most likely in your case is likely not gonna help.  Unless Daz chnaged the code or your system works different than mine.  Close DS and reluanch is only option that works well.  Same for Hexagon and some sclupting functions.

Sign In or Register to comment.