On morph injection, I understand the arguments for and against, but I think more would agree that the concept is great, however the first/Daz implementation is somewhat limited. Consider this: First do not use :1 in any figure, including clothes, as suggested by lesbentley earlier in this thread (i.e. be FII compliant). So more that than 1 injection character can be used in a scene. Don't implement with the "2-level" readscript files that Daz uses. I don't have the details to hand, but Migal and lesbentley have posted the details several times on PoserPros. This won't save much space, but halve the number of disk I/O's - and thus the time - to inject. Skip all the unhide parts of the remove files, again just extra I/O & time. Don't over do the number of injection files. Having every one of the morphs in a separate .pz2 file is anal. Sensible groupings would save lots of time. Best option, have them both ways, then groups can be used when developing a character, but individual ones can be used for injecting characters to truly minimize disk file space. Incorporate routines - Python a la svld's new tool - to build the final injection character but using individual injection morphs. Daz's injection builder produces a file full of "fluff" (0 morphs), and is way too slow and clumsy done as a stand alone, which needs updates per character to stay current, which shouldn't be necessary. Done well, readscript base injection should work for us, not make us jump through procedural hoops. As to the original question: Yes, but please make it a unisex base, a la the old Free Market Family idea - including the FOSS aspects too preferably.