Okay - first up, I'm not bashing anything. I used the Genesis figures and clothing as an illustration, not as the point.

The point is that Poser needs something like this. Sure, you can get the same results - with external apps, more time spent by the user, and a more convoluted workflow, but... why? Why should that be necessary?

Please don't dodge it by saying that software development is hard... I smack around code for a living as well (and simple/fast collision detection functions have been around since the days of DOOM, for cryin' out loud! And before you say it, we've got enough horsepower these days to get past the bounding box.)

Yes, SM has to balance features against ROI - so does everyone else, but most of them seem to do it well enough... So tell me: where would you not see an increased level of customer interest in having an in-app simple (to the customer) means of utilizing nearly every bit of clothing made in the past frickin' 12+ years (or more) for your default figures? Maybe expose the API so that folks at, say, HiveWire could add definitions to it to allow clothing fits to the Dawn and Dusk figures? Opens up a massive pile of good stuff for the customer, and since SM makes its money from the application (and not really from content)? Not like I'm asking them to supply a free MacBook Pro with every purchase here, and they'd see ROI fairly quickly from it, from newbie and old hand alike.

Sure, I could ask SM directly, but they likely already know about this, and I think they can hire who they need to. So what's holding them back? I've given my theories earlier; I hope they change their minds.