I've been getting program errors when rendering my animations lately. I'm on a 450mhz G4 Mac. Sometimes I get errors that I'm out of memory (even though I'm running Poser with bare minimum extensions in my Extensions folder and I have plenty of memory applied to the application). Lately I've been getting errors - and sometimes 5 frames before the end of a rendering - saying that it can't read bump map or texture map or it doesn't exist! It's driving me crazy! I'm using the version of Poser that is Poser Mac 4.0.2.117. I did use .118 for a bit, but it really has memory leak issues to the point I had to go back to .117. Can someone tell me what is going on? And can this be fixed? I'm about a month away from being finished with this big animation project for Marvel Comics and Alex Ross and I've been working on it since December and this problem has been going on and getting worse for about a month. Anyone who can help me has my thanks forever!

How much RAM do you have, and how much is allocated to Poser? It is possible to have too much RAM allocated to an application. You should have at least 3 - 5 MB free for system overhead while an application is running. Other than that, I can't think of anything. I've done some long Poser animations, and a 3 day Bryce animation render on my G4/450 with no trouble. -sk

I have 100826k assigned to it at the moment. I have had as much as 120826k. You are right about it going ahead and rendering anyway ... but not for me lately. When it says it's done due to error, it's done. Before you laugh at me and my memory allocation, it has not been an issue in the past ... only in the last month or so. The suggested size is 64145k, but that will immediately get me not enough memory errors. 120826k seemed a goodly excessive amount, but it wasn't an issue on my 350mhz OS 8 G3. It's an issue on my 450mhz OS9 G4. I'm rendering out animations that range from 300 to 600 frames each and sometimes with a couple characters in it, FYI.

The solution I have seen fo this was to just restrt rendering the animation where it died. As long as you are rending seperate frames it should work. I though they had killed this bug, actually.

I've gotten that message. I'm on a PowerTowerPro 225 (mac clone) 320 K RAM. Fireworks and Dreamweaver usually leak memory, and if I run Poser after using either app, I get the error message you describe when I try to render in Poser. I use high res shadow maps, usually 1024+, render images at least 800 x 800 and give Poser at least 200 K of RAM. My guess is the usual Mac presciption: more RAM. --ratta

Poser has had a problem with animation renders with BUMP since Poser3. Another problem is that if the program crashes during a animation render you loose everything, as far as I know Poser does NOT put a EOF marker after each frame rendered. Even in Full frame uncompressed the image quality is marginal. Here is what I currently do: Render to Image files, the quality is better and if the program crashes you can just pick after the last image rendered. Then assemble all the images and compress etc. I have not tried to render an AVI or MOV in Poser in a long time, I find the Image file render to work the best and have the least amount of problems. The resulting Movie is much clearer with Image files. I am on a PC PIII 800 384ram 28gigHD WIN95 OSR2.5 and WinNT SP5 Hope this helps Paul Hafeli