@Blu3wolf:
If you make this output dx directinput from a virtual device, that might be interesting. Keyboard output isnt going to be very useful once you run out of keys and start playing with key modifiers.
Most of the features are already supported by BMS. You can do key release commands in BMS, you can do key down and key held commands. Although, the ability to switch stick profiles hands on could definitely come in handy for simpler sticks.
Hi Blu3wolf,
I think you are mistaken. So far pure BMS GUI lets you to setup button (or keyboard key) press only. There is no option to fire action on button or key release. Take Warthog APU switch for example. If you move it up to start position, BMS will register it as joy button 20, and this you can assign to any cockpit function. When you move it down to off, BMS will NOT register any button press, and you cannot map action on off position. Also, BMS DOES NOT recognize input from Warthog Throttle POV AT ALL. So, I would be veeery careful saying “most of the features are already supported”. RS Mapper lets you decide whether you want to have an action (currently sending the keystroke, modified any way you like) on button press (APU start), release (off) or both (of course, different action - like master arm on / off). Aditionally, RS mapper lets you configure repeated actions, very useful in invoking radio commands (take: Q, Q, 1 for active threats call to AWACS). With RS Mapper you can call AWACS like that with one button only Also, most of the software (take TARGET for example) works with sending keyboard commands, as most sims are coded with different keyboard shortcuts mapped to specific actions of the plane.
In theory I can simulate virtual DX device, that is not a big problem. Problem is that when this device IS being simulated you would need extra mapping of virtual DX device into the BMS, so that correct action / virtual input is mapped to correct cockpit action, while keyboard strokes are already assigned by default.
Avantar.