Well we can agree to disagree :)

DAZ Studio has zero support for Poser beyond things that were Poser 4 based.  Everything beyond that 1999 standard has forked:

mc6/mt5 extensions not supported, nor the material folder at all.  Therefore, those that design for both platforms have to either produce double-material files or completely ignore mc6/mt5.

No support for Poser Shaders and instead DS has it's own shader system as well as Shader Bricks.

Uses it's own dynamic cloth system.

Sticks with ERC (and in fact uses some Poser 3 ERC tricks.  I can show examples.) instead of encorporating any kind of support for Dependent Parameters.

And this is only a few things.  There are several that add up to a ton of differences between the programs.

DS could have brought in Python support if they wanted to.  It's freely open source and fully integratable.

DAZ chose to instead stick with their own developed or adopted technologies, so it isn't just about Smith Micro not playing ball.  They both, certainly, have a right to do so.

Quote - I'll have to completely disagree. DAZ wanted from the beginning for Poser to have full support for Genesis. DAZ provided a way to get full functionality for Genesis in Poser without using a DAZ Studio pipeline, Smith Micro chose not to use it. I admit Smith Micro chose not to for a legitimate business reason. But to say that DAZ has chosen to only offer support through DAZ Studio is wrong. Without the functionality DAZ offered Smith Micro, Poser simply isn't capable at this point of using Genesis to it's full extent.

 Coldrake

Kind of a case of he said, she said.

Smith Micro said this:

"Many ideas, even some of the interesting ones, come with a consequence, and sometimes those consequences are too dear to accept. This is the case with fully adopting the new Genesis system from Daz. There are some good features in their new system, and those that make sense to us, are supported in a way that would benefit not just Daz, but the whole ecosystem of content developers. Those that do not fit within our strategy of an open system, free from dependencies on technologies that are beyond our control, aren’t in synch with our long term goals for growing Poser. Directly supporting the Genesis system does not meet those needs. However, doing our best to support the features that Genesis can provide to all Poser users is clearly beneficial."

Direct link: http://blog.smithmicro.com/2011/08/11/poser-3d/support-for-3rd-party-character-systems-in-poser/

I'd honestly like to read your source information as well because I haven't been privvy to all this inside knowledge :)

Sorry, but it IS a choice DAZ has made because it's obvious that it's how things are right now.  It is not possible to even look at the Genesis .obj without DS4 being installed... I know as a content creator that all those missing things could be accomplished or approximated within Poser.  I have working experience and product releases that dip into dial control and manipulation, morph target moving via deformers, etc.  It could be automated with a little effort.  Citing things like "Metadata" is reaching for incompatibilities, IMHO (i.e. an excuse).

Poser is not capable of using Genesis, as is.  But the figure could be redefined as a Poser model and supplemented with scripts and things of that nature.  There's nothing stopping DAZ from utilizing Poser as a tool for this, is there?

.