A revenue stream that might be of value is LOMAC with a joystick.
#Keyboard command for bullet point on pc software
And especially recommended key mappings.Īnother pathway that you see with graphics cards is the bundling of software with the vidcard. In reading the provided LOMAC documentation, there was no introduction to joysticks. On a wider level, how would we introduce the new user to the idea of buying a joystick. I don't know if LOMAC is mapped with CAPSLOCK taken into effect. Or CAPSLOCK sets it at A0 and CTRL-CAPSLOCK toggles the sim speeds A16, A8, A4, A2 and A0. What ever happened to Capslock? Rapidly toggling between sim speeds A16, A8, A4, A2 and A0 would be cool. The TAB key is for me the preferred method to access the Comms menu - that may be the IL2 experience talking though but I like the close proximity of TAB and F1, F2, F3. I would prefer Backspace as the target switching button as it's very close to the TDC arrows and the Designate/Undesignate. The TDC skewing with cursor arrows would designate the target on the Radar screen by proximity of the next target to the TDC cursor. On my current simple sidewinder I've 1 button that Designates and UNdesignates. You should look at the idea of making the UNdesignate key also the Enter key.
(6) Make the Backspace key "Undesignate Target". (5) Move the "Designate Target" key from Tab to Enter. I'm sure this has been hashed out before, but I thought I throw in my two (imaging my frustration when for years, simming with USĪircraft only, then to give a Mig or a SUE a shot. We practically have to self tutor ourselves as it is when trying out aĭifferent craft. Wouldn't be better to have a unique keyboard set for each aircraft? It's challenging to produce a "unified" layout for many different aircraft with the available keyboard controls.īut given the amount of complexity of each aircrafts controls and avionics, The F-15 controls are quite different in detail from F-16 (no Dogfight or Missile Override switches), let alone Warthogs, MiGs and Sus. :(įrom what I've found though, F4 can take such an approach more easily than Lock On, because it models only one aircraft. The more I ask about this, the more people I get into trouble for helping.
I'm interested to know if any important commands were missed in this proposal, so feedback is welcome.Īargh. This evolved out of the "F-15 avionics" sticky discussion, where it became apparent that the Tab "lock target" key would not be sufficient for manipulating multiple TWS bugged targets, but I decided to start a separate discussion, since the subject involves padlock, communications, view controls and many other non-avionics-related themes.
To help resolve these conflicting requirements, I'm writing a proposal for a different keyboard command layout to be used in the future: At the same time, we hope to make the avionics more sophisticated. We would like more players to join our community, but an awkward user interface can aggravate the already steep learning curve barrier. As flight simulators become more advanced, the keyboard user interface is becoming ever more crowded with commands.