JAG opened this issue on Nov 10, 2019 ยท 61 posts
JAG posted Sun, 10 November 2019 at 1:34 AM
I just came in from the cold with regards to Poser Pro 11. Up until last week I was still using Poser Pro Game Dev 2014. I loved it. It no longer works now. I'll frown and move along.
In my previous and wonderful version of Poser, I could GoZ with no problems whatsoever. Click, morph tweak in Zbrush, click and my figure is back and morphed successfully. Of course you could only export the figure in zero sub/base resolution. Now Poser Pro 11 allows export to Zbrush with the higher resolutions and you can bake your morphs and this is great. I love that. But...
I use Genesis 3 in Poser. I never had any issues with her in PPGameDev2014 doing this. But now in PP11, I can get her into Zbrush one time and get an awesome morph accomplished at zero, 1, 2, or 3 subdivision levels and bake down the morph and save her. All is great. Wonderful. But if I try sending her to GoZ a subsequent time to tweak something or smooth something, when the morph comes back it goes wonky. Sometimes it's only a single polygon that shoots off into random positions and sometimes whole figures blow. Why does it work once but then never again? Also why is it every single time that I send a figure out, it renames it and makes it a new tool in Zbrush. Previous version did not do this.
I have tried GoZ with both bake and no-bake, materials and body parts. Doesn't matter. Higher poly settings are messed up after the first run. I once brought a morph back and named it the same as the first morph (which of course replaced the first morph) and that actually worked, but I've lost my original morph and so that's bunk. I've even had some of this happen using nothing but zero/base resolution setting. What the heck did they do here?
Any help or suggestions appreciated - but PLEASE READ MY ENTIRE POST before you post a reply. I don't mean to be a so-and-so here, but I hate when people suggest things I've already tried. It's redundant and a waste of everyone's time. So please read before replying. Thanks.