Thu, Feb 13, 3:09 AM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: Can only render one Mike 3 in an image.


DrYoshi ( ) posted Sun, 21 December 2003 at 2:32 PM · edited Wed, 05 February 2025 at 12:18 PM

I'm having trouble with this scene I'm doing. It's a basic Caesar stab scene and I have 4 Michael 3 figures in the image with hair and cloth simulations. I also have a whole bunch of props in the scene as well. I've tried to render the figures and the background separately, using magenta as a transparency color but it does come out quite right. If I have all four figures rendering at the same time, Poser freezes. If I have one figure and the background rendering, Poser freezes. Thanks!


xantor ( ) posted Wed, 24 December 2003 at 10:24 AM

Couldn`t you replace a couple of the michaels with the poser 4 man or some other smaller (in megabytes)character? You could leave the caeser one at least as a michael 3.


DrYoshi ( ) posted Wed, 24 December 2003 at 1:18 PM

Hmm, well the robe that I'm using to substitute for a toga will also work with Don. I suppose I could try using that figure for the senators. I'll go ahead and try that now.


artistheat ( ) posted Sat, 27 December 2003 at 7:50 AM

Also if you have Michael 1 you can use him for the background guys...The same thing happens to me when I use to many MIL 3 People:)


bogwoppet ( ) posted Tue, 30 December 2003 at 2:36 AM

Yes, I can confirm this problem. I have just attempted to render a scene with two Michael 3's and a Vicky 3 and Poser hangs every time. Task manager says it's busy but in reality it is doing nothing or looping.


stewer ( ) posted Fri, 02 January 2004 at 4:09 AM

a few notes: using magenta as a transparency color You don't need to use a transparency color. If you save your file as PSD or TIFF, poser saves an alpha channel to the file. Are your figures wearing clothes? Hide every body part that's hidden by clothing, that'll save you both memory and render time. As others said, substituting hi-res figures with low-rew ones for the background is also a good idea. If you have decent textures on them, they'll still look very good. Finally, some more info about your rendering settings and the computer you're using couldn't hurt. It sounds to me like you're possibly running out of memory, or going beyond the limits of RAM that Windows can handle per app. If you open the task manager, what does it say about Poser's RAM usage?


DrYoshi ( ) posted Fri, 02 January 2004 at 9:26 AM

It is using 1.51 GB of my page file usually which equates to some of my RAM and all of my virtual memory. I have it on Production render settings with smooth polys off but even when I change it to Draft settings it refuses to render. My computer is a 2.53 GHz P4 with 768 MB of physical memory and 1.5 GB of virtual memory. I will attempt some of the methods you suggested today, stewer. I would rather not substitute for another figure as Mike 3 is the best one I've got right now.


stewer ( ) posted Sat, 03 January 2004 at 3:09 AM

Where exactly and how does the render fail? Is it doing the "adding objects" step? Does it proceed to "Rendering"? Is it completely frozen or does it abort rendering halfway throuh?


DrYoshi ( ) posted Sat, 03 January 2004 at 9:16 AM

It stops at adding objects.


DrYoshi ( ) posted Mon, 05 January 2004 at 12:38 AM

file_89954.jpg

Well I managed to finish the image using the alpha channel method. Thanks for all your help!


xantor ( ) posted Mon, 05 January 2004 at 1:11 AM

Its nice to see the finished picture, most people dont bother showing the pic. You could have rendered the 2 figures at the back and the background as a picture and used that as a background and rendered the foreground picture.


DrYoshi ( ) posted Mon, 05 January 2004 at 7:41 AM

I tried doing that but Poser crashed in the middle of rendering.


TOPcat831 ( ) posted Sun, 11 January 2004 at 11:11 PM

Some ground shadows would look good for your image


svdl ( ) posted Tue, 13 January 2004 at 8:52 PM

Yep, this is a major Firefly problem. Ran into it using 4 V3s, Don plus Posette plus a complex background and lots of light, on a P4 2.8 with 1.5 G of ram and 3 G of VM. It does NOT have to do with available RAM or virtual memory, it also does not have to do with the 2 Gb limit per app. Usually turning down the bucket size to 8 helps, not always. I also try reducing maximum texture map resolution (but not below 1024) and increasing shading rate from 0.5 to 2. Usually I can get it to work that way. I hope SR4 will address this problem.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff


HandspanStudios ( ) posted Sun, 25 January 2004 at 2:07 AM

This might have something to do with what's called 'crosstalk'. There was a file created called a 'null' which fixes some problems from that. http://www.daz3d.com/pages/faq/techtips/crosstalk.html All that stuff also could just be too complex for your resources to render but I'd try the null thing first.

"Your work is to keep cranking the flywheel that turns the gears that spin the belt in the engine of belief that keeps you and your desk in midair."

Annie Dillard


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.