hborre posted at 10:03 AM Tue, 27 September 2022 - #4445357

It is not so much as Poser is able to use DAZ figures, it is DAZ not interested in providing any further investment into Poser portability.

Why do you think DAZ should care that a competing software is compatible with their products?

For your information: There is a converter to export DAZ figures to Blender. This works perfectly. With all the bells and whistles. Also textures/materials. DAZ thinks it's ok and doesn't do anything about it.

There are two converters: One from DAZ itself and one (IMHO much better and more comprehensive) that is created by the user community (first and foremost: Thomas Larsson).

The converter is a Python script. Written directly under Blender, where there is an even more extensive Python integration than in Poser. Still, you could take the open source software and make a Poser converter for DAZ models out of it, running in Poser. All the hard stuff is already solved, especially the materials which are more or less the same in Poser and Blender (Cycles).

What gets a bit problematic is what DAZ calls "geo-grafting". This is more commonly used in some of the newer DAZ stuff, and should be made possible in Poser somehow as well (but the Poser programmers will have to either implement that directly, or extend the Python interface to allow deeper access to the internals).

And yes, such a converter is 100% legal. Because the converter runs on the user's machine and makes his legally purchased figures compatible to another software (DAZ even advertises that they see converting as a cool feature).

adp001 posted at 1:43 PM Tue, 27 September 2022 - #4445364

What gets a bit problematic is what DAZ calls "geo-grafting". This is more commonly used in some of the newer DAZ stuff, and should be made possible in Poser somehow as well (but the Poser programmers will have to either implement that directly, or extend the Python interface to allow deeper access to the internals).

And yes, such a converter is 100% legal. Because the converter runs on the user's machine and makes his legally purchased figures compatible to another software (DAZ even advertises that they see converting as a cool feature).

I recall Cage saying geografting was possible in Poser, but I don't recall it it was here or in a now dead forum. It is basically a geometry switch, albeit with a separate figure.  It does work on Genesis 1 and 2 figures brought into Poser via the Late Lamented DSON Importer.

As far as conversion goes, it could be a matter of converting one text file format to another.  I think the trick would be incorporating all of the morphs referred to in the base .duf file...

WandW posted at 7:20 AM Fri, 30 September 2022 - #4445554

adp001 posted at 1:43 PM Tue, 27 September 2022 - #4445364

What gets a bit problematic is what DAZ calls "geo-grafting". This is more commonly used in some of the newer DAZ stuff, and should be made possible in Poser somehow as well (but the Poser programmers will have to either implement that directly, or extend the Python interface to allow deeper access to the internals).

And yes, such a converter is 100% legal. Because the converter runs on the user's machine and makes his legally purchased figures compatible to another software (DAZ even advertises that they see converting as a cool feature).

I recall Cage saying geografting was possible in Poser, but I don't recall it it was here or in a now dead forum. It is basically a geometry switch, albeit with a separate figure.  It does work on Genesis 1 and 2 figures brought into Poser via the Late Lamented DSON Importer.

As far as conversion goes, it could be a matter of converting one text file format to another.  I think the trick would be incorporating all of the morphs referred to in the base .duf file...

Geografting is only easy to implement at first glance. But because of the fact that the mesh gets additional vertices (and others may be omitted), the vertex indices do not fit anymore. This has to be corrected in a separate run, so that e.g. morphs, magnets and weightmaps work again.

Not unsolvable with Poser Python, but a few additional methods to Poser internals would simplify the process.

Collecting the morphs from the duf files together is not a difficult task. Everything is plain JSON. And, as I already wrote: In the existing converters all possible problems are already solved. You just have to make it compatible with Poser (instead of Blender). And this is really not rocket science.

Y-Phil posted at 10:05 AM Tue, 27 September 2022 - #4445359

gwp posted at 9:19 AM Tue, 27 September 2022 - #4445353

If someone came up with a version of Poser that could use the newer Daz figures natively, without complicated work-arounds, I would be happy to buy it, because I still prefer Poser's interface to Daz Studio's, but I don't think this is very likely.

I understand you, honestly, even though there's an upcoming Dawn2 that will very probably be must-have.
But I sincerely doubt that you will simply import a recent Genesis to Poser, from 8 on this will become harsher and harsher, if this will ever possible. Especially with the new G9.

Looking forward to Dawn 2.

Riversoft Arts has a pair of scripts that will allow you to move G8 figures back to the G3 mesh.  Lots of folks buy it. 

AFA G9 - it's a solution in search of a problem.

I have a large amount of $$ invested in Poser content, both from Rendo and Daz.  This a little bit from time to time over a decade. It adds up. A lot is V4M4.  I liked the ability in Poser 11 to reduce facets and make groups of static props out of figures. You could make big crowd scenes.  I still mostly use P2014, however. A lot is because I am not dependent on Renderosity to keep it from shutting down like in Poser11 and 12. When my Poser11 shuts down periodically I have to scamble. So I "backport" items from Poser 11 to Poser2014.

Why should I continue to buy content if it is going to become unusable in a few years?   Shouldn't the software be the  reason for artists and vendors to invest in content?