I had posted a note a week ago about memory problems with Poser 4.. and I never did get it fixed.. for example, I tried to load a pz3 this morning and 20mins later it still hadnt loaded and my system was completely out of memory.. considering that I had 512 MB of RAM, it shouldnt happen.. So I backed up the directory and installed P4 in a new directory and tried to open the same file, it loaded perfectly with no problems... now, before I install the patch and start moving files back in, has anyone had a problem similar to this? I dont want to move something in that will cause the problem anew.. Also, what was happening was that if a texture map was not found, all I got was an error message, though with the new install, it actually pops up a dialog so that you can specify the location of the map... is this a result of the patch? Hoping someone out there has an answer :) Thanks Darrin

Hmmm, by making some complex scenes I had the same problem - especially with the texture-maps -. My quick solution for not-being-nerved with many many popups to define the texture-location was simply to give Poser exact the name of the texture but using a smaller texture for that ... I found out that it seems to depend on the texture-maps (if you use many, it will increase the need of RAM in an enormous way. Another problem seems to be that Poser can't flush the memory - so if you're planing to load a really big scene (>70 MBye) it is wise to close poser - wait until win386.swp (I don't know the Mac-Synonim) is at a normal size and then restart poser again and loading the scene ... I know this isn't exactly the problem you had - but maybe it'll help ...

not sure which file windows 2000 uses as virtual memory file, but I did notice via the task manager, when I had loaded this scene the poser process was taking up about 350 MB, but when I loaded it with the fresh install, it only took 90 MB... so it has to be something with the file versions or a corrupt dll or plugin..

sounds crazy - are you sure ??? Forget it - of course you are sure - Couldn't explain it ... Sorry

hehehehe yeah, I thought it was pretty crazy too, but at least I have it working correctly now... I will gradually up date the directory with all my other backed up files after I do the patch, and hopefully I can trace it down.. thanks :)

Darhorn, Just my two cents. I've found that the bigger the texture files, the slower Poser loads models. Even have had it lock up on really big ones. The large texture maps are nice, quality wise,but I usually try to keep mine at 1000x1000. If I render in a different program, I use the bigger ones. Especially for closeups. hdrider

Darhorn in my experience Poser is a memory hog and releases it like a miser parting with a coin. I often find that when trying our different textures it soaks up the memory. However, I have found one free utility (Maxmem) that frees up memory most of the time and stops me having to restart the system. Go here: http://www.analogx.com/contents/download/system/maxmem.htm It seems to work for me most of the time. STORM

One thing I do is 1) Save a lot before rendering and 2) Shut poser down if I've been playing with texture maps. I shut it down and then load the biggest memory hog of a program I can think of, usually "mame" running Mortal Kombat. (emulators eat memory like crazy). Then when I go back to poser, the memory is cleared up properly and extra tex maps are no longer in memory or in the pz3. Frustrating nonetheless. -Darth

I've had similar problems, although never quite that extreme. I usually do what Darth does (except for the mame/Mortal Kombat bit grin) and the problem is resolved. It's down to Poser's reluctance to release memory once its got hold of it. Storm, thanks for the URL - that's a programme that's been mentioned before but I've never managed to find it. Thank you Paul

You're welcome Paul. It is not perfect but it often comes in handy at crucial times when I want to punch Poser in its mighty memory gut! STORM