#Flightgear controls keyboard code
#Flightgear controls keyboard free

carburettor heat - some piston aircraft only.propeller - some piston aircraft only ⇧ Shift+ N / N.mixture - piston aircraft only Shit+ M / M.differential toe brakes left/right, /.elevator trim up/down 1 / 7, Home / End.landing gear raise/retract G / ⇧ Shift+ G.look forward/backwad ⇧ Shift+ 8 / ⇧ Shift+ 2.look left/right ⇧ Shift+ 4 / ⇧ Shift+ 6.Winch / Aerotow (begin winching, open hitch etc).throttle - for helicopters, should the same key control the collective? 3 / 9, Page up / Page down.

#Flightgear controls keyboard free

Keyboard bindings.Īs a first step in the keyboard refactoring, we need to come up with a prioritized list of functions that (a) are general enough to apply to most (or at least many) aircraft, and (b) are important enough to justify a keyboard shortcut rather than just a menu/dialog or a model hotspot.įeel free to add to the list, but please don't delete anything - just move it to the bottom if you don't think it's important.Īs we'll probably not want to change too many existing key-bindings, The current CVS key-binding is also listed in brackets. This is basically a usability discussion, so everyone will have strong opinions :) What I'd like to see is the entire 'Ctrl' (Command on Mac) space reserved for GUI functions, like a normal application - Ctrl-Q for quit, Ctrl-M for map dialog, Ctrl-A for autopilot dialog, Ctrl-R for replay dialog (or radios dialog :) - then have a complete discussion about which key-bindings make sense on The other issue is the keybindings are effectively 'full' (we can't easily add more), because they've been added and added over the years, but rarely removed, so at this point every key 'does something', but often something quite obscure. So flaps, trim, CDI/HSI heading,įine, but things to change view distance or FoV seem unnecessary to me. My *personal* feeling is that unless it's something the > 50% of users use *each flight*, it shouldn't be a keybinding.

#Flightgear controls keyboard code

My point of view is that the current keybindings file is a mess, with many historical bindings, and also it binds in the ASCII space, as opposed to the scan code space, so we can't distinguish keypad vs normal number keys, and various other combinations, even though osgViewer supports that.

Modularizing, parallelizing and distributing FlightGear.