Al set ready for P6 to arrive.. Should I keep the !Daz folder in my P5 runtime or does it help to move it to the P6 runtime? Now where is that truck - not a good day to give up smoking!

To link your Poser5 runtime properly for Poser6, check out the Knowledge base on CL's web site. It tells you exactly how to do it correctlt there. Follow this and everything will work just fine! thefixer poser coordinator

Message edited on: 04/04/2005 15:05

The injection poses will work from an external runtime, but copying the delta folder to the P6 runtime wouldn't hurt. You might see a slight improvement in the time it takes to inject all morphs.

A bigger question is whether you'll want to adapt the DAZ figures to P6's external binary morph technology.

Message edited on: 04/04/2005 15:08

could you elaborate on the "external binary morph technology"? Thanks Dragontales

By default, Poser 6 saves the morph deltas in a separate binary file (.pmd). This reduces character and scene file sizes, speeds loading, etc. And multiple characters in a scene can use the same .pmd, so it supposedly will save memory, also, once the memory-handling issue is resolved. You can disable external morphs from your General Preferences, if you prefer to keep them internal.

AHHHHHH that explains why when I imported the pz3 file into Vue 5 Esprit that the morphs were gone. I guess one reason not to use the separated binary file would be if you can open the poser file in another program. You've just helped solve a major mystery for me. Thanks for the info. Dragontales

I had to copy my delta folders over to the P6 runtime. Poser couldn't find them otherwise. And when I tried to cancel the search for them, it locked up and crashed. Just like with P5.

Good point, Dragontales. The same problem came up with the Poserfusion hosting plugin and Shade. And DAZ|Studio or Bryce 5.5 probably won't be able to read external morphs, either, unless DAZ chooses to add support. randym77: Mine worked from an external runtime, but I decided to move them over to P6 anyway.

For some reason my last post didnt work so here goes again... I understand the 2 options for getting my P5 content merged - Copy the Runtime over or add Runtime to Libraries. From this thread I am getting the impression that merging the content would make injections and loading of things a little faster, but then the question about Internal/External mrophs. If External makes things render faster and uses less memory why wouldnt you just go for it?If I understand correctly, the only drawback is that you lose morphs when importing the file into a 3rd party like Vue or Shade? Are there other ways to deal with the morph loss if I copy the content to the P6 Runtime? Could someone help clarify the pros and cons for me in simple language? Im not really big on 3D technical terminology.

pixelpunk10010, I'm no great technical wiz either. When I first got Poser6 I put my Poser5 runtime over to it in the way I though it would work. The result was c**p, nothing worked properly. I went to CL's web site and followed their instructions in the Poser6 knowledge base and hey presto, everything worked just great. No problem with DAZ figures or the DAZ injects or deltas, morphs or anything else. My advice, if you're like me is to follow CL's instructions and do it that way, worked great for me! thefixer poser coordinator

Fixer, can you post a direct link to the article you are talking about? I looked around, and the P6 knowledge base at CL looked very skimpy, with nothing about runtimes that I could see.

Attached Link: http://www.curiouslabs.com/article/articleview/807/1/597/

Thanks! Looks pretty straightforward. Just like P5, actually.