I should say also, whilst I appreciate the various reasons why the DSON Importer works the way it does... creating a dynamic instance of Genesis, within Poser, and a more "virtual" cr2... I still wish it was capable of outputing a functioning native Poser figure, i.e. an actual cr2, referencing an actual object.

Basically I wish it could "bake" it's end result into proper Poser format...

...that is, I could, as a feature of it's design, load up a Genesis figure from the virtual cr2, dial it, select a subd level, fit clothes etc, and then save that as a functioning cr2/obj, without all the stuff I'm then not requiring for my scene, before I work with it further... posing it etc.

The above would be top of my wishlist for how the DSON Importer could ideally work, for me.

It would then be up to me what point in my workflow I did the "baking" ...and once "baked" I accept that I'd have to go back to a dynamic instance to perhaps change anything more than pose or expression, I would guess... but being able to effectively remove all the stuff I don't need that is bogging down my subsequent scene prep would be a major deal for me.

I don't think the above is entirely possible at present. Although a cr2 can be saved, I think key aspects of it are then broken? They seemed to be when I tried this previously...