I use Genesis 2 in Poser quite frequently. I also use the HD versions in Poser. So the idea that DSON importation doesn't work is just a myth. To be sure, it doesn't work well on lower end machines. The HD Genesis 2 models, set a subdivision 3, will cripple a slow machine or one with too little RAM. But that's not a limitation inherent to the format. I remember V4 being hard to load on a slow machine when she first came out. But if your machine is actually designed for 3D work, then DSON imports work fine. I have no problems with them. So I absolutely support vendors who choose to create for Genesis and Genesis 2.

I do vaguely wish that some DS only items came with Poser CFs if only so that I would know before purchasing that the meshes actually load in Poser (as some will not work at all). The materials I'm quite happy to fix up myself.

Maybe vendors like Sickleyield could do a quick test and just make a note in the readme as to whether or not the meshes can be imported into Poser -- even if they as vendors have no intent on supporting that method? Recently I bought the M4 versions of an outfit from SY when I would rather have bought the Genesis versions -- except for my uncertainty as to whether or not they could be imported. [I did buy some similar ones that had Poser CFs, as well -- SY's a very fine creator.] A simple nod to say, "Yes, they work in Poser, but you're on your own if you try it," would have been sufficient to persuade me to buy them. :) Just a thought.

Edit: I want to add that I do understand the hesitation -- because what a headache if some customers take a warning in a readme that Poser works but isn't supported to mean that use in Poser should be completely error free and easy! So I get why even that might be a problem. (All I wanna know is whether the mesh will explode or not. :))

---

PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.