It's not the 'readScript' calls that are the problem.  These just facilitate the morph injection/removal process and only unhide/hide existing dials and inj/rem the morph deltas.  The important data here lies in those hidden morph dials used for morph injection.

The fix up for V4.1 is a way to avoid contention between different morph products using these hidden morph dial banks.  In the older versions, there was a fixed set of morph dial banks for morph injection and sometimes two different (or several) morph product creators used the same morph dials from the fixed bank.

When you get one of these new ExP morph products, you run the DAZ script and it writes a unique bank of hidden morph dials for that morph product so that you can inj/rem morphs and there will never be contention.  Without running that script, injecting the morphs in Poser will fail (no dials, no morphs).

The DAZ script actually writes targetGeom channels (morph dials) into the V4.1 CR2 to do this.  But any other version of V4.1 you have laying about - in a Poser scene or saved as a new figure into the library - is not updated.  You load the Poser scene and there is no way to inject any newer morphs - because the DAZ script hasn't added the required morph dials (targetGeom channels) to the V4.1 in the Poser scene (!).

When Poser loads the Poser scene, it doesn't reference the figures in the library so any changes to the library figure (CR2) are not transmitted to the figure in the scene - despite the similarities otherwise... ;)

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone