Attached are screen shots of my settings.

I have windows XP, and over 3 gig of memory.

Ahhh Yes! One of  the dreaded not enough memory  messages.

First of all to save yourself reworking things over and over, always do a File/Save before you render. Get into habbit of doing that without exception so that when you do encounter this problem all you have to do is close poser, reopen it again and then browse to your ready to render .pz3 file.

In order to get your file to render, you may have to do one, some or all of the following:

1. Check the size of the shadow map for each of your lights. Sometimes they are set high and can cause problems  with memory when rendering. If that doesn't fix it....

2.  Reduce rendering bucket size to something smaller....64, 32, 16, or even 8. If that doesn't fix it...

3,  Make parts of the scene invisible using the Heirarchy Window or the Parameter Dials Properties.  Render what is left visible. Save it as a .png file.  Hide what you just rendered and make some other things visible and render that. Save that render as a .png file.  Keep doing that until you get all parts rendered.  Open your graphic program and reassemble all of your renders into one image. If that doesn't help...

4.  Browse to the folders that contains the textures you are trying to use.  Make a copy of these texture files to keep somewhere save (because you are going to be overwriting the files in that particular texture folder in the next step). Make sure you account for the texure files for everything in your scene...hair textures, skin textures, clothing textures, prop textures.... it all adds up and eats up memory.

1. Open your graphic program. Resize each of the texture and bump map files to a maxium of 1024 pixels on the longest side.  Use "Bicubic Resampling" so that you don't blur the textures when resizing.  Click "Save" and resave the file to it's original location.

You may still have to render in pieces and lower the bucket size even after resizing the textures.

6  You can force XP to give Poser more memory (provided you have it to give). See these threads:

http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2516735

http://www.keindesign.de/stefan/poser/3gb.html

Arcadia, couldn't this message, as it suggests, also mean that it cannot find an image map - one that is only used when rendering, and not for preview, such as a displacement map?

Or does Poser check the availability of **all **image maps at the time of loading a figure/prop?

If it is due to a missing render-time image map, Phily should be able to find which figure/prop is responsible, and eventually which image map is missing, by a process of elimination.

Of course, I could well be talking through my bumsies...

 Sorry, it came out grey on white again... sorreeee!

Quote - Arcadia, couldn't this message, as it suggests, also mean that it cannot find an image map - one that is only used when rendering, and not for preview, such as a displacement map?

Or does Poser check the availability of **all **image maps at the time of loading a figure/prop?

If it is due to a missing render-time image map, Phily should be able to find which figure/prop is responsible, and eventually which image map is missing, by a process of elimination.

Of course, I could well be talking through my bumsies...

I've seen it happen when Poser "loses" something like that and can't find it.  It seems to be Poser's general "Something's Wrong And I Don't Know What To Do" error message rather than one that always correctly points to a memory issue.

If I ruled the world, a program that got itself into a state where something was wrong and it didn't know what to do would just say "AAAARRRRRGGGGGHHHH!!!".
That way no-one would be misled.

Acadia,

What is Bicubic Resampling? I have to admit all my years doing this ,and that's the first time I've ever heard the term. Is this a Photoshop specific thing?

~ Seliah

Nope. Not a Photoshop specific thing. I use Paint Shop Pro.

Resampling is basically rescaling the pixels instead of  just shrinking them down. By choosing the right Resampling option you can often eliminate or reduce the amount of image quality loss IE:  a crisp image becoming blurry or pixelated after reducing its size.  In Paint Shop Pro (probably other graphic programs too), you can choose from:

• Bicubic: Best used to enlarge a realistic or complex image or to avoid jagged edges.

• Bilinear: Best used to reduce images that have well defined edges or text.

• Pixel: Best used for drawn images or ones with well defined edges.

• Weighted: Best used if the Bilinear option doesn't work.

• Smart Size: Lets Paintshop Pro decide how to resize the image. Usually requires the image to be "sharpened" after size reduction.

NOTE: Bicubic and Bilinear resampling options can only be used on images that are 24 bit (16 million colours) and grey scale images. You can still use these on the image, but you will have to increase the colour depth of the image first by going to Image Menu --> Increase Colour Depth --> 16 million colours. Once you have resized the image you can go back to the Image Menu --> Decrease Colour Depth, and choose which option you want to use.

While each option has it's purpose, none of them will work 100% of the time. Sometimes "Smart Size" and then "Sharpening" the image works best. Other times "Bicubic" will. I find for my purposes when creating a tutorial, that I prefer to use "Smart Size" and then "Sharpen" the image afterward otherwise the text becomes unreadable and grainy. But when I'm resizing textures, I use Bicubic Resampling to prevent the pixels from blurring.

It's also possible that the OP hit the proverbial wall, in terms of how many previous textures had been loaded in. That's generally when I get such a message.

As Acadia noted, best to save and restart.

Acadia~

Thanks for the info! I use Corel Photopaint 8 and have for about 6 years now. No such animal in my app. laughs No wonder I didn't know what the heck it was! Thanks again - that was actually very informative.

Philly~

Poser 7 has a glaring HUGE memory hole. Also, when doing work for extended periods of time, if you load in a texture only to change it later, etc, it never dumps the previously (and not-in-use) textures from the memory being used to run. Even if you click File-New and start a brand new scene, all the textures that were loaded in from the previous scene are still in Poser's memory and list, thus hogging up massive amounts of memory available to Poser even before you've started work on the new scene.

Eventually Poser 7 simply runs out of memory. Only option is to save the scene (even if things in the scene have turned solid white - don't worry, just save it), shut it down, and reopen it. Yes, it's a HUGE pain in the tail due to loading times and all that, but it's the only way, in my experience, to deal with that blasted problem. LOL

~ Seliah

Acadia is right, It has to do with the size of the textures.... many of the ones that I have for v4.1 or above are over 4000x4000.  I've had this issue many many times so add the body texture on top of a huge clothes texture and crash boom bang. ;)  The bicubic thing is helpfull, gonna check that out!!! Great tip!