Forum: Poser - OFFICIAL


Subject: "Fake" area renders with P8 SR3?

Cage opened this issue on Jul 02, 2010 · 4 posts


Cage posted Fri, 02 July 2010 at 1:22 PM

I'm having some difficulties with area renders in SR 3.  About 20% of the time, one render out of every five (I've been counting), Poser will fail to handle an area render.  I'll just end up with a Preview render, seemingly, but it may not even be doing that.  It may just be doing nothing and is just displaying the preview background at the end of the fake render.

The problem is really driving me a bit nuts now.  I'm hoping someone here knows a simple tweak to settings or something which can help circumvent the issue.  Bucket size?  Number of threads?  Graphics memory alterations?  Swap disk size?  Anything?

Just kind of hoping it's not something else I'll have to report to customer support.  I suspect they're as sick of dealing with me as I am of dealing with them.  :lol:

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.


Ghostofmacbeth posted Fri, 02 July 2010 at 4:09 PM

It happens to me in Poser 7 and Poser Pro 2010 too.



johnpf posted Fri, 02 July 2010 at 5:27 PM

You can add the 2008 version of Poser Pro to that liist, too. It's annoying and sometimes, to get around it, I'll do a full render but block off the unwanted parts with a few cube primitives. It's not as quick as a proper area render, since it still has to render the cube surfaces, but at least I know it will work.


Cage posted Sat, 03 July 2010 at 12:38 AM

Thanks, guys.  I don't recall ever having had the problem in Poser 7, and Poser 8 wasn't stable enough to use regularly on my system, before SR 3.  I thought it might be something new with the current service release.  But evidently it's another long-standing, multi-version bug.  Which is really sort of worse, actually.  Sigh.

Has anyone had this problem and discovered a way to make it stop?

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.