Hi all,

some more detail on the "memory bug" issue: when I was referring to the 2 gig limit, I meant the maximum amount of virtual & physical memory that a process can allocate on a 32 bit Windows system. You don't have to have 2 gigs of physical RAM for Poser to use 2 gigs of RAM. Setting your virtual memory to system managed while having sufficient hard drive space will do (I run 1 gig of physical RAM).
That said, if you do very heavy renders on a regular basis, 2 gigs of physical RAM will be help, because access to virtual memory is slow and it is not guaranteed that Windows will give the memory requested to an application when all physical is maxed out.
If Poser is denied more memory by the operating system, it will present the error message that I think some people call "the memory bug". I personally wouldn't call it a bug, since the alternative to presenting the error message and stopping the render would be freezing or crashing.
If you want to know for sure whether or not you're trying to render a heavy scene, you can flip a little switch in Runtime/prefs/Poser.ini. Changing 'WRITE_MEMORY_LOG 0' to 'WRITE_MEMORY_LOG 1' will make Poser 6 SR1 leave a log file behind in the location where it is installed (i.e. where the 'Runtime' folder is located). The log file will present you a detailed listing of memory available at the start of a render and how much memory is needed for loading textures.

Uli

P.S.: XENOPHONZ, yes, I work for e frontier. Sorry for camouflaging.

Message edited on: 05/27/2005 12:36