EClark1894 opened this issue on Oct 19, 2013 · 489 posts
AmbientShade posted Wed, 30 October 2013 at 6:03 PM
Quote -
Most definitely. The Poser rig isn't very good from what I've seen & heard. If she worked nicely the first time I tried her, I might have been happy. I think that's what hurt her the most, with me anyway. However, the bad taste in my mouth has made a big difference. If you don't do it right the first time, it's not good especially when you've designed figures before & "know" what you're doing.
That was basically my argument with Dawn from the beginning. She's not a professionally crafted figure. She's a 1st or 2nd draft at best. It's not about her out-of-the-box attractiveness or lack thereof, as attractiveness is entirely subjective. Technical aspects however are not subjective. It either works to it's fullest potential or it doesn't. Dawn, in her current form, doesn't. At least not in Poser. It appears to me she was rushed to completion while important issues were either overlooked or just ignored.
Quote - I'd like to see an enhanced version of her. Getting rid of the 'line backer' look would make her look more Dawn & less Don. As long as they correct it, I might give her a chance. They should just do an update to the entire figure though instead of an injection. Just more to annoy the end user, imho.
I just dug up the Dawn to Danielle thread and re-read it. Basically it seems that in order to actually fix her shoulders and other rigging issues in Poser, it will "break" the pseudo-compatibility between the two platforms, which never actually existed to begin with.
The shoulder issues (and other rigging issues) with DS-based figures is apparent in Genesis as well, not just Dawn, when loaded into Poser. That doesn't mean that one platform is better or worse than the other, it just means that they are two very different platforms and therefore the end results will not be the same when trying to crowbar the tech together as has been being done with DSON and now Dawn.
I wish people would just stop trying to force the two programs to have compatible content. There's no reason for it. Build for whichever one you want to build for. If that means both then great, but accept the fact that when you try to support both equally it means double the work and beginning from the ground up in both platforms. There are no shortcuts that can be taken without sacrificing the quality of the product in the end, on one platform or the other, if not both.
~Shane