There are basically three choices at least:
-
Binding a SET command on a SPST for the up position only (meaning 1 when up, 0 when down)
-
Binding a SET command on a DPST for the up position only (meaning 1 when up, 0 when down)
-
Binding a pair of commands on a DPST (thank you for the acronym!) )(meaning ON when up, OFF when down)
Each case is as valid as another and in all these cases, the only problem is FS2020 accelerating any command as long as 1 and only 1 is always active. If FS2020 is accelerating only the “SET” commands though, it would then be better mapping the switch positions to the ON and OFF commands instead but this is a user facing problem only, not a hardware problem.
However, because of the DPST nature of the switch, the autodetection of input when setting up the controls in other games doesn’t work, because activating a switch changes 2 inputs instead of 1. For these, it would be best having an alternate firmware mode when each switch is working as a SPST. It can be easily done in removing all the switch down position inputs from HID, as if each switch would only have a UP position (1 is up, 0 if down), or if not possible to remove them from the list exposed via HID, at least making the down positions always 0.
I hope this makes sense?!
PS: about the ON/OFF commands, some of them are presently not working as expected, or not at all in FS2020… I believe this is affecting the LIGHTS ON/OFF commands (the first 3 switches from the left in the Alpha).