I am running Win98 w/256M ram and having problems with the DAZ3d MAT files for Victoria 2. Everything seems to work well until I try to render the image and the program goes off to 'la-la land'. Doesn't say 'Not Responding'. Just not doing anything either - even 12 hours later. DAZ tells me it's my system. Take the images and reduce the resolution until it works. When I originally talked with them about this the tech said I need 256M, I told him that I had that... (sigh) Now they just are saying "Sorry. Check with the forums and see what other people have done to fix the problem." They admit that it does happen but don't know why. (sigh) Anyone have constructive thigns I should try? I've reloaded my system and that didn't fix it either. As long as I don't use the MAT files all works well. THANKS!!

I have the same problem. There are 2 options: 1. Use another render engine, like Bryce or Vue, 2. change the OS to Win2000. The reason is the combination of Poser and Win9x/Me. Poser has some nasty memory habits, and the consumer OS of M$ dosent reclaim lost RAM.

Hrm.. Yes, I suspect that changing my OS would help. Win2000 is a very stable platform. But does spending several hundred dollars to fix a problem that I 'assume' some people have working with Win98 ( anyone out there that DOES? )seems a bit excessive. As for a different rendering engine. I do have Bryce1-4 and thinking of getting 5... but it SHOULD work on my system as 'sold' to me. Again, throwing money at it, or working with something not designed for Poser is costly also - in time/effort. (sigh) If it takes Win2000 or something other then Poser to use Daz's MAT files they should say that. Then I wouldn't have bought it. Instead I have to try to get support from the people that didn't get money for the product I purchased in good faith. If more memory would fix it. THAT's cheaper then a new OS. Grr. Thanks for the options. I don't like them, but they may be my only choice. Anyone else??

Now, I am swell with Poser, and anything it can toss my way on Windows ME....but, Bryce, on the other hand does the "hang up dance" alot. It does help to shut down your system....for at least 2 minutes...Don't ask me why, but simply restarting does not necessarily clear out the M$ mem bugs. Then, save often...and reboot, often, as well. But, remember Poppi's 2 minute rule on shutting down. Hope this helps.

The only thing that I've had work is to turn off letting WINDOWS ME automatically set the virtual memory settings. I have a PIII 800 with 448 megs RAM and have the same problem. I went into system properties, clicked the performance tab, advanced settings, and turned off "Let Windows manage my virtual memory settings". I have about six gigs free on my C: drive (which is where POSER is located) I set the minumum to 2000 which is 2 gigs and I set the maximum to 4000 which is 4 gigs. I'm trying to free up more disk space to make it it even bigger.

Lower the resolution of the testures a little would be another solution ... Unless you are doing closeups then it mostly won't affect the final look ...

Sometimes the problem occurs when you use the MAT files meant for the Pro Pack on a Poser4.x intallation. The Mat file will apply a JPEG into the bump or texture channel and Poser4.0x can't handle that. -Jeff

Well... We have a WINNER!!! ( mostly, kinda, sorta ) I've changed the virtual memory to a 1Gig allocated section of my Ddrive and that allowed me to render the HIRES versions of the MAT files for Victoria2. The MW Updo hair still want to make it go off to la-la land - BUT we are making progress. I'll expand the Memory allocation and give that a try. It would be nice to have that working also. I'll let you know what I find out. Thanks for the comments/suggestions. If anyone else has more please feel free. I do desktop support for a living and don't mind hacking on things in the system - if there is a good chance that it might fix things. THANKYOUTHANKYOUTHANKYOU!!!! Special thanks for namja1955 for the VMM 'point in the right direction' .. perhaps PUSH, not point? Aahzimandious

If you have your puter partitioned try setting the virtual memory in a diff drive. I have C, D, and E. I set my virtual memory to my E drive rather than the C drive where the proggies are located. Not sure this will help, but its a thought. :)

Also make sure you do not have a lot of suff working in the background, I found that if you eliminate other programs you can have better luck. also make sure your sleep mode on the computer is either windows or the machine but not both...I have it switched to the machine mode and I have not had the hang up problem.

To optimize your virtual memory, change it to Fixed memory. for example 2000 - 2000. second: use the hdd-space from a different hdd (Not a different partition!!) for this. If you use only a different partition of the same drive, this do not result in better performance, but if you use a different HDD this do help. :-) and, best thing: ... use Win2K ;-) Robert

You're welcome. It was really hit or miss process for me. I've had people suggest that the problem was with a bad prop and all sorts of other things a lot of which didn't make sense. I began to suspect memory usage when I found I could use the V2 standard rez texture without a problem, but the exact same render with the hi-rez texture would lockup. (You would think that 450 megs RAM was enough, go figure.)