We know the integrator value has been driven to -0.17 in the case of joystick held but to -0.0149 in the case of joystick not held. For that to happen, the error must have been non-zero at some point in the past.
The error is computed like this:
- Code: Select all
<fcs_function name="systems/vectoring/pitch-rate-error">
<function>
<difference>
<property>velocities/q-rad_sec</property>
<product>
<sum>
<product>
<property>fcs/elevator-cmd-norm-css</property>
<difference>
<value>1.0</value>
<property>systems/ap/launch/autolaunch-pitch-channel</property>
</difference>
</product>
<product>
<property>systems/ap/launch/pitch-cmd</property>
<property>systems/ap/launch/autolaunch-pitch-channel</property>
</product>
</sum>
<value>-0.2</value>
</product>
</difference>
</function>
</fcs_function>
We know that systems/ap/launch/pitch-cmd is zero. We know systems/ap/launch/autolaunch-pitch-channel is 1. We know it should always have been 1 because it is initialized to that value in SpaceShuttle-common.xml.
The stick command is only felt via fcs/elevator-cmd-norm-css (as it should) - but that is multiplied with (1 -systems/ap/launch/autolaunch-pitch-channel) - which is to say, with zero.
So about the only explanation I can think of is that we're seeing a buggy initialization sequence (like in the case of the brakes) - the functions are run, but the parameters are not yet set and default to zero.
Now, if that is true, the stick should not do a thing if you pull it after the splash screen disappears and the Shuttle sits on the pad (basically what I can do with the mouse or keyboard). It should only affect the integrator when you do this during the whole splash sequence.
Could you verify that - and if it works out, make a post to the mailing list (sadly, I'm temporarily out since my internet provider has issues with its webmail interface that doesn't connect to a mail server properly, and the backup mail server I'm using gets blocked by the list because of a spam history...)