Dodger,I was not entirly convinced by your answer, a "normal" channel does not have a 'staticValue' and so must restore to the 'initValue'. The 'initValue' is not the value on load up, in "normal" channels the load value is the second number in the first keys line. I have just found that this is not necessarily so for some of the hidden channels, but channels never seem to get their load value from initValue, in any circumstaces, even if the keys block is entirly missing. I decided to do some experiments to see wether 'staticValue' was the value actually restored to in the channels that have this line, rather than the initValue as in "normal" channels. The answer appears to be no. Initial setup:

                yOffsetA originY
                        {
                        name GetStringRes(1028,45)
                        initValue 0.111
                        hidden 0
                        forceLimits 0
                        min -100000
                        max 100000
                        trackingScale 0.004
                        keys
                                {
                                static  1
                                k  0  0
                                }
                        interpStyleLocked 0
                        staticValue 0.222
                        }
        origin 0 -0.333 0 

The file was loaded into Poser 4, and the OrigenY dial changed to 0.444, then file saved to pallet. The channel now looks like this; yOffsetA originY { name GetStringRes(1028,45) initValue -0.333 hidden 0 forceLimits 0 min -100000 max 100000 trackingScale 0.004 keys { static 1 k 0 0 } interpStyleLocked 0 staticValue 0.444 } origin 0 0.444 0

Now a Restore>Element is done. The OrigenY dial now reads '-0.333'. Conclusion: The value restored is the one in 'initValue', NOT the one in staticValue! So the question is still open. What is the function of 'staticValue' and 'static'?