- Posts: 7
- Thank you received: 0
Time Estimator
14 years 9 months ago #1428
by avicohen2k
Time Estimator was created by avicohen2k
OMG - I just wrote a long feature idea and at the end it said I was logged out! cant believe it.
anyway, I'll make it short. my first post was filled with nice remarks and funny quotes - this is going to be to the point (sorry for spelling too)
-It is hard in general to get an estimate on how long a render will take.
-with SR there are quality changes being made that you don't know of.
-the estimate you get is for each pass and the final render. each are separate and not that good.
implementation?
calculate render time button - simulates 5-10% of random buckets of all passes and render (yes it will take a while but if your going to get stuck with a really long render you should know it before you start!).
at the end gives a report of how long each step will take and a total estimate.
SR gives you the best reasualts for less time, but sometimes you have really little time and you need to know really fast whats the best reaslt you can get with the time you currently have.
Thoughs, wise developer ?
Avi.
anyway, I'll make it short. my first post was filled with nice remarks and funny quotes - this is going to be to the point (sorry for spelling too)
-It is hard in general to get an estimate on how long a render will take.
-with SR there are quality changes being made that you don't know of.
-the estimate you get is for each pass and the final render. each are separate and not that good.
implementation?
calculate render time button - simulates 5-10% of random buckets of all passes and render (yes it will take a while but if your going to get stuck with a really long render you should know it before you start!).
at the end gives a report of how long each step will take and a total estimate.
SR gives you the best reasualts for less time, but sometimes you have really little time and you need to know really fast whats the best reaslt you can get with the time you currently have.
Thoughs, wise developer ?
Avi.
Please Log in or Create an account to join the conversation.
14 years 9 months ago #1430
by subburb
Replied by subburb on topic Re:Time Estimator
here's a nice idea !
but... i've tried many things to have a decent setimation, with no luck for instance.
your idea is nice, i'll think about it deeper.
it' not possible technically to render only 10% of a pic, Vray doesn't permit that.
but i can make a preview render and try to make an estimation... but it will not be really precise..
a brushed metal can take huge time on ultra settings, and takes 1 second in preview... not so evident..
but, as you said, i'll have a try. but i prefer not implement that kind of tool if result is too much average.
to have an "idea" of the time estimate fo your render, you can use the following rules :
each quality level time (except preview an draft) = lower level time * 1.5 with default SR presets.
For example, a render wich takes 60s in medium will take 90s in good, 135s in very good, 203s in prod, and so on.
if preview if you referential, then :
preview = x
low = 5 * x
medium = 6.5 * x
good = 10 * x
verygood = 16 * x
prod = 24 * x
ultra = 36 * x
i'll try to make an algorithm for that, but i'm sure that the prediction will be really average : render time estimation and ratio between quality / render size may vary a LOT depending of the scene and materials used...
for example, when you double the resolution, sometimes the render is 1.5 longuer, sometimes 3 times longer, depending of the scene/materials, SR optimisations....
but... i've tried many things to have a decent setimation, with no luck for instance.
your idea is nice, i'll think about it deeper.
it' not possible technically to render only 10% of a pic, Vray doesn't permit that.
but i can make a preview render and try to make an estimation... but it will not be really precise..
a brushed metal can take huge time on ultra settings, and takes 1 second in preview... not so evident..
but, as you said, i'll have a try. but i prefer not implement that kind of tool if result is too much average.
to have an "idea" of the time estimate fo your render, you can use the following rules :
each quality level time (except preview an draft) = lower level time * 1.5 with default SR presets.
For example, a render wich takes 60s in medium will take 90s in good, 135s in very good, 203s in prod, and so on.
if preview if you referential, then :
preview = x
low = 5 * x
medium = 6.5 * x
good = 10 * x
verygood = 16 * x
prod = 24 * x
ultra = 36 * x
i'll try to make an algorithm for that, but i'm sure that the prediction will be really average : render time estimation and ratio between quality / render size may vary a LOT depending of the scene and materials used...
for example, when you double the resolution, sometimes the render is 1.5 longuer, sometimes 3 times longer, depending of the scene/materials, SR optimisations....
Please Log in or Create an account to join the conversation.
14 years 9 months ago #1431
by avicohen2k
Replied by avicohen2k on topic Re:Time Estimator
I'm glad you liked the idea. of course I didn't know you can render random buckets. maybe thats something to wright chaose on the next release?
its logical that if you can't randomize the buckets and render 10% on the original then your in the rough.. Ive noticed that a complex material from far away would take a sec in low res since vray is ignoring allot of its attributes (which is good because you don't see it anyway), but when you size it up then the details come to eye and its not so linear..
anyway, a rough estimate could still be nice, although that wasn't what I was aiming, even knowing if your going to have a 2-4 hour render or a 4-6 hour render is a big different wouldn't you say?
you might think again about a few unnecessary elements you could have dropped to gain an hour or so.. you can add a "fools hope" title to the estimate message window
subburb wrote:
Thanks didn't know that.
its logical that if you can't randomize the buckets and render 10% on the original then your in the rough.. Ive noticed that a complex material from far away would take a sec in low res since vray is ignoring allot of its attributes (which is good because you don't see it anyway), but when you size it up then the details come to eye and its not so linear..
anyway, a rough estimate could still be nice, although that wasn't what I was aiming, even knowing if your going to have a 2-4 hour render or a 4-6 hour render is a big different wouldn't you say?
you might think again about a few unnecessary elements you could have dropped to gain an hour or so.. you can add a "fools hope" title to the estimate message window
subburb wrote:
here's a nice idea !
each quality level time (except preview an draft) = lower level time * 1.5 with default SR presets.
For example, a render which takes 60s in medium will take 90s in good, 135s in very good, 203s in prod, and so on.
if preview if you referential, then :
preview = x
low = 5 * x
medium = 6.5 * x
good = 10 * x
verygood = 16 * x
prod = 24 * x
ultra = 36 * x
Thanks didn't know that.
Please Log in or Create an account to join the conversation.
Time to create page: 0.116 seconds
