Well, maybe in a few months time Win XP will solve all our problems... Have you ever considered taking out one of the RAM modules, and run your system with 'only' one Gig? I think 98/98SE/ME CAN handle that amount of memory and it sure knows how to deal with AGP/openGL cards. I know you probably want to keep all the RAM, but that seems to be the main problem at this moment. Maybe try it until Win XP becomes available? You would at least be able te run a decent OS on what is still a 'killer machine'. I'm using a system with only 640Mb, and it does everything I want it to do, without any memory problems. I know it's a big step, but just think it over...

He, I'm glad something works for you. It isn't the most elegant solution for working with Poser, but at least you have a temporary workaround. I do the same thing: I pose in Poser, and I don't even render anymore; I just export as an .obj and do the rendering in Bryce. I hope Max won't be giving you to much trouble.

He Gabe, Yes, you're right: only Win2K is designed to handle such large amounts of RAM. That's one of the 'drawbacks' of RAM becoming so cheap... we can buy al lot of it. :-) So basically you're stuck with 2K. So... back to basics. I take it you've tried to reinstall Poser already? Then: have you already tried making your pose with non-textured figures, and apply the texture only at the very last minute? I would really like to know if that makes any difference.

Gabe, Why don't you simply create a multiboot for Win2K/ME? From what I understand, ME gave you less problems with Poser, so try making your scene under ME, and then export it all to Max. But you DO have a weird problem. Most people have a more stable Poser with Win2K then with 98/ME. I take it that you run Max without any problems with Win2K? And what aperture size do you use for your AGP card? (I have it set to 128Mb and I have no problems at all. (Just a GeForce with 98SE))

Hi Gabe, Looks to me like you are having more serious problems then most of us do. For most people Poser freezes when they try to render a hi-rez scene. You could try to pose/morph your figure and apply the textures only at the last minute before you try to render... Or you could skip rendering in Poser all together and export your figure to an other program like Bryce. (BTW... 1536Megs...? :-)

I agree with you on both issues. I only have NOA (for now...), and it IS a wonderfull texture. And as for CL addressing this problem... it should be on top of their list. (Dunno if it is, but it should be.) Like you said yourself: you can get 1 or 2 renders out of Poser before it freezes, so you could try that aproach. Pose a lot and render a little. You could also try downsizing the texture maps. (I know: not really an option :-) Or make a pose, and import it in Bryce. The lighting in Bryce is better anyway.

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=341853

A few days ago I saw Poser eat up about 400 megs when I did a close-up with the Noa tex and a bumb map. But after the render, Poser returned everything to the OS. The second render I tried just froze, and Poser had only used about 140 megs at that moment. I just don't like having to save those pz3 files, just because Poser is about to freeze. And then having to quit Poser and restarting it, just so it can freeze again after 2 or 3 renders.

So we can eliminate quite a few things here: a) It's not a particular version of Poser. b) It doesn't really matter how much RAM there is in your system. c) The size of the texture doesn't matter (I'm still not to shure about that one, but OK...) And furthermore: I am running MemTurbo, and I can see Poser returning almost every Mb of RAM to the OS after it has finished rendering, so: d) It's also not a question of Windows running low on system resources. OK, it's a bug in Poser. :-(

Hmmm... and I was almost sure about that RAM thing. But than what? Is it only a specific version of Poser? Does the Pro Pack lock up as well, or is it just version 4.0.3? Or are the lock-ups caused by the large textures we are using now. I do get the lock-ups when I'm working with the Noa texture (3000x3000?). And that is about the only texture I am working with these days. Still trying to find a reason why...