They're the result of working out how Poser 4 did certain things (otherwise known as "reverse-engineering") and applying all that hard work in new situations. In this case, INJection morphs are designed to save disc and memory space (and in theory time) over having all morphs constantly loaded, and without the character's end-user having to understand how to add a morph to a character. It may add some overhead to the character creator's workload, but is technically easy to use (you just point and click). You're far from alone in not being convinced that it's an improvement on using standard morphs. Poser 5 users seem to have particular problems with INJection morphs, seemingly because of the enhanced library organisation of Poser 5 (and the order it searches runtim folders). This causes INJections to be, in general, somewhat more tardy than in Poser 4's single Runtime environment. DAZ may not have been aware of how badly V3 would operate in Poser 5 before V3's release due to the politics between them and CL at the time. Users have found 3 basic solutions that I know of: 1. Install character directly to Poser5's runtime folder, and not to Poser 4 or it's own folder (Poser 5 make sit possible to have a runtime folder dedicated to a single character, or to a style/genre, or to anything you want - a handy way to organise things). Or in both P4 and P5 Runtime folders if you want to use the character in P4 as well. 2. INJect all the morphs you want in Poser 4 and then save to the library as a "fully loaded" character. This then works in both P4 and P5 and (from experience) seems to load up much more quickly than INJecting. 3. Install in P4 as per usual and then copy the P4 !DAZ folder into the P5 runtime folder. This apparently speeds up INJecting as well, and tho I have yet to try it sounds like a good compromise if you want to get used to INJecting and REMoving morphs this way.