Quote -
Thanks all for the info, but being a crazy bunch, you've cleared-up one curiosity and created another :-D

I thought the whole idea of Genesis is that they don't need to change the base mesh itself.  If Genesis 2 has a different poly-count to Genesis 1, then surely any morphs aren't compatible between them.  And like RorrKonn, I'm curious what the G2 stands for on the Poser figures.  To hazard a guess I'd the say the "G" stands for "Generation", but those figures aren't the second generation of Poser figures so Generation 2 wouldn't make sense.

Well there are ways to transfer morphs between the two via DS's transfer tool; it generally requires a common shape between them, but the idea about a common base is the same between the males and females. The reasong for Genesis 2 figures are 1) specific weightmaps, 2) distribution of polygons specfic to a gender while keeping the same poly count and 3) base shapes that make creation of gender specific content easier (for example trying to visualize a bra on a figure without breasts was not easy with the first generation).

But don't want to derail the V4 conversation, but going back to the ExP  (since I had to go out of town for the day), the ExP exporter tool is in DS, and though it takes a few steps, once you get the flow, it's pretty easy.

Basically you'll build your product with the morphs, any morph corrections, custom morph channels names and JCMs and save it as a CR2 (this way you can save it out again with any changes), then use the ExP Exporter to read the CR2 and save out the setup to a directory. Then you package that up so it can be saved to a runtime. Customers would just run the "Update V4" script to prepare V4 for the new injection channels.

So it could be used for bend fixes, custom characters that have JCMs, custom body shapes, emotions, etc. and not have those compete in the community injection channels where they could overwrite or be overwritten by other products.