Fri, Nov 15, 5:51 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 15 9:11 am)



Subject: another rendering problem...


peevee ( ) posted Sat, 10 March 2007 at 12:07 PM · edited Fri, 15 November 2024 at 5:48 PM

Hi there,

I'm having some trouble rendering scenes in poser 7 ( don't have sr1 yet but here's why ) :

I had the same problem using poser 6 although my computer perfectly matches the system requirements ( in fact it's even better than that ) None of the three service releases for P6 fixed the problem, so I gave up hoping SR1 for Poser 7 would do it since P7 itself still has the same problem...

I happen to have one of these programs that lets you see the amount of free RAM mamory. Now, whenever I try to render, the amount of free RAM memory never drops below +/- 500MB and there's still about 50 GB free disk space. Yet poser ( 7 ) tells me that I should do one of the following things:

lower the bucketsize ( it's allready down to a value of 1 )  
Render in a seprate process ( but what does that mean? Do I need to export my file to another 3D application?
The render dimensions are approximately 40cm x 40cm ( I know it's big, but it should be possible I've seen poser rendered images that big ) And yes I tend to put the render settings quite a bit towards the final stage, but then again I want to have a quality render.

raise the adaptation threshold ( again: what does that mean?) It's not in the manual, I even checked the one on my hard disk so I could do a word search and be sure: it's not in the manual.

If somebody knows what these two things mean, and how to do them, please let me know. 
If somebody knows why P7 doesn't render please let me know as well

Thanks a lot in advance,

PeeVee.


adp001 ( ) posted Sat, 10 March 2007 at 12:55 PM

If you try to render a 40 x 40cm pic with standard 300 DPI, your image will become 4724 x 4724 Pixel. That's a lot for non-trivial renders.

Solution may be:

  1. Use raytraced lights only. Shadowmaps are stored in memory, raytraced light is computed at runtime (Poser)
  2. Change the size of virtual memory (Windows)
  3. Add some internal memory (Hardware)
  4. Add more internal memory (a joke)




richardson ( ) posted Sat, 10 March 2007 at 6:29 PM

Set your bucket at 64 to start. Let P6,7 lower it as needed 0n auto (EDIT>General prefs>Misc tab>check Adaptive threshold) Just below is the controler you seek. I've never messed with it. Chances are, you have exceeded the memory limit of your pc. You did not say how much you have total. It can be exceeded with a hi res head in the viewer and/ or with unrealistic rendersettings. I would leave dpi settings at default until you resolve a render(dpi is for printersettings only). I would turn off anythging you are not sure about elsewhere too (DOF ot texture filtering... ). Shading rate is a renderkiller(dropping by 1.00 = 100x calculations per pixel) Ray Trace bounces too (less is better) Pixel samples (less is better. 2-3 for closeups, 3-5 for full figure) Your lights may be the culprit too... What are the bias settings? As adp001 stated,, each shadowmap is stored in memory. RayTrace lights are "lighter" on resourses. Set bounces to 0 if you are not using reflect, refract. Better to start low and work your way up. Save before you render, too...


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.