Controller Setup: New column "Auto recognition"

[Limaro]

When having a lot to setup, and multiple controllers, it's a painful scrolling, checking, testing (when they ar enot well named).

In order to make the controller configuration more comfortable, it would be great to have one column with which you can work to manage setting up new inputs. Just by automatic recognition of what controller made the input.

Anyhow, this is actually the way most games I knew do it. Having one column, in which then the button assignments are listed with corresponding controllers. But for the current purpose it would already be great to have that auto column.

Or, secondary Idea: When chosing the wrong controller, pressing a button, DCS could see that and offer a "Ok, then assign this button from the other controll".

[cfrag]

I like the idea - and TBH, we don't even need a special column for that. Just put a big bad button on the bottom (or top) called "AUTO ASSIGN", and when clicked open the same controller interface we have now that listens to all connected controllers, instead of just one. Any controller that moves / state-changes is then tentatively assigned until confirmed. Might not work with all controllers, but it surely will make things a bit easier. 

[sirrah]

No idea how complicated it would be to implement this, but this would most definitely be very convenient indeed 

[upyr1]

I would go for a single column if we could get the option to expand and collapse. No Matt what the menu looks like I want a profile called common controls where we can set the defaults for the most common controls