The reason why the throttle axis seems reverted on helicopters
is that it isn't actually used as throttle, but as collective.
And the collective lever is pulled to rise and pushed down to
sink in a real helicopter.
Some people don't like that, and on some joysticks with horizontal
throttle wheel (instead of lever) that's indeed not very intuitive.
The place where the axis gets inverted is in the respective FDM
config files. For example, in $FG_ROOT/Aircraft/bo105/bo105.xml
there is:
<control-input axis="/controls/engines/engine[0]/throttle"
control="COLLECTIVE"
src0="0.0" src1="1.0"
dst0="1.0" dst1="-1.0"/>
and this src-dst mapping inverts the throttle axis. One can now
easily change this to dst0="-1.0" dst1="1.0". This would have
to be done in every single config file, though, and might have
unwanted side effects.
Another way is to let the joystick invert the throttle axis back
for all helicopters. Just put this nasal code somewhere on the
top level:
<nasal>
<script>var tmode = props.globals.getNode("rotors", 0) != nil</script>
</nasal>
and in the throttle binding add tmode as argument to throttleAxis():
<binding>
<command>nasal</command>
<script>controls.throttleAxis(tmode)</script>
</binding>
This will invert the throttle axis if a /rotors/ node existed
at startup. The existence of this node isn't a very reliable
indicator for a helicopter, though, and the condition might have
to get extended.
m.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
