Quote - > Quote -Also, the DSON importer just imports the figure. Because it is not native to Poser you really can't do development with it, hence the issues with GoZ. That has to be done in DS, so it's probably not going to fit your workflow.

I'm not sure what you mean by this, Male_Media.

Ok this gave me an excuse to get Genesis into Poser. A quick 30-second test proves Genesis sculpts just fine in ZB via Poser's GoZ. Attached pic: Default genesis on the left, quick zb sculpt on the right.

aldebaran - the method I gave should work. Glad you understood what I meant (been up over 30 hrs now so brain is a bit fuzzy).

Now, getting a custom morph back into D|S from Poser I'm sure would be a different challenge, but if you're just using Genesis in Poser, then there should be no problem. 

I don't know what it would entail if you wanted to try sharing anything you did in Poser though. For that I would use DS, though I'm sure there's a way, just takes enough digging and experimenting.

~Shane

I'm sure you can go-z it back, however if you plan on distributing it or incorporating it into genesis, you'll have issues as Poser does not write the DSON notification needed for it. So you can save it out as a cr2 or possibly use it in the scene file, but without the tools to save that morph back into a dsf file so the DSON importer can read it, you just have an orphaned morph... which is why I said you really can't do genesis development in Poser.