heiro5 opened this issue on Jan 25, 2005 ยท 50 posts
svdl posted Wed, 26 January 2005 at 3:11 PM
I've experienced this problem quite often. The "Adding Objects" stage for the final render seems to be the critical part. I always watch memory use when rendering in Poser (and I always save before render, rendering is the most crash-prone action in Poser!). When there are NO page faults and memory size adjustments for 2 minutes during this stage, the render has crashed, and Poser must be killed. Do it from the Processes tab on Task manager, that'll kill it instantly. End Task on the Tasks tab easily takes minutes to kill off Poser in this situation. Why does it happen? I'm not sure. It seems like the render engine goes into an infinite loop and never breaks out of it. It may have to do with the fact that the object sizes in Poser are very small compared to the object sizes in other 3D apps (I have to increase scale by a factor of 250 when I import something in Max, for instance). Firefly is not a specialized Poser render engine, it's pretty generic, and it may run into floating point rounding errors. I've mailed CL several times on this issue, but never got an answer. The weirdest thing is: sometimes a scene will not render on my P4 2.8 FSB800 with 1.5 GB RAM, crashing like you describe, and it will render fine on my AthlonXP2700+ with 1.0 GB RAM.... One thing that definitely helps: before rendering, save the scene, quit Poser, delete all .tmp files and all poserTemp.* files, then restart Poser, load the scene, and render. Sometimes I reboot the OS before restarting Poser, especially when I suspect memory pollution. It may make the difference between a crashed render and a successful render. The standard production settings are somewhat too high in most circumstances. The main culprit is maximum texture resolution. Let's take V3 for example, she usually comes with hires texture maps. If you have a V3 completely in view, she'll be about 1,000 pixels high in your final render, which means those 4000 pixels of the texture map will get compressed to 1000. So a maximum texture resolution of 1024 will not decrease the render quality, while dramatically increasing render speed and chance of succesfully finishing the render. There's a thread on maximum texture resolution here on the Poser /Poser Technical forums, can't find it right now, it can't be too old. Worth looking into. Hope this helps, Steven.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter