Having an problem loading saved pz3 files that contain V4.2 in the scene.  They won't load and the document window vanishes.  I've discovered through trial an error that if I delete the pmd file, I can then load the scene without problem, but this seems to contain the morph target info as those all disappear.

Does anyone know why this happens and what to do about it?  I'm running an old copy of Poser 6 until I can get Poser Pro, but that may be awhile.  In the meantime I'm trying to get back into doing 3D renders and graphics.  Been away for awhile.

Turn OFF the use binary morphs un preferences. It makes your files a bit bigger but seems more stable.

That seems to have corrected the problem.  Quite a relief, though I wasn't going to be able to use the V4.2 figure.  Thank you for the tip!

You know I've heard alot of people say that binary morph targets cause problems in poser, but, for the life of me, I haven't ever encountered one. maybe just lucky.

I don't know why it caused a problem, just once I turned it off and resaved my scenes I could then reload them without trouble.  Previously I'd had a scene (just posted a render last night), and with the binaries turned on it would not load.  Left Poser sitting for nearly an hour (watched a TV show instead) hoping it would load thinking maybe it was just having trouble with all the props and textures.  Once I got rid of the binaries, the saved scene could be loaded in about 20 sec.

I had also had trouble with rendering some hi-res images (3,000 x 3,000) which I found odd cause I easily work at that resolution in other apps (Photoshop CS5).  Once I turned the binaries off, the rendering problems went away as well, again I don't know why that is.

I don't know if in this case it has anything to do with using a more current figure like V4.2 on older software like Poser 6.  I suppose that's possible (seems likely but I haven't gotten the current version of Poser Pro yet to compare against).  For the moment, however, I'm just happy to have it solved.  I'd bought quite a bit of stuff from Daz recently and was worried I wasn't going to be able to use most of it.

Quote - You know I've heard alot of people say that binary morph targets cause problems in poser, but, for the life of me, I haven't ever encountered one. maybe just lucky.

They play hell in external apps - Vue for e.g and for the supposed benefit, you get all sorts of grief.  A lot of people who render outside Poser won't use them

I had exactly the same problems with Poser 5 and Poser 6 and now I always switch off external binary morphs.  I am now using Poser 2012 and a lot of people say there have been a number of changes in this area but I have never wanted to find out.  Files are larger but storage is cheap so I am sticking with what I know works.

Well that would be my next question, what exactly is the point of the external binaries?  If its just to make file sizes smaller that doesn't seem very important to me.  I've got 2 TB on the HD.  I don't think I'm going to be running out of space anytime soon.

IIRC, that "smaller file size" was in fact the primary marketing reason behind the introduction of external binaries.

And a few people did question that, as even then it seemed like something introduced a little too late to be really useful.

could be wrong, but I think it's also possible to make injectible moprhs using the binary files, don't know for sure since I've had it turned off for years due to the similar problems as others...