Attached Link: http://www.fotoonz.com

Hi! I've beaten my brains out all week trying to render my latest 'toon in Poser. It's ratracer's CafeII with two characters. At 800x600, the render works. At 3500x2700, it fails every time. I've had the bucket size as low as 8!! And the max texture down to 750. No dice. Both characters have the HyperReal textures on them. Could this cause a problem??? Thanks!! Gordon

Resize a copy of the (5333x4000) texture to 50% in paint prog. Same for head. Inmatroom load new 50% to torso,,, new head to head. Save both to library,,, then double click them onto each part... If in P6 you can do a material save once you finish the switches. If you've got "big" hair, do the same ( turn off shadows and visible in RayT if possible). Set min. shading rate to 1.5. Max texture to 1024. Set bucket to 32. Hide anything NOT visible. Especially under clothing or out of scene props. Back in poseroom save new cr2 to library. Resave your scene and retry, or better yet do a shutdown of poser to clear the memory (it stores textures until it dies)

Yikes! I didn't realize those skin textures were that large. As a photographer, I applaud that. But I can see where that might tend to chew up available memory. I'll give that a try. Um... I did that new HyperReal for V3 trick on one of them where you can use ANY texture with the HP python script. I wonder what THAT causes. Thanks! Gordon

I haven't experienced HyperReal to be a memory hog. Even if the texture is over 4096x4096, whatever you set the max tex size in Firefly is what it will be. I've tried rendering only one figure with the Cafe II and it hung. I think the Cafe is the problem, especially if you've loaded everything.

It's a big one for sure. I've got all non-visible textures on it killed. It's one big chunk of geometry, though. I also shut down displacement mapping. I'm trying a partial render right now with the texture completely removed from one of the characters, just as a test. We shall see.

it is a big memory hog, i couldnt ever get a comp with 512mb ram to even render a 1024x768 pc, with render settings rather low but it does give good results, so its worth the memory poser is a bit more to blame for the problems though :P

Anxcon, I render with hyperreal at 1024x768 all the time on a 512mb machine, no problems. And that's without reducing the texture size in Firefly. Maybe it has to do with the number of figures in the scene.

Well, Poser is absolutely to blame. None of the above should cause a render to crash. That what multi-segment, multi-pass rendering is for. Oh, Poser can't do that!!! :-D And that's the problem. Working around it. I finally got a finished product, here. I'll tell y'all how in the morning. Gotta hit the sack. Almost midnight here.

Attached Link: Glow Worm @ Daz

*That what multi-segment, multi-pass rendering is for. Oh, Poser can't do that!!! :-D* Actually, it can. That's what Glow Worm is for. Great proggie. Highly recommendable!

Attached Link: http://www.fotoonz.com

GlowWorm can break a render into segments. I bought it hoping it would do that, but, from reading the instructions, I'm not seeing how. And that's how I finally got a finished rendering from this scene. I broke it into two separate scenes. A top half and a bottom half. I deleted anything not showing in that scene's half. This didn't fix it, yet. So, I used the heirachy editor to turn off ALL the body parts that weren't showing in each respective half. I got rid of the HyperReal texture on one of the characters in the "bottom half" scene, because he was wearing pants and boots. Set the bucket to 24. Max texture size to 750. Shading rate to 1.5 . And rendered the two hunks. Then composited them in Photoshop. Whew!!!! What seems to have done the trick??? Turning off body parts of the second character. Unti I did that, the renders still crashed. This was the character that was wearing the default HyperReal texture. Maybe when I ran the python script for the texture it encountered some weirdness and created the shaders and texture in a more humongous fashion than usual. I just don't know. I'm glad I finally got the render. Too bad I had to waste several evenings doing it. Thanks for your help and suggestions, All!!!! G.

hehe i havent done a render in 6 months without splitting it up lately i've been making 300dpi poster sized renders, for fun the last one i split into 150 (10x15) seperate renders just to get the quality and still render it without crashes also learned that if you move camera right, you can keep the same view, and render a full screen (maybe obsolete due to P6 new area render, but it seems to work better for rendering big pics)