Tue, Feb 18, 3:47 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Moderators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 18 2:22 am)



Subject: Can't find textures or ...


UrbanChilli ( ) posted Sat, 12 January 2008 at 2:41 PM · edited Thu, 09 January 2025 at 4:52 PM

Using Poser 6.0.3 I have a fustrating problem suddentley.
When rendering I get the message; 
"There was a problem during rendering.
You can reduce rendering memory usage by lowering the maximum texture size, turning off texture filtering or using smaller bucket size." 
I'm using P4 rendering with Anti-alias, bump maps and texture maps.

I then rename the tex, resize (compress), make new nodes and try again.
When one texture works another one dosent.

It seems to be only on two texture areas the problem is.


BeyondVR ( ) posted Sat, 12 January 2008 at 3:49 PM

After resizing and reassigning the new maps, have you tried saving the file and reatarting Poser before you try to render?  You may have the old and new maps in the memory, and this will get rid of the old (big) ones.

John


Acadia ( ) posted Sat, 12 January 2008 at 5:50 PM · edited Sat, 12 January 2008 at 5:55 PM

Quote - "There was a problem during rendering. You can reduce rendering memory usage by lowering the maximum texture size, turning off texture filtering or using smaller bucket size."

Ahhh Yes! the dreaded not enough memory to render message.

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 cene 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 bum 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

"It is good to see ourselves as others see us. Try as we may, we are never
able to know ourselves fully as we are, especially the evil side of us.
This we can do only if we are not angry with our critics but will take in good
heart whatever they might have to say." - Ghandi



Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.