Ghostofmacbeth opened this issue on May 27, 2007 · 20 posts
pjz99 posted Mon, 28 May 2007 at 1:56 AM
I think I should explain the remark I made about Poser 7's renderer not being too well designed in this sense, as I wasn't really too clear.
In the case of the higher end renderers, like Mental Ray (3ds Max, Maya), or Vue's engine, rendering is broken up into multiple threads in a very piecemeal way that keeps all cores as busy as possible - which is good, this is what you want. You press the Render button, and all your cores become very busy - ideally, 100%, but at least they are all doing something as long as the render is running.
In the case of Poser 7, when you press the render button, the task is broken up into 2, 3, or 4 separate sub-tasks, and rendered in a separate thread. Assume you have a quad core processor, and you've set Poser 7 to render in four threads. This isn't too great when you have a lot of very complex stuff (e.g. reflection of high quality) in the top left corner of the frame, and much easy stuff on the other three cornders of the frame - what happens is, the easy stuff all finishes very quickly. The top left corner takes "a long time" because much more math is required to calculate the reflections. You render is not complete and cannot be saved to file until the whole image is complete. Meanwhile, 3/4 of your processor capacity sits there doing nothing. Very annoying, should have been implemented smarter.