Hmm...

SubD: Where were we before SubD?  I really don't find this to be the silver bullet in the ultimate posing solution but it seems to be touted a lot.  If there are enough polygons in the shoulders (for example) and enough density and correct contouring in the areas that fall along the bends, does this not achieve the same thing?  Depending on how low poly the mesh is and the system used to provide the subdivision, this can actually add density and remove detail by over-smoothing then you have to rely on mapping for detail.  To me, this is fine for a game engine.  And yes, I am very familiar with smoothing "cages" in modelers that are driven by subdivision but I find them to be a better tool to flesh out a basic shape and then build upon that.

Auto Morph Generation: Already have several solutions there.  Morphing Clothes, Wardrobe Wizard, Cross-Dresser, etc.  Of course it isn't particularly "automatic" and in some cases requires some kind of modular "add-on" in regards to getting the morphs in there.  Alternatives: Deformers could be created to easily provide approximate morph shapes in clothes (I have done this many times).  As far as auto-morph movement (dial matching) it can rather easily be Python-driven.  In fact the entire Deformer/Auto Fit scenario could be Python-driven.  So, the tools are already there just not tapped into.

Smart Content: Pretty much irrelevant as DS uses a separate database system, which I don't think everyone gives two squats about (some, not all).  However, not only are Poser's metadata files human readable, there is an xmp editor included with Poser.

Dynamic Morph Loading: Hmm... not exactly sure what this means? A morph delivery system?  Can be:  Injection Slot driven, .pmd driven, readscript injected driven, python driven, etc etc.  This is really a non-issue.

Here are some thoughts:

Much of the antiquation of Poser technology has been to try and bring a balance between DS and Poser.  We have had to settle for ignoring much of Poser's technology to reach a common ground by using "Poser 4" features so that things can work in both programs.  If we were to simply allow DS to split off, we can build on Poser's strengths.  It's a catch 22 with content development though.

DAZ is making an effort only as long as the trail leads back to using DS4.  This is not an optimal or desired situation for everyone.

Releasing a V5 stand-alone for Poser will fork content support and is likely why it will not be done.

My personal thoughts is that this is less about giving back to the community or making an effort to support Poser and more about control and a requirement to keep DAZ Studio in the pipeline when using Genesis/V5.  If I am 100% wrong here, then there's no reason not to release a Poser only standalone of V5.

As far as alternative figures go, I am willing to give it my best effort.  I ask myself first: "What can I do?".  Trying and failing is not an issue and shouldn't be.  Not trying is the real issue.

I hope none of this comes across as being combative (and it isn't the intent) but I have to admit that I'm very weary of the whole "it can't be done", "you will fail" kind of rhetoric.  To me, the glass is always half-full.

.