I am working on a Macintosh G4 450 with nearly 500 meg of RAM. The difficulty that I've been running into is this: I've had Poser 4 running for a year and have just recently upgraded through DAZ to V2. When I attempt to apply her new "make up poses" her I get: "Please locate V2HeadBumHi.bum" I am able to create these bumps from within Poser -- Materials -- but I find it curious that they are not included with DAZ's installer. So my rendering goes something like this: "Unable to locate bump map." Okie Dokie. "Unable to locate bump map." Yup. And so on -- ten in all. Then "Unable to allocate enough memory to Shadow Map..." (I've allocated plenty to Poser -- 300meg) and then I get a Vic with a white head and no prospects of going out dancing. Hmpfh. Am I loopy? Am I watching too much CNN? Should I revert to my good ol' Victoria the First? Any help would be much appreciated. Troy the Bruce

Eep. I wish I could help, but I've never had that problem, and I'm not on a MAC... but maybe if Vicky met a nice albino gentleman she could still go out for a night on the town! :)

Hey there ... Not sure what I did for this particular one but I know this is what I do sometimes. Load the bum map before you try to assign the mat pose. It is a pain but it sets up the .bum map. Then you can load the mat pose and it should load fine and then you can render fine. Normally.

Hi I ran into that when I had 256 mb of ram. I had to use Vram AND downsize some of the texture maps in Photoshop. If no Pshop get GraphicConverter (LemkeSoftware). I recently upped to 640 Mb RAM. And allocated 500 Mb. with a heavily morphed V2 and the fullsize bump and tex maps-that is barely enough. I would try GhostofMacbeth's idea. ALSO, Poser does NOT let go of RAM once its used it. I would do all posing-save as pz3, CLOSE poser, reopen it and THEN try your render and MAT assignments. This is a problem with Poser-that OSX will address. Good luck Eric WAlters

Eric, many Mac programs allocate memory that way, only growing, never shrinking. It helps avoid memory fragmentation, and keeps the Mac running a bit smoother and faster, at the cost of requiring more overall memory. Any memory that one program frees up will be "trapped" as an odd sized chunk of memory because other programs will have allocated chunks of memory "above" it. Please don't blame Poser ;)

Your G4 450 with nearly 500 meg of RAM may part of the problem You need at least a faster machine more ram and tons of hard disk space. I use a G4 857 with 1.5 GB of ram and 42 GB of hard dik space. Before with My IMAC Ihad that problem all the time. Also the is a plug in called poser speed bump that should help. VIcky llikes and demands lots of ram, hard disk space and the fastest processor you can afford.. She is very demanding.

Actually I run on a 7300, 180 with 305 meg of ram just fine. Can even render a couple of vicki's.

Wiz and Ghostof... That is certainly true. I meant with ONLY Poser open-do the posing etc, etc, save- then close Poser- reopen and render. I still have to do that with 640 MB of RAM-just less often. And for me. It has only been a problem with Poser-which is not to say its the only program that does that-just that it has only been problematic for ME with Poser. Ghostof... ERic Try Vicki2 with the hires Daz textures and Bump maps- throw in the Allies transcurls for good measure. Vicki2 and the Hires textures use LOTS of RAM.

Eric .. Don't have the Hi rez but I can just imagine. Didn't find much use for the high res ones to be honest since I rarely do hyper hyper close ups with is about the only time you see a difference.

Thank you... all of you. (That doesn't mean stop posting... :) I want and need all of the advice I can get from you all!) I just wanted to drop a note and let you all know how much I have appreciated your time and helpful hints. Each time I've written with a question I've been overwhelmed with good answers -- I credit this forum with making Poser fun. It's a great bunch of software, but without people like yourselves to guide me through all of the morphs, tweaks, and hidden passages, I'm afraid that it would simply be too tangled for me to navigate. Again, thank you. Troy

Got it! The answer was simply to snag a bit more RAM. I bumped my machine up to a gig of RAM and Vicki 2 renders like a dream. Thank you all again! Troy