[Raindroptheelf]Maybe Poser started it off but Daz took it a whole lot further in their development of the still FREE software Daz3d.[/quote]

FREE (not counting the numerous add-ons to get it's functionality near what Poser has out of the box... And D|S wasn't always free.

Smith Micro had their chance to go hand in hand with Daz3d but I guess they do not really want to commit to it as they do not only sell Poser...

Not quite. The Poser Team decided not to integrate Genesis into Poser for the same reason Daz Studio exists: They didn't want to be tied to the whims, mercy, and fate of another company's program.

If they had accepted, then every time D|S and Genesis got an "under-the-hood" update, then the Poser Team would have had to divert people from working on other Poser updates, or the next version of Poser, in order to put out a patch for Poser that incorporated those updates; because not doing so would tick people off, though with a side-effect of delaying the release of the next proper Poser update/version. And given that Poser generally has a (somewhat) set release schedule, with program updates only when they get enough fixes done, and D|S seems to have a "whenever Daz3d feels like it" update schedule, there would be conflicts between updating. Not to mention whether Daz would give the Poser team enough time to implement their own update before releasing a D|S one.

where Daz3d is committed to stay exciting, develop and bring out characters that will always be exciting to work with.

I disagree, Daz is all about recycling content. Just look at how many different versions of a "Morphing Fantasy Dress" there are (not counting texture sets) in the Daz store.

I remember when I first started with Daz Studio * before I gone Poser and later back Daz Studio * we had the same dilemma. No one was making things to use in Daz Studio, only a few things Studio came with and we had to convert skins of V3 to look better in Studio.

The difference then was that, aside from materials, the majority of Poser content loads, and works, as is inside D|S. From what I've heard, even with the DSON importer, the same cannot be said for moving D|S content to Poser. So it wasn't a big deal if people weren't making D|S-specific content, as the people using D|S could still use it with some tweaking.

But those people making D|S-specific content aren't making anything that Poser users can use properly. And many won't bother with DSON, meaning that they can't use it at all; or they have to put far more effort into getting it to work in Poser (and sometimes jumping through hoops is needed even with the DSON importer).

________________________________________________________________

If you're joking that's just cruel, but if you're being sarcastic, that's even worse.