Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)
I get the same error actually. Usually when I have more then one figure using the same skin though. I have 2 gigs of ram installed and usually any figure with different skins work fine. 2 using same skin have no probs. But when moving to 3 or more it hates me and I lose all my work. Not sure why this is the case. Perhaps the skin itself is the problem seeing as they are large and high rez to begin with. Hopefully someone will have an answer for this probelm.
you can try shrinking the textures (back up the old ones first) in a paint program -- they all do this. You can even get a free one that's pretty good at http://www.getpaint.net/index.html
So if the figure textures are say 3000x3000, try downsizing it to something like 1024x1024. In many renders it's not necessary to have such large textures -- large textures are only needed for close-up shots.
Attached Link: Smith Micro
Did you install all the Service Releases? Check SmithMicro for the latest SR2.1.Ulli
"Never argue with an idiot. They drag you down to their level and beat you with experience!"
I have a PC,Intel dual Core,2.4 processor, with 3.24 of ram.
The image I'm trying to render is just DAZ's V4 with one set of clothing, no props, no background.
A window says I'm out of memory.
another window says "Raise adaption threshold or specify smaller bucket sizes.
I'm afraid I don't know what they are talking about.
V4 series seems to be the problem, V3 can have clothing, props, backgrounds etc, and no memory problem.
Did anybody have a problem with the latest Poser7 fixes?.
I run a AMD dual core machine with 4 gigs of RAM ( accessing 3.50 of the RAM) and never encounter these errors and I feel it's because of using the manual settings which gives you control over the things I mentioned above which will lower the use of resources on your machine.
Try using the manual settings and lower the bucket size down you do not need a bucket size setting larger than 64 and even that in my opinion is much I'd try a setting of 32. I have posted my settings as a guide.
Also I found that reducing textures sizes help there is a utility I use here in the marketplace called Downrezer that works well for this. My settings are just the basic setting for a preview and not for a final render. But it is just to show you the manual settings tab.
I'll try shrinking them and see if that works. I use manual settings often so I don't have issues there. Its just if I use the same texture for lets say...triplets with full gear and all I get the error. I use photoshop so I don't need the free programs I should be ok with what I have. Hell I noticed when I shrink them their pretty much still high rez (reason why I love photoshop). So I'll give that a try. Any other suggestions would be great.
You can also try rendering as a separate process if you have a multicore machine. Or was it unchecking that option? I don't remember, but once I had that error dialogue, and I changed that setting, and everything rendered fine
still hooked to real life and enjoying the siesta!
Visit my blog! :D
Visit my portfolio! :D
I set bucket size 150 when using p6 and p7 i set 150 bucket and separate process, i have amd 4200 2 gb mem xp 32 and can go so far.
When i render on my quad machine with 4 separate process instead using xp 32 i boot into xp 64 and have 2 gb mem.
Xp 64 i can render max settings more happy than under 32 as xp 64 handles mem better.
Best way is practice with bucket size from 10 to 200 but if you can in art program export a texture map lower far better.
I take a 3000 x 3000 texture and export it with no loss down to 500 k instead 1 mg so just experiment that's the best way.
Another good tip is to delete high rez items from your scene if it is not the main focus of the render or out of camera shot no sense wasting resources on something not seen. Also, as a matter of fact, using low rez items such as props and other things only seen in the background helps also.
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.
I keep getting this error when rendering at the higher settigns. (Default setting one from the right.) Memory usage when this occurs isn't all that high, less than a gig, and I have four gig of physical memory. (Yes, I know that Poser can't use that much, but it should certainly be able to use a full 2 gig.) I generally don't get that problem one level of rendering down.