|06 June 2006||#1|
My Mind Is A Wastelandportfolio
Join Date: Mar 2006
vue 5 rendering....?
yes, i've read the post's here in regards to rendering and that neat little message that says, "memory all used up, bud!"
with 2 gigs of ram, radeon 9600 pro card, p4 3.0 ghz chip...i'm finding this a lot hard to believe.
right now i have a scene with 2 million polys and i can't render anything above "final" (i think that's whats after production/test mode)...and even then i have to drop the dpi down below 300. it will write to disk and get stuck at 99% and lock up. silly.
now i know it's a big scene but not even being able to render it is stupid...if it takes hours on hours that's one thing, at least it's rendered though!
any help would be appreciated.
|06 June 2006||#2|
CSB & Friends
Black Forest, Germany
Join Date: Mar 2005
What Vue version are we talking about here? I guess Esprit.
2 million polygons is not a big scene, my average for Esprit is around 50 million -
for Infinite we talk billions of polygons.
However, the problem you have is real. What is in the scene? This is more important than the actual count of polygons. Any objects with highres textures? From Poser for example? Ultra highres textures are identified as "enemy #1" - so to say.
You should check that and reduce them if possible.
I guess you are not using network rendering - for that you need to do some extra settings to render in higher quality level than final - 2.5D blur off.
As well i often heard that when people do the dpi setting higher than the default there are problems. I never do that - this is something that is absolutely NOT needed at all. What is important is the amount of pixels you render, not the area you spread them out in. Rendered images for print need to go through something like Photoshop anyway - to change anbd control the color mode - and there the dpi setting can be done easily too.
It is nice to be important,
but it is more important to be nice.
|06 June 2006||#3|
Up to Hereportfolio
Join Date: Jun 2005
Good ways to reduce that is to look hard at your scene. Things that are not close to the camera and will not suffer from reduced texture maps, right click on them and chose "bake to polygons" a great memory saver. Also look at the textures you are using. Doing a lot of reflection/refraction or perhaps transluscency? Try tweaking them down, also. There are lots of little things you can do to help make it over the threshold where you'll get what you're looking for.
|06 June 2006||#4|
Join Date: Sep 2003
Thread automatically closed
Note that as CGTalk Members, you agree to the terms and conditions of using this website.
|Thread Closed share thread|