Tried both when not using rendering areas. Of course due to design limitations in Vue, you can't render areas to disk.

Thanks for the reply. Already tried that - see my original message. Vue still crashes even doing a render area as small as 270 x 270 !

...I mean getting it to render above 100dpi at 200dpi. That was the max. But I couldn't get anything above 100dpi until I baked the Poser objects to low count polys.

I tried converting them to VOBs and it didn't have any effect. In fact the only time I was able to get Vue 5 Infinite to render the scene is when I converted the Poser objects to low count polygons. My past experience with Carrara was that it was junk. However that was long ago with v1. I gave up on it then. I'm sorry to hear you are having instability problems with v5. Perhaps I may stay away from Carrara too.

According to Eric Holbrook, C5Pro handles it with no problem and memory to spare. My experience is that similar stuff in other programs poses no problem. I can only get up to 200 dpi in Vue after converting the Poser objects to polygons. I'll keep it at that. Future projects will probably be done in another program, however.

Thanks for the reply, bruno021. After your suggestion, I tried converting all the Poser objects in my scene to low res polygon objects (using bake to polygons) because they are away from the camera enough to not make a difference. The polygon count stayed close to 9.8 million. Still the same problems. I also posted my message to e-on's forum and Eric Holbrook (a great Vue artist in my opinion and one who I admire) posted a reply which basically says that I was right - Vue simply has too many bugs to handle rendering my scene at the resolution I desire. It is very sad that such a creative program can't handle this. I guess I'll seek out another program.

Congratulations CL and kupa on the great redesign of your web site and the comprehensive info on the exciting Poser 5. I really love the picture of (probably the Poser team) standing around the big Poser 5 box in awe. They should be extremely proud. If kupa is listening, I am one Poser user that will put his money where his mouth is - I have my $179 ready to upgrade the minute you add the upgrade to your store. I hope every Poser 4 user will do the same and support the tremendous efforts of a small company like this. This is no ordinary software company in this time of companies who frequently ignore their user base. It is obvious that CL has made a major attempt to pack into the upgrade as many major features Poser users have asked for. Companies like this are far and few between - I know I'm a software engineer for a software company and listening and acting on what your users are telling you they want is very hard to do and can be very costly. Congratulations to kupa and his Poser 5 team. I am looking forward to the new creativity that Poser 5 will give me.

Attached Link: http://www.zipcon.net

Attached Link: http://www.zipcon.net/~cdisdero

Thanks! This worksaround the bug for sure. I sure wish Curious Labs would have posted this workaround on their site instead of just admitting to the bug and saying it'll be fixed sometime. But, do you know if the bug is fixed in Pro Pack?

Does anyone know if Curious Labs finally fixed the following irritating bug that they introduced in the 4.03 patch in the NOW AVAILABLE Pro Pack? Preferred state reverts to the factory state on relaunch of Poser.

I'm PC and they acknowledged this bug on the Curious Labs web site as a bug that was introduced with 4.03.

I just thought members of Renderosity would like to hear what kind of useless tech support response I got to my report of a bug (namely, not saving preferred state on exit) after installing the Curious Labs 4.03 patch. My original question appears at the end: ----- Response from Curious Labs Tech Support ----- From: Tech Guy To: Chris Disdero Sent: Wednesday, August 02, 2000 8:45 AM Subject: Re: Problems with your latest patch 4.03 Rule of thumb is never apply a patch to a used and installed copy, apps change to many parameters that confuses the patch. Reinstall like this: Win presets will remain if installed to the same directory, BACKUP MAC PRESETS (personal custom stuff) WIN:Use control/alt/delete and the task manager that appears to close (end task) some of these tasks, leave if possible only the explorer and the systray running, reinstall. This assures that your install is clean, if your are installing Poser to a different directory then you must assign it a folder example d:/Poser 4, the installer will ask "this folder does not exist, shall I create it?" This assures you that it is a correct install. Mac:In extension manager make an extension set copy of OS base, rename to Installer. Turn off all of the extensions but Apple CD-ROM and QuickTime and QuickTime power plug, reinstall. Something in you system has conflicted with the proper install of the program. This set can also be used to check on further conflicts. Then patch it in this state. Tech The prefered stae is a bug and the fixes will be posted soon. ------- My reply to "Tech Guy": Hey, I'm a software engineer and I don't need to be told about how to apply a patch for a program. I applied your patch to Poser 4.0 (direct off the cd from Metacreations) and guess what, it failed in the exact way I describe. Second, I applied to another fresh install of Poser 4.0 off the cd the 4.02.118 patch (which by the way does not have the bug I described). Then I applied your 4.03 patch. I get the bug I described. So the problem is not with how I applied your patch - the problem is that YOUR PATCH HAS A BUG. So please fix it and don't give me any stupid lectures about rules of thumb. ----- Original Message ----- From: Chris Disdero To: tech@curiouslabs.com Sent: Tuesday, August 01, 2000 7:34 PM Subject: Problems with your latest patch 4.03 I downloaded and succesfully applied your 4.0.3 patch to Poser for Windows. I sure wish you had tested this on installed copies just a little more carefully before shipping it out to customers. Although I appreciate the bug fixes you refer to in your readme.txt file, I don't appreciate the new bugs you've introduced in this patch. The most irritating one is that the preferred state is no longer saved when I exit Poser. Can you guys please post another patch with this problem fixed?

I just thought members of Renderosity would like to hear what kind of useless tech support response I got to my report of a bug (namely, not saving preferred state on exit) after installing the Curious Labs 4.03 patch. My original question appears at the end: ----- Response from Curious Labs Tech Support ----- From: Tech Guy To: Chris Disdero Sent: Wednesday, August 02, 2000 8:45 AM Subject: Re: Problems with your latest patch 4.03 Rule of thumb is never apply a patch to a used and installed copy, apps change to many parameters that confuses the patch. Reinstall like this: Win presets will remain if installed to the same directory, BACKUP MAC PRESETS (personal custom stuff) WIN:Use control/alt/delete and the task manager that appears to close (end task) some of these tasks, leave if possible only the explorer and the systray running, reinstall. This assures that your install is clean, if your are installing Poser to a different directory then you must assign it a folder example d:/Poser 4, the installer will ask "this folder does not exist, shall I create it?" This assures you that it is a correct install. Mac:In extension manager make an extension set copy of OS base, rename to Installer. Turn off all of the extensions but Apple CD-ROM and QuickTime and QuickTime power plug, reinstall. Something in you system has conflicted with the proper install of the program. This set can also be used to check on further conflicts. Then patch it in this state. Tech The prefered stae is a bug and the fixes will be posted soon. ------- My reply to "Tech Guy": Hey, I'm a software engineer and I don't need to be told about how to apply a patch for a program. I applied your patch to Poser 4.0 (direct off the cd from Metacreations) and guess what, it failed in the exact way I describe. Second, I applied to another fresh install of Poser 4.0 off the cd the 4.02.118 patch (which by the way does not have the bug I described). Then I applied your 4.03 patch. I get the bug I described. So the problem is not with how I applied your patch - the problem is that YOUR PATCH HAS A BUG. So please fix it and don't give me any stupid lectures about rules of thumb. ----- Original Message ----- From: Chris Disdero To: tech@curiouslabs.com Sent: Tuesday, August 01, 2000 7:34 PM Subject: Problems with your latest patch 4.03 I downloaded and succesfully applied your 4.0.3 patch to Poser for Windows. I sure wish you had tested this on installed copies just a little more carefully before shipping it out to customers. Although I appreciate the bug fixes you refer to in your readme.txt file, I don't appreciate the new bugs you've introduced in this patch. The most irritating one is that the preferred state is no longer saved when I exit Poser. Can you guys please post another patch with this problem fixed?

I downloaded and succesfully applied the 4.0.3 patch to Poser for Windows. I sure wish Curious Labs had tested this on installed copies just a little more carefully before shipping it out to customers. Although I appreciate the bug fixes referred to in the readme.txt file, I don't appreciate the new bugs they introduced in this patch. The most irritating one is that the preferred state is no longer saved when I exit Poser. If Curious Labs is listening, "Can you guys please post another patch with this problem fixed?"