Importing saved V4 bases characters from PZ3 files - geometry issues

HellR4iser

Hi all, 

I'm probably one of the last dinosaurs still dabbling with Poser, which means I'm pretty much stuck with the V4/M4 figures. I've been looking at Genesis for a while now, and tried time and time again to make the switch to DAZ; Every time I was pushed back by how...well, the only word coming to mind is "horrible" the experience of working in DAZ was. Nothing of my existing library worked, poses etc wouldn't apply well and so on. Plus, the interface was an isane, unreadable cluttered mess with no concept of how things affect one another. This was a few years ago. 

Fast forward to today - the interface...still looks like the guys at DAZ read a book about user-friendly interfaces and decided to do the exact opposite, but at least things work - I can use most of my existing library and even adapt V4 clothes figures to a Genesis character, which is a great thing as I wouldn't neet to start completely from scratch. 

So, WILLING to give this a bit of a go, but I've ran into a pretty odd issue - every time I try to import a PZ3 containing a V4 character, the geometry gets messed up pretty badly; The more morphs, the worse it gets. This is NOT RELATED TO THE PMD file issue - I have Poser set up to save everything in the PZ3. 

I've tried saving a simple V4.2 character in Poser, no morph targets applied...it imports OK for the most part, with the exeption of the hips, which come up as shown in attachment #1. 

Attachment #2 (WARNING: FUEL FOR NIGTHMARES) shows what happens when I import a more complex character. No errors were thrown during the import process in either case. 

Any ideas about what's going on here?

 

 

 

DrunkMonkeyProductions

There's a few possibilities for these problems.

1. Morph error.

Check the loaded character to see if any morph dials are not in the zero position. You may need to turn on "show hidden properties" in the parameters tab(tab menu button or right click on the tab and highlight/click the item) and may need to select the thighs for the first one, and probably everything for the second one.

2. Poser only content.

If there's something you're trying to use that is poser only, especially python script based items or poser magnets, it can cause some weird results, without any errors, it's just ignored as DS can't interpret it.

If there's a DS version of something and a poser version, you'll need to use the DS version for DS work.

 

Something to consider is that DS and poser handle things a bit differently. Where poser can add morph dials on the fly, DS has to have all the information applied to the character prior to load. This is why V4/M4/k4 have an initialization script for things like Morphs++ etc. They add definitions to the files for the morph dials, if something is Poser only , it may not have the scripting for adding the morph dials, in which case you'll need to add said dials in Poser and save the V4 as a new Cr2 that will then contain those dials, which may or may not work properly in DS, it's kind of hit or miss.

 

My biggest suggestion is going to be don't try to import scenes from poser, do the work from the ground up in DS.

It will save a lot of headaches and exploding/imploding characters.

 

HellR4iser

Thanks, pretty much confirms my theory that Poser applies the Morphs++ in a way that DS doesn't like at all; Yet, there's something else at play as well - the picture with the deformed hips/upper thigs I posted, that's a "clean" V4 with no morphs injected at all. I've done that as an experiment to see what happened and, while it's certaily better than the poor "exploding girl" of the second picture, still has oddities. 

The upside - if I load a V4 from the content library and apply the Morphs++ to her, the model seems to work flawlessly. It's just the matter of curiosity as to why the pz3 import doesn't work well, I do plan to switch over to Genesis if I decide I can stand DAZ's interface - it is NOT growing on me at all, but at least I'm starting to know where things are.