fly/A320-family
1
0
Fork 0
Code Activity

Remove the broken thrust lever bindings.

Browse source 
The binding say they are for PgUp/PgDn, but `n="33"` is `@` and n="34"
is `"`. I don't think they should be moved to the described keys because:

- The default bindings is what is being used and they work OK.
- When I switched them to `n="360"`/`n="361"` and tested it, the right
  thrust lever lagged behind the left one when moving out of detent. It
  does not do it with the default binding.
- The bindings break the engine selection logic (both now, because `@` is
  select engine #1, and if moved to PgUp/PgDn, because they don't respect
  the selection), which can be useful for handing engine failures, and
  to which pilots are used from any other aircraft type.

So just remove them.
This commit is contained in:
Jan Hudec 2020-02-15 20:15:31 +01:00
parent d47b3431d2
commit 95425e23a1
1 changed files with 0 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
A320-main.xml
View file

@ -1451,28 +1451,6 @@
<script>libraries.fovZoom(0);</script>
</binding>
</key>
<key n="33">
<name>PAGE UP</name>
<desc>Throttle Increase</desc>
<binding>
<command>nasal</command>
<script>
setprop("controls/engines/engine[0]/throttle", getprop("controls/engines/engine[0]/throttle") + 0.01);
setprop("controls/engines/engine[1]/throttle", getprop("controls/engines/engine[0]/throttle") + 0.01); # Not a typo, always use engine[0] as a reference
</script>
</binding>
</key>
<key n="34">
<name>PAGE DN</name>
<desc>Throttle Decrease</desc>
<binding>
<command>nasal</command>
<script>
setprop("controls/engines/engine[0]/throttle", getprop("controls/engines/engine[0]/throttle") - 0.01);
setprop("controls/engines/engine[1]/throttle", getprop("controls/engines/engine[0]/throttle") - 0.01); # Not a typo, always use engine[0] as a reference
</script>
</binding>
</key>
<key n="49">
<name>1</name>
<desc>Captain View/Elevator Trim Up</desc>