LadySythe opened this issue on Feb 28, 2006 ยท 22 posts
LadySythe posted Tue, 28 February 2006 at 2:04 PM
Help....again... whimpers
Thanks!
LS
svdl posted Tue, 28 February 2006 at 2:15 PM
Yup, a well known issue. Here's some things you can do: - lower the maximum texture size to 1024; - increase the minimum shading rate (keep it at 1.0 or less though) - lower the bucket size to 16 If you're using many spotlights to simulate global illumination, replace those with a single IBL light with AO enabled and shadows disabled. A few (no more than 4) additional (spot or point) lights should be enough to light your scene. If you're using mapped shadows, lower the shadow map size. Play with the shadow cams (look through each shadow cam, and zoom and pan until only the visible portion of the scene is visible in the shadow cam), that will get you nice shadows without using extreme shadow maps. Try raytraced shadows wherever possible. If you're using Gather nodes, a complex scene sometimes refuses to render. Hope this helps.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
operaguy posted Tue, 28 February 2006 at 3:06 PM
GEE I'VE NEVER SEEN THAT MESSAGE BEFORE! everything svdl said. plus you can actually reduce the size of your texture files. (Scale them down in a 2D app) And the final thing to do: write to e-Frontier and petition them to make Poser talk to a LOT MORE RAM. Thanks ::::: Opera :::::
LadySythe posted Tue, 28 February 2006 at 4:04 PM
Ehhh... Ok. But how do I go about re-adjusting those three things? I have eh... I guess about 5 lights...er... 2 main lights (white and an orangey gold) and the rest are shadow. Anyway, I turned off the shadows, deleted the Macrocosmos thingy. Texture size...texture size... That doesnt have anything to do with the render settings? I had the puppy set to 1024...but, as you can see, I got that freaking thing 3 times before closing the program. Hmm. Everytime someone answers one of my questions, it sounds like Im listening to my best friend talking in Dutch :p Im a newbie...and Im teaching myself everything...so... ehmm...yeah ahem Gonna have to dig out that 20+mg manual again. In over her head... LS
richardson posted Tue, 28 February 2006 at 4:05 PM
Yep. Got that tshirt. Ditto and just reboot! Poser saves the textures in memory until this happens. Every scene you open. Everything you add. And every texture you change your mind on. Eventually, (bs line) it cannot render a cube with color...
diolma posted Tue, 28 February 2006 at 4:35 PM
"Ditto and just reboot"... almost..:-)) Save your scene 1st! Exit Poser, restart Poser, load scene, see if it'll render. Poser IS a memory hog, and also likes to squirrel everything away, just in case it might come in useful sometime. But only for the session. When it saves, it only saves what is actually used in the scene. So exiting and reloading the scene can often clear up memory problems..:-)) Cheers, Diolma
bandolin posted Tue, 28 February 2006 at 7:33 PM
Quitting and restarting Poser has never worked for me. I've been reduced to rendering each figure separately and compositing them in post-work. It is the sigular most aggravating thing about Poser, for me. Often, just out of frustration, I export the entire thing to Bryce and render from there. I'm sure Vue could also handle multiple figures and Props. My Bryce record is 22 Poser figures and numerous props totalling over 5 million polygons. The render took 4 days, but it rendered.
<strong>bandolin</strong><br />
[Former 3DS Max forum coordinator]<br />
<br />
<a href="http://www.renderosity.com/homepage.php">Homepage</a> ||
<a href="http://www.renderosity.com/mod/sitemail/">SiteMail</a> ||
<a href="http://excalibur.renderosity.com/mod/gallery/browse.php?user_id=70375">
Gallery</a> || <a href="http://www.renderosity.com/mod/freestuff/index.php?username=bandolin">
Freestuff</a>
<p><em>Caution: just a hobbyist</em></p>
Parthius posted Tue, 28 February 2006 at 8:38 PM
One of the real PITA things about P6 is that it won't render a single V3 at max default render settings. The best place to start when it gives you the evil message is to try a render at minimum default settings. If that works, you can try increasing settings until it barfs. If it win't reach acceptable quality settings, then you can start playing other games. About the only alternative is to start using another app to render (the route I finally took in disgust).
kathym posted Tue, 28 February 2006 at 10:18 PM
I'm running into simular problems, though I get the "out of memory warning" if i try to go too big or use FireFly at a better resolution.
Just enjoying the Vue.
:0)
thefixer posted Wed, 01 March 2006 at 9:05 AM
Mwwwhahhahahaaaa! Welcome to the World of pain that is Poser 6!
Injustice will be avenged.
Cofiwch Dryweryn.
LadySythe posted Wed, 01 March 2006 at 1:18 PM
World of Pain indeed!!! growls I feel a Sithly mood swing coming on... lol Yes Poser IS a memory hog. I had to alt-ctrl-delete a few times cause the pc was slowing down. I had outlook express, Poser 6 and another program running. At that time, Poser was running over 100,000 in memory! YIKES!! I ended up closing everything but poser. And as for save, close then reopen. Tried it. 3 times. Didnt work. exporting to another programs sounds more promising. I have 3dx max, Maya...and working on getting Vue 5 Infinite. Would any of those work for rendering??? Feeling face getting hot... phew! LS
LadySythe posted Wed, 01 March 2006 at 1:18 PM
World of Pain indeed!!! growls I feel a Sithly mood swing coming on... lol Yes Poser IS a memory hog. I had to alt-ctrl-delete a few times cause the pc was slowing down. I had outlook express, Poser 6 and another program running. At that time, Poser was running over 100,000 in memory! YIKES!! I ended up closing everything but poser. And as for save, close then reopen. Tried it. 3 times. Didnt work. exporting to another programs sounds more promising. I have 3dx max, Maya...and working on getting Vue 5 Infinite. Would any of those work for rendering??? Feeling face getting hot... phew! LS
richardson posted Wed, 01 March 2006 at 2:56 PM
100,000 is nothing. Are you sure you didn't forget a zero? I wouldn't give up yet. Lots of things can cause this. No fault of Poser. But you need a big processor. Lots of memory. A fast harddrive...and the right settings. Can I see your rendersettings? Be happy to help.
LadySythe posted Wed, 01 March 2006 at 3:53 PM
Eh... Let me see... closes other programs One post please :p LS
Jules53757 posted Wed, 01 March 2006 at 4:17 PM
Did you install the SR2?
Ulli
"Never argue with an idiot. They drag you down to their level and beat you with experience!"
LadySythe posted Wed, 01 March 2006 at 4:58 PM
the SR2?? Im not sure. I still have lots to install...and move around sighs at thought LS
LadySythe posted Wed, 01 March 2006 at 4:59 PM
richardson posted Wed, 01 March 2006 at 9:33 PM
Yikes. Those are "nada" settings. Well. That wasn't it. 50 alternatives to go. I'll wait for the SR2 update.
LadySythe posted Thu, 02 March 2006 at 4:35 PM
I dont know what settings to use, so I just didnt touch anything. Its basically at factory default. Anyone have other settings to suggest??? SR2? When does that come out, if not already? Hmmm. Ill look into it I think. LS
Jules53757 posted Fri, 03 March 2006 at 2:10 AM
Check out e-frontier, they released the SR2 in November?? 2005. If you purchased Poser later, AFAIK it is not included in the software, you have to install in addition.
Ulli
"Never argue with an idiot. They drag you down to their level and beat you with experience!"
LadySythe posted Fri, 03 March 2006 at 1:42 PM
Eh, Ive got all the new updates, etc from e-frontier. I just have to install them. Content update is already installed. Does this make any difference? LS
LadySythe posted Fri, 03 March 2006 at 1:48 PM
Hmm. Seems I missed something smacks forhead Nevermind, Im dling the SR2 now. Maybe it will help shrugs Lets see... LS