I'm looking for documentation on how to use Poser readscripts to inject custom morphs for a digitigrade package that I am working on. If anyone can help me with this problem or direct me to a tutorial with the information I would be very grateful.

Attached Link: http://www.rbtwhiz.com/rbtwhiz_rScript.html

Robert Whisenant is responsible for bringing Poser's ReadScript feature into everyday use, so his tutorial should be the best place for the nuts and bolts. Most of the higher level tutorials deal with making INJ and REM poses for existing characters which already have the channels, so are probably not what you need.

I haven't used readScript much, so I'll stand to be corrected by the experts, but this is my take on it. When readScript is used in a pz2 file it is a way of calling a number of diffrent pz2 files and applying them all at once. Say for instance you had a Delta Injection pose "MyBody.pz2" that shaped the body, and another that shaped the head "MyHead.pz2", instead of having to load each pose seperatly, you could use a pz2 with readScript to add both poses at once. Here is an example of a pz2 using readScript:

{
        version
        {
                number 3.00
        }
readScript ":Runtime:Libraries:Pose:Sam:Inj-Sam.pz2"
readScript ":Runtime:Libraries:Pose:Sam:EXPRESSIONS1.PZ2"

figure
        {
        }
}

I use this file on a Posette that is modified to have some empty targetGeom channels in each actor. "Inj-Sam.pz2" is a Delta Injection pose that adds body and head shape morphs, "EXPRESSIONS1.PZ2" is one that adds a set of facial expressions. The point is that rather than having 6 Delta Injection poses on HDD each also containing deltas for facial expressions, I only need one pz2 containing the expression deltas, and 6 read script poses, each calling diffrent character morphs. This saves a lot of HDD space. So readScript is an easy way mix and match pz2 files. One drawback of using readScript is that the poses that are being called must be in the expected location, if the user were to move the pose files or install them in the wrong location the readScript would not be able to find them. Also remember that a pose file can only inject code into a channel that already exists in the target cr2. Some points regarding the Delta Injection poses you are calling, I always include a 'figure' section at the end of the file, as I find this helps the paramiters pallet to refresh. I do my delta Injection poses diffrently from DAZ, I stripp out all the actor numbers (:#) from the file, and if there is any slaving code in any of the channels I replace the 'Figure 1' line with 'NO_FIG', I must be doing something right bacause I hear that if you use DAZ injection poses on a figure that is not the first figure loaded you sometimes get problems, and I don't. This is an adaption of an idea by Maveris, in this thread: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=1431670 Message edited on: 12/23/2005 13:02

A couple of comments: One thing to remember about the readscripts is they more-or-less are just a way to run a pose by remote control, the only advantage I see to them is by convention the pose folder only contains small files, injector files can get very big. So, it is a good idea to follow Robert Whisenant's lead and make your injectors run remotely (I always put mine in the !DAZ folder, BTW, even Glamorous Jessi's, I see no need to make even more library folders). However, I see no need to run the REMovers remotely, lik eDAZ does, they are only small files, why build in extra complication. I also do as lesbently said, and make them numberless, I think this is important. I don't use "NO-FIG" though, I just have a line "Figure". I think Jaager first suggested this setup.