- Mon Jun 20, 2005 12:17 am
#36228
Based on my experience so far, 15 is what most people stop at... most of the clean renders seem to be 14-17... so, time is cool, but a check box allowing you to enter/remove time as a rendering parameter would be cool.
At first I thought COOL I can say 20 minutes then it would render up to that point, creating the best render for a 20 minute window... however, the time spent between iterations shows no image improvement, thus stopping it anytime between 12 and 13 is no different then stopping it just after it completes 12. To me, this reduces time as a critical part of the rendering equation. In fact, I see no difference, considering the way this is set up to disable time altogether (which is what I've done by setting it to 99999minutes)
The thing that REALLY needs to be done is to show how far along an iteration is. As each iteration gets longer and longer, 50% of your time could be spent going from 17 to 18, and waiting for it to click over to 18 before stopping the render is just a plain guessing game.
Thus, I suggest, an iteration based limit with a second progress bar for each iteration. Much like bryce, which doesn't have a progress bar, but shows you in the render the progress of the iteration pass.
Just a thot.
Cheers
If we had just one lowly SuperStarDestroyer, all of earth's problems would rapidly become rather trite. I mean, who worries about war in the middle east when a 1.5km death triangle is in orbit.
- By jurX
- By Mark Bell