How many control device ID's do you play Evochron, Arvoch, and/or StarWraith with simultaneously?

[Vice]

I'm looking into the feasibility of attempting to expand controller support for split button bindings across multiple game control device ID's and am interested in learning how many control devices players may be using with the games at the same time. That is, how many individual devices are connected to play the game with their own unique ID's as listed in Windows. For example:

- The Saitek/Logitech X52 has a joystick and throttle, but only registers as one device ID in Windows, so this would count as 1.
- However, the X55 has a joystick and throttle and each registers as a unique device ID in Windows, so this would count as 2.

Please indicate in the poll how many device ID's you use to play the game(s) and if you want to elaborate further, feel free to reply with the specific makes and models of each device.

[Marvin]

I use the Logitech Extreme 3D Pro, keyboard and standard (not gaming) wireless mouse. Nothing else.

[TraderDan]

That's funny marv I had the same setup

[Vice]

Ok, we'll add two more for the '1' category then. I think this kind of change would mostly impact a relatively smaller percentage of players that either use a HOTAS with two separate USB device ID's and others who may have two or more devices of various types.

[Marvin]

That's funny marv I had the same setup

I think I've had three of the same joystick. The other two are back in their boxes waiting for the day (if it ever comes) when I can make repairs.

[TraderDan]

Hahaha same

[Vice]

Kind of a development blog post here. I've studied the control systems in detail and have formulated some possible solutions to integrating cross-device dual button mapping. A dedicated second layer of input mapping will be required, one that takes into account a second mapped input's unique device identifier and coupling that with a baseline device identifier for button one. Special markers will be put in place for both the standard setting control template (using the '=' character) as well as for the custom control profile template (using the '/' character since '=' is already used as an earlier delimiter).

New indications will be added for the Key/Button Controls menu to display which device is assigned to a secondary input, something like '1/D2' will likely be used to indicate button 1 on device 2 for a secondary mapping. For example, a split-device dual input binding might look something like this in Evochron/Arvoch:

Device 1, 4+2/D2

To indicate the primary button 4 on device 1 being linked with button 2 on device 2 for a combined input mapping. Due to the limited length available in SWC, it's mappings might look something like this for the same arrangement:

D#1, 4+2/D#2

The goal will be to implement an additional 'listening' mode in the Key/Button Controls (and for SWC, Keys/Buttons) device selection drop down menu. It will be labeled 'All Devices' and when selected, will allow the game to listen for input from all connected/detected game control devices when mapping functions. All ignore bypasses (including a newly added system for secondary mapping) for active buttons/toggles as well as sequential order procedures will be retained and function as normal. This way, the simplicity of selecting a control function and then pressing buttons will be kept in place without the need for any kind of multi-step selection or mode process. The only added step would be selecting 'All Devices' to listen to all inputs.

Since axis input operation uses its own separate system dedicated to individual channel detection and mapping, it will continue to operate as before and be limited to direct key/button function mapping via individual channel assignment. This means that like the Axis Configuration menu, only one function will continue to be mappable per axis channel input (as it has been). So there should be no changes to those systems.

The new multi-device dual mapping system should support both button inputs as well as HAT/POV directional inputs. So mixing and mapping should be just as possible across multiple game control devices as they are now on single devices alone.