Olympia doesnt load genesis 2 female morphs in poser
![ISIKOL](https://farnsworth-prod.uc.r.appspot.com/forums/uploads/userpics/860/nE8A18371CEAA.jpg)
Hello There...
today i bought at the same time Olympia and the female morphs bundle for genesis 2.
when i load Olympia at poser pro 2014 the morphs are there but they dont change her shape when i dial them...
any thought on what is happening?
thanks!
p.s. have poser pro 2014 with all the updates...
Comments
and after some tries, neither does fenesis 2 female loads the morphs...
its the first time im using genesis 2 in poser...i have the latest dson installed by the way...
edited...
well..i managed to fix it..but in an odd way...it seems that if you install olympia first without having installed the morphs bundle for genesis 2 first...it doesnt work...
i deleted all the runtime and started progressivly...first the genesis 2 bundle and then the morphs...and after that the characters...
Daz people maybe you should look into this...
Are you sure you hadn't installed the morphs to a folder that was selected as a DAZ Studio content directory in DS but wasn't selected as an external library in Poser?
Hello Richard...yes im sure..i keep only one external directory for all my genesis stuff...
im trying to find a logical explanation on why did that happened, but i can't..
i didn''t have any issues with m6 and his morphs bundles...
either im unlucky or something is going on...
im lucky though cause it took only a few minutes to reinstall everything in the right order...
something coflicts and doesn't update genesis 2 with the morphs...is my guess...
When you load Genesis it reads in all of the available morphs (or at least, it should).
Richard im aware of that :)..i wish there was someone who would duplicate that...it would be interested to see what went wrong...
All this drawbacks make me having second thoughts on using Genesis in my main workflow...and trust me when im saying that i want them to be a part of it.
If you uninstall and reinstall in the wrong order do you still get the same issue? if so I would report it as a potential bug - report it as a DSON issue.