A bug that new users may not know and impacts the quality of rendering large scenes with cpu

soulofthesword_88604559d2

This may be just a issue I have, but I just figured this out after spending 2 weeks trying to get my pc to finish a decent render with scenery. the setting for how many seconds defaults to 7200 seconds. this is 2hours if you do the math. I saw a video were the person said this was 10 hours so this bug took me a longer to discover then it could have. but if daz hits you min passes, or min % of coverage to canvas it will stop and kick up the save file interface..... however, my daz will not stop at 2 hours. It WILL stop making new passses and improveing the image, but will not close the interface or bring up the save dialog while also continuing to count how long its been working even tho it stopped working a long time ago.

I had so many crappy 10 hour+ render that look like poop because they actually stopped at 2 hours. I did not realize this until it occurred to me that I get about 300 passes an hour on a large scene, but always seem to have 600-700 passes when I cancel 10 hours latter. I do not know it this is an issue for everyone, but on a low end rig you need the time. MY last render, first after realizing this and upping my time  to 4.5 hours I ended at 1500 passes with denoizing starting at 1400 passes and looks amazing.

Hopes this helps another new user.

Richard Haseltine

Stopping for time, when I set the max to 10 seconds as a test, worked for me.