Sun, Dec 1, 2:28 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)



Subject: Ignorant Problem Opening Saved Files


lornix ( ) posted Fri, 08 May 2009 at 5:18 PM · edited Sun, 01 December 2024 at 9:22 AM

Tried searching this but couldn't find anything about it.

On far too many of my saved files, Poser 7 crashes when I try to open them. By crashes I mean it simply shuts down partway through opening the file and I have to relaunch it. I have not sucessfully gotten back a file that this has happened to and I end up starting the project all over and losing my progress.

This happens regardless of how I open the file - I mean, from within Poser using the file open menu item or by double clicking the file in WIndoze and launching Poser that way.

Can anybody give me a hint as to what types of things cause this? I know you can't really diagnose it without seeing the file etc, but if I know what to look out for I may be able to prevent it in the future.

I can tell you what I am NOT doing  ...

I do not save from the render window - I always save from the preview window
I rarely use more than 3 or 4 lights
I don't have any complicated shaders or node setups beyond default character setups - yet :-)
I don;t use any special characters in my file names
There are no memory error messages when I save, so no indication that anything has gone wrong.

I'm stumped and starting to get a little frustrated.

I have the ability to read through the pz3 file in a text editor, so if there is a fix right in the source code feel free to lay it on me :-)

Any help or suggestions would be much appreciated.

Cheers,

Lorne


Victoria_Lee ( ) posted Fri, 08 May 2009 at 5:45 PM

Just a question but I have a good idea ...

Are you using pmd files? (Edit -> General Preferences->Misc Tab->Use external binary morphs targets)  If so, uncheck that.

If this is happening because of the pmd files and any of the Gen4 DAZ characters, that's your culprit.  It's a huge bug in Poser that it doesn't handle the Gen4 characters.  Poser 8 may resolve that but P7 doesn't like them.

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.


lornix ( ) posted Fri, 08 May 2009 at 5:50 PM

Ah yes, I think you nailed it. I am using pmd files, and when I opened the corresponding pmd file for the pz3.... lo and behold it was Simon that loaded instead of a morphed V4.2 character.

Pesky little devil!

I will disable pmd. Thank you so much for your quick response. I believe this to be the problem. And yes, it only seems to happen with the gen 4 figures from Daz.

Dang, I should have asked this a long time ago :-)


Victoria_Lee ( ) posted Fri, 08 May 2009 at 6:05 PM

My gramma used to say the only stupid question is the one you don't ask and that's definitely true when it comes to Poser.

Glad I could help.

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.


Daidalos ( ) posted Sat, 09 May 2009 at 8:38 PM

Sounds like a possible memory problem to me lornix.

I have that happen sometimes when I save a file, and there's lots of stuff in it, making it a huge file.

So I save things seperately incrementally. You might try that, I'd be really interested to know if it works for you.

Hope that helps some.

D.


"The Blood is the life!"

 


lornix ( ) posted Sat, 09 May 2009 at 9:23 PM

That's interesting. I do get the occasional memory error message, but so far I have not seen any weirdness as a direct result. Usually I save as a different name and it seems to be fine, but there are a few props that I use that really seem to hog-down my system.

I'll try what you suggest on some of the bigger ones and see if it makes a difference.

Thanks for the tip!


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.