Forum: Poser - OFFICIAL


Subject: Firefly render problem. What's the deal!?

heiro5 opened this issue on Jan 25, 2005 ยท 50 posts


svdl posted Wed, 26 January 2005 at 4:14 PM

Opera: You're doing animations. There is a big difference with stills. In an animation, you don't use hires texture maps and hi-poly figures, so even a system which is low on RAM can render those fine. I'm not surprised at the numbers you quote here. A hires still, with many hi-poly figs and hires textures/bumps, easily grabs 1.2 - 1.5 GB of RAM plus an equal amount of VM. Funny thing is, often the total of RAM plus VM exceeds the 2 GB limit, so I think quite a lot of VM is a copy of what's in RAM (not everything). Or maybe Poser IS compiled to use up to 3 GB. Why not completely in RAM? This has to do with the way modern multitasking OSes work. Most of the RAM gets assigned to the system cache, and whatever goes to VM is retained in the system cache and written to disk when possible, that way the application runs almost as fast as if it were completely in RAM. And now it's possible to have multiple memory hungry apps running side by side (I often have both Vue and Poser open, sometimes 3DS Max too, all with rather complicated scenes) without slowing them down too much.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff