I seem to be having a weird problem that just started happening.
If I load V4 it might crash shrotly afterward, or if I reload a previous saved scene (done in P7) it will crash when I load it. Is anyone else having this problem? Is there a solution?

Another question I can't find the answer to:
In the V4 folder there is the option of  V4 to V3...what exactly does that do?

Currently there is a problem with V4 and external morphs in P7.
Open the General Preferences dialog and uncheck "Use external binary morph targets".

The V4toV3 figure, allows you to use clothes rigged for V3, but it is somewhat limited w.r.t. morphs.

Thanks nruddock.

Does it work for you PerfectN? I saved a V4 scene yesterday and today I experience I cannot open it. Crashes to desktop everytime. also unchecking Use external binary morph targets does not help.

Any info when V4 will work correctly with Poser 7?

Quote - Does it work for you PerfectN? I saved a V4 scene yesterday and today I experience I cannot open it. Crashes to desktop everytime. also unchecking Use external binary morph targets does not help.

Any info when V4 will work correctly with Poser 7?

If you've saved a scene with V4 in and you had binary morphs turned on, you'll need to delete the PMD file before the scene will load (the option just dictates whether binary morphs are saved, it has no affect on loading).
You will lose the morphs by doing this, but it will allow you to recover most of the scene.

thanks nruddock! That worked but as expected all my face morphs are lost. So I have to start over because this file was pretty much only a custom face. My question before I start again would be: Does this V4-Poser incompability mean that I cannot use custom morphs on V4 at all or are only certain morphs affected by this?

Quote - thanks nruddock! That worked but as expected all my face morphs are lost. So I have to start over because this file was pretty much only a custom face. My question before I start again would be: Does this V4-Poser incompability mean that I cannot use custom morphs on V4 at all or are only certain morphs affected by this?

So long as you save with binary morphs turned off, things will be fine.
(see this thread for the technical details of the source of the problem -> http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2679897)

I have also found that if you need binary morphs turned on, you can usually get away with turning it on only for the task you really need it (e.g. saving an external morph target to load onto another instance of V4). 

Thanks but could you enlighten me a bit? What are binary morph targets used for? I'm not really that far with Poser.

Quote - Thanks but could you enlighten me a bit? What are binary morph targets used for? I'm not really that far with Poser.

They are a way of reducing the the overall file size required by storing the morph data in a seperate file (with the extension PMD) instead of being in text directly in the scene / character / prop / pose file.

There are other ways to save disk space, compressing the files using Poser's or Window's built-in support.
However most applications that interoperate with Poser don't get along with either binary morphs or Poser's compression, so these have to be turned off.

I've read here from some others that there are different, and equally crippling, issues that can arise from Poser 7 binary/compressed files (e.g. some people have had problems with Sydney's .crz file).  IMO both cases of these are really Poser's fault, as there is pretty clearly insufficient error trapping - nothing should make an application simply exit with no message, that's obviously a case of an unhandled exception.

nruddock & pjz99 thanks for the explanation! So after all the situation seems not so bad. I just wish I had known that yesterday! ;)

I understand completely, the very same thing burned me the same way in my first days with V4 and Poser 7.  It really sucks.
ps: all I offered was nearly-useless trivia really, nruddock was the one gave you useful info.  ;)