ashley9803 opened this issue on Feb 18, 2008 · 139 posts
Tyger_purr posted Thu, 21 February 2008 at 4:08 PM
Quote - Poser 7 only divides the work of rendering once, at the start of the render; so if your scene has a bunch of complicated stuff in the top right corner (e.g.) then it will behave like this. Three cores will drop to idle and 3/4 of your uber quad core processor will sit there and do nothing, while the remainder gimps along on one core until it finishes (which might be hours). I talked to EF about this shortly after Poser 7 was released and they acknowledged it, and told me no change is planned there until "the next version of Poser", but I expect that will not include the upcoming "Pro" version - certainly it isn't enough to get me to buy it, even if it does make it in.
edit: and comparing to other renderers out there, none of the "big dogs" has such a stupid implementation of multiprocessing; if you are rendering in 4 threads/4 cores, and one finishes earlier, the work is re-divided immediately to keep all 4 cores busy, as much as is practical.
well, i appreciate their incramental progress Poser is making, even if it isn't "fast enough" for some. I also understand they are not keeping up with the "big dogs" who have had a much more stable ownership.
I also note that the fact that Poser can divide the threads at all and the upcomming pro being able to network render, are clear signs that they have been rewriting the code necessary to get Poser where you want it to be.
My Homepage - Free stuff and Galleries