Everyone seems to recommend turning this option off, but since buying P2012 last year I decided to leave it on and I don't seem to having any problems so far, knock on wood.

I've tried out having the option off recently but I turned it on again because-

1. Saving - I save often because I have undo levels very low, and saving a scene without EBM enabled takes seriously longer.

2. Perhaps just my imagination, but with complex scenes EBM appears to lighten the load on my PC. Malipulating objects in a heavy scene seems to be slow to respond and jerky unlike when I have EBM enabled. Something to do with the much smaller file size, or some other unrealted factor? Or maybe I'm just imagining it.

(Win64, 24GB RAM etc, etc.)

It creates file corruption for me.

Quote - It creates file corruption for me.

And me as well.

Laurie

Ditto... But only in a few instances. Doesn't make sense for me to risk it though, plus it's another file to add to an already absurd amount of Poser files.

It is "said" that P2012 corrected the inherent problems previous versions of Poser had with PMD files. And I haven't experienced the issues that others have had with EBMs.

Which leads me to believe that corruption might be associated with a mixture of OS, unique installation peculiarities on different PC systems... or God pats Ashley on the head for living a blameless and pure life up to date.

While the later is demonstrably a rediculous joke, the gremilns at play between each and every Poser installation in conjunction with the uniqueness of everone's PC set-up could explain the difference between my experience and that of others. The flutterby effect.

You are not alone.

I have external binaries on all the time. I do get sometimes (very rarely) a PMD error but that did not seem to have an effect on any of the morphs which were present in the scene.

SR3 had fixes for issues with external binaries and that seemed to have solved the ones I had in the past for me. One of them had to do with the way you work: Accumulated saves (Save As) under certain conditions would result at one point in a corrupt PMD.

The big advantage in having it on is that speed in saving and loading a scene. A very large scene  will now save in 2-3 seconds which used to take up to a minute without external binaries.

I think a lot of people turned it off in Poser 7 and never tried it again.  I lost a few hours of time trying to recover a scene where the pmd file was bad and that was the point I turned it off.

My work pattern is to save before a render and I usually go for a snack , or do other chores while Poser renders.

Quote - Everyone seems to recommend turning this option off, but since buying P2012 last year I decided to leave it on and I don't seem to having any problems so far, knock on wood.

It works just fine on or off in Poser 6.  But the SDKs that Curious Labs wrote for it back in the day can handle such things.

Definate file corruption for me in PP2012. As mentioned above, I use a lot of "save as" as I'm working on a project.

Quote - Definate file corruption for me in PP2012.

Just curious - have you experienced that yourself with PP2012 SR3.1?

Yes wimvdb I'm afraid I still have the problem, but I am working with very complex files. Animations with thousands of frames and dynamic cloth and hair. I don't seem to have problems with something simple, but I have it unchecked for now.

I am working with pretty complex files as well (although not animation).

Have you reported this to SM? They are keen on solving this PMD issue once and for all. My issues are gone now, if there are any left, they would like to know. But they need to have someone who can give information on when this problem occurs

You know, wim... I'm not sure I HAVE tried it since 3.1 came out.

I'm going to turn it on again and see what happens. But if it f's up, I'm sending you the bill for my time!  (Just teasing)

I'll send SM an update. I have talked to them in the past, but not since 3.1

My issues are gone for everything except the animations. It may well be an animation issue.

Quote - You know, wim... I'm not sure I HAVE tried it since 3.1 came out.

I'm going to turn it on again and see what happens. But if it f's up, I'm sending you the bill for my time!  (Just teasing)

I used to have it off in P7, turned it on again in P8 until I got issues. Then in P9 I tried again and when I had issues again, I worked with SM to get these fixed. Now I do not have them anymore.

But telling everyone to turn the thing on, goes too far. There may be problems with it of which I am not aware. Toxicwolf's problem may be one of them

Quote - I'll send SM an update. I have talked to them in the past, but not since 3.1

My issues are gone for everything except the animations. It may well be an animation issue.

Thanks for doing that. Even if it is limited to animation they want to fix those too.

The strange thing is that with the PMD off, the animations never fail to save properly. It could be that the changes they made are not in effect when the file is an animation file. I'll mention that to them.

I honestly have never tried it since I first got Poser 7, as the advice then was not to use it.  The risks seemed to outweigh the benefits...

I leave it off, may be fixed in 2012 but having lost a number of scenes in previous issues I am not about to try again.  The impact of having off is not major and so I also think the benefit is not worth the risk.

You Lone Ranger. Me Tonto. (Sorry, Couldn't resist)

I leave it on all the time and do not have problems. I had it on with Poser 8, Poser Pro 2010, and Poser Pro 2012. It really speeds up opening and saving of files. It also make MUCH smaller files. My animations and cloth simulations don't have a problem either.

Sadly, I have found that it does not work with Genesis via DSON. I think thats do to how DSON importer works. So when use Genesis I end up with over 100 MB file poser with just her in it. Very annoying.

I always wonder where people ran into the problems. Was it with morphs in character files or props?

I only use external binary morphs since nearly 3 years and never have major problems.

I even have converted all my runtimes items to binary morphs and you can't imagine how much space disk you can save. I also have created for example a V4 cr2 with all morphs (++, aiko, Girl and even some NGM morphs) on an unique external PMD. With this I can use huge PZ3 scenes with less than 1MB size instead of 100 MB or more without EBM ! And of course scenes are loaded in less than 10 seconds.

I recently even have extracted embedded delta morphs in pz2 files.

To solve any PMD link problem I highly recommend the D3D tools and the poser file organizer in particular. There has never been what you can call corruption files with PMD, it's just that the the PMD link in the pz3 files is wrong because it has been moved or relatives paths are not been used. So edit the pz3 if necessary.

Nah, you're not the LoneRanger, I've taken to using them with this latest version.  When I read that they were improving stability, I went looking at advantages and disadvantages as posted in the forums and realized that the majority of issues people were talking about actually seemed to refer to problems with the Daz third party figures losing morphs.  Since I wasn't using them to speak of anymore, it only made sense to try and save some space and speed things up.

The problem may well be fixed but I think there is also a big chunk of "once bitten twice shy" about this one.  With the cost of hard drives being comparitively low space is foften not an issue for many.  Those who have had problems in the past and lost work because of it, me included, are not so sure it is all worth the risk.  Of course each to his/her own and if storage is scarce or load times are a major factor then the benefits may well be worth it.