I have also been trying to stay out of this thread as it seems to me not a lot more than an extension of the software wars that have boiled over around these forums for so long and that Renderosity has worked so hard to stamp out in the interests of a cohesive community that supports many different artists, platforms and content creators.

Firstly there seems an ideal solution that no one seems to want to touch. Why does Smith Micro not work to make Poser support DS content? It seems like a win win to me. Daz 3D sells more content to a broader market. Poserphiles can use their preferred platform with access to a wealth of content that grows larger everyday. I really cannot see the negatives that many seem to conjure up for this outcome? Each businesses marketing strategy is clearly complementary and not competitive. Why are you asking many vendors to shift their focus instead of asking SM to provide broader compatibility with their platform that you are paying for? I really don’t understand. In the past I have been told by many dedicated Poser users that ‘Poser users don’t need content as they prefer to make their own’. But I see thread after thread begging for that very same content…

As far as the idea of making a Poser product first and then porting to DS as an ideal. There are so many DS functions these days that are not supported within native Poser file types. It really makes no sense for someone who is targeting the DS market to create a product for a different application and then wrangle it into DS with limited capabilities to keep an entirely different market sector happy. Surely the best DS products will always be made native to DS and take advantage of the advanced features within DS such as Instancing, LAMH, Geografting, Geoshells, Dforce, Iray shaders, Genesis 8 figures etc,etc. As would the best Poser products be made native in Poser. Until there is some parity in platform compatibility, there will always be a growing division in content support.

Also there are no real clear reasons to include .obj files in products when DS is free and can export many different formats with various options including obj, Collada, Poser Cr2 files, fbx, u3d. And if for some reason you do not want to install DS there are 3rd party stand alone applications available that can extract .obj data from daz native files. Where is the value in adding extra work to each vendor and larger demand for product file storage for Renderosity and other markets, in a process that can be completed by the end user to a greater degree of accuracy to requirement in just a few seconds? I'm sorry I also do not understand this request.

Personally, I find it a little humiliating to see vendors needing to declare their fealty here to the Poser overlord or risk the wrath of the purists who cannot understand why a content developer needs to adapt and progress in their own art and creativity to thrive and to continue to be a success. Why that very act is healthy and normal, not some kind of betrayal. Some members in this community have continued to reinforce a rift between the DS and Poser community for far too long with no positive outcome as can be seen by threads like these. Maybe it’s time for some to consider a change in tact? How about asking Smith Micro to add a broader level of support to the platform that you are paying for. Seems to me this would be the ideal solution to the issues presented here. Or am I missing something?

Just my 2 cents.