More flexible control options

[Nereid]

Well, it's not on top of my wish list, but easy to implement: A bit more flexible control options. The options in the configuration screens are quite good but key consuming on the HOTAS (and all other auxiliary input devices) have some disadvantages.

 

At least every switch/button on the virtual cockpit should have a (optional) key command to toggle its state. In A10 this is not the case for all switches. The "Master Arm Switch" has three keyboard shortcuts for all its setting (which is great so far) but this means you have to configure three buttons on the HOTAS for that. I miss a control option that toggles the switch from ARM to SAFE to TRAIN.

 

On the other hand it would be nice to have control input that set the switch to the state of the button. E.g. Button 25 on Device 3 pressed should set the switch into "on" setting until the button is released. This could be used by other input devices that have real swicthes (switch in up position hold the button, switch in down position releases the button).

 

I'm currently building my own panel witch switches and two MFDs. But I'm limited to 128 switches at first and I have to keep other simulations in mind also. Three button or a three state switch for the "Master Arm Switch" is just to much.

 

Regards,

André

[Spy Guy]

Well, it's a bit old, but I did a search and this thread came up as a really close match to what I was looking for, so...

 

I wonder if it'd be possible to set other switches up in the same manner as those mentioned above and in Black Shark as well.

In A-10C the Master Arm switch (for instance) is set up to allow for three different keypresses to put it in three different states.

 

However, in the Ka-50, the Weapon Mode switch (burst-length) is one keypress to cycle it only. Would it be possible to change these switches to reflect how it's set up in A-10C, with the option to have one button for HI, one for MED, etc?

 

Right now I've been scratching my head at how to properly bind it to the three-state autopilot switch on the TM Warthog, but it doesn't seem possible without this functionality, which would go a long way to assist in setting up a smooth control scheme.

 

Does anyone know how much effort this would be to implement?