|
![](/i/fill.gif) |
> I was wondering if anyone (up to and including developers) knew any way to work
> out how much CPU work/time would be needed to render an image based on its size
> and render options. It seems like it must be possible to find out.
> Thanks,
> Ross
>
>
Hardly possible.
In some cases, simply moving the camera, a light or an object by a
/tiny/ amount can make a huge difference. The same can appen with any
rotation.
Have a transparent object with any ior different than 1? Changing the
ior by 0.01 may cause a significant render time change. It may cause
tons of total internal reflections.
Use blured reflection using averaged normals? What if, in one render,
you now have some large areas with multiple inter-reflection of those
blured surfaces...
You may have a case where adding just one object cause you to exeed the
available RAM and plunge you into swapping hell.
A small, very simple scene can take ages to render, while a very
complexe and huge one can render in minutes, once the parsing is finished.
Alain
Post a reply to this message
|
![](/i/fill.gif) |