Hi Gang,

I was having problems with some recently installed Genesis 2 presets and morphs not working, and as I was finishing up typing the problem up below, I realized that folks have had similar issues with V4 and M4 when there were multiple installations. I hunted around my Library and found multiple DSON auto_adapted folders. While PP 2014 apparently doesn't mind, (the Library Search is set to Deep on both) it caused problems in Poser 11 Pro. Getting rid of the surplus ones by moving them to an unmapped folder solved the problem (I saved them in case I have a saved scene that might need something) The correct one is of course in the Writable Runtime in Scripts>DSON Support> Importer Preferences. If you have multiple versons of Poser, consolidate them to one location.

Below describes the symptoms...

Due to a recent sale, I picked up some Genesis 2 morphs and characters and, while they work fine in PP2014 and in Studio, I'm, having problems in P11 Pro;

When loading certain preset characters, such as Ysabeau 6 or Monique 6, Joanie HD, the figure loads at the default shape, and the morph dial corresponding to the preset does not work. However, if I bring in, say, V6, it loads fine, and I can dial V6 to zero and dial in the Joanne or Ysabeau morph without a problem.

Also, I picked up Zev0's Growing Up morphs for the Genesis 2 Male and Female, and they work fine on the Male, but only the 'Youth' dial works on on the Female, and I think it's scaling rather then a morph.

I've recently started using DS4.9Pro, and am still a hardcore Poser user. I have done the PoserCF conversions etc etc and have used the DSON utility blah blah. I agree that over time, the DSON conversion folder(s) and runtimes can get untidy.

Another way is to simply export your genesis content out as Poser native, and ignore DSON.

?

ssgbryan posted at 7:48AM Wed, 16 March 2016 - #4261250

Another way is to simply export your genesis content out as Poser native, and ignore DSON.

I bring them in via DSON, and Poserize them this way, ignoring the "speed" part...

https://www.renderosity.com/mod/forumpro/?thread_id=2874212..

WandW posted at 11:28AM Wed, 16 March 2016 - #4261352

ssgbryan posted at 7:48AM Wed, 16 March 2016 - #4261250

Another way is to simply export your genesis content out as Poser native, and ignore DSON.

I bring them in via DSON, and Poserize them this way, ignoring the "speed" part...

https://www.renderosity.com/mod/forumpro/?thread_id=2874212..

How did you keep the correct UVs on the figures? I have saved out a couple dozen characters and not a single one kept the correct UVs - genesis 1 would revert to Gen4, and genesis 2 would revert to genesis 1.

ssgbryan posted at 9:39PM Wed, 16 March 2016 - #4261383

How did you keep the correct UVs on the figures? I have saved out a couple dozen characters and not a single one kept the correct UVs - genesis 1 would revert to Gen4, and genesis 2 would revert to genesis 1.

JP tells how in the thread; I messed up the link above with an extra period. This one should work:

https://www.renderosity.com/mod/forumpro/?thread_id=2874212

You have to load the desired UV set, then export the .obj and point the cr2 to it after fixing the grouping. You end up with a bunch of .objs, one for each UV set...

WandW posted at 10:41PM Wed, 16 March 2016 - #4261440

ssgbryan posted at 9:39PM Wed, 16 March 2016 - #4261383

How did you keep the correct UVs on the figures? I have saved out a couple dozen characters and not a single one kept the correct UVs - genesis 1 would revert to Gen4, and genesis 2 would revert to genesis 1.

JP tells how in the thread; I messed up the link above with an extra period. This one should work:

https://www.renderosity.com/mod/forumpro/?thread_id=2874212

You have to load the desired UV set, then export the .obj and point the cr2 to it after fixing the grouping. You end up with a bunch of .objs, one for each UV set...

Point it to the .cr2

Aha!

That is what I wasn't doing. Thanks, I'll try that again and see how it works.

A related but different question - (minor hijack of this thread) - does DSON work in Poser 11 PRO "as well as" it works in Poser 2014 PRO? (I'm not asking folks opinions of DSON! Some love; some hate - different topic.)

I so far haven't upgraded from 2014 to 11, in part because i didn't see any new features I wanted, and also because I feared SM may have hampered DSON by accident (or carelessness, or even on purpose). However, if G3F can work in PP11 DSON, then I'd have a reason to consider upgrading. Still might not. With V4/Aiko4 and G2F/Callie6, I have far too much content to honestly want to buy more ... ha ha - famous/foolish words!

On topic, I'd probably delete my PP2014 is PP11 was working, so hopefully less cross-talk. Anytime I want 'legacy', I still have Poser7 installed for checking PZ files, etc.

So far the Importer seems to work well in P 11. Panning with the camera seems a bit faster than with PP2014, but posing is about the same.

I'm using the last Importer beta, 1.1.3.49, because the current released version results in mesh distortion in Genesis 2 and 3...

Does using the DSON importer in Poser 11 still bork the library? It's the main reason I don't use P11 with Genesis products. (And like ssgbryan, I've converted most of my figs to Poser native -- but I still use DSON importer to apply poses or to test something I haven't converted yet.)

That issue was fixed with SR1, IIRC The Importer causes no issues with the Library with SR 2 and 3...