Kobalt:

Quote - no, that's what i mean.  it does not do that.  S4 writes that line. 

Right, and the updater is invoked as part of the installation unless you force it not to run (which I've never tried actually and I'm not going to do).

Quote - no, the cr2 is not updated.

Right also, I see it working that way as well.  The CR2 relies on readScript commands so it can remain generic - it's the files that are called by the readScript commands that are changed when you install an update.

Quote - what i don't understand is why this would mean you need to update the base at all.

It's not the CR2 that gets updated - and I realize this contradicts what I've said before, I'm sorry.  I was guessing how it worked, now I'm pretty sure I understand it correctly.  Actually the CR2 might get some kind of update, if some JCM/JSM is modified between updates, but I think DAZ would go back to the base V4 install to add that kind of thing.

Quote - anyway, i managed to add all the morphs without having any of the Version 4 morphs or scripts in my main runtime.  i just tried loading them, to see what would happen, and it worked.

This is because when you load in the DAZ-written CR2, the readScript lines are read, which calls those various *.pz2 files and silently creates all the channels and group nodes for you,  When you save a new CR2, the channels are written into the CR2 and there are no readScript commands any more.  When you run the various DAZ INJ poses to load the DAZ morphs, these will un-hide those channels and load their deltas.  For third-party INJ poses, like some of the ones I've done, they may also change the friendly name (the name that shows up on the Parameter Dials, not the internal name.  I might be misunderstanding what you mean, but this makes perfect sense to me.

Still a bit mystifying why it should take multiple tries to get the updater to do its thing, I can only blame crappy programming there.

My Freebies