Better auto-configuration of (new) controllers

[Flagrum]

When a new controller is used the first time with a module (i.e. new controller OR new aircraft), DCS configures some default mappings. This usually leads to conflicts as already assigned functions are mapped and it is usually also quite pointless. Nobody needs the fire button mapped to the Saitek MFDs, nobody needs the pitch and yaw axis mapped to the rudder pedals, etc.

 

This especially confuses simmers that are new to DCS and is a PITA to clean up even for DCS veterans.

 

Therefore I propose a modified approach: the automatic configuration should only be done after asking the user! When DCS detects that an aircraft lacks a propper controller mapping for a controller, a dialog should be displayed. In this dialog he would be asked what kind of controller the newly detected one is and be offered to select an appropriate default mapping. This dialog will be displayed for all relevant controllers sequentially so that in the end, i.e. for a new aircraft, everything is set up allright. Just a couple of mouse clicks later all basic mappings are applied to the respective controllers and you are ready to take off within 1 minute.

 

Example:

DCS has detected that a new controller "Saitek Combad Rudder Pedals" is not properly configured for use with the aircraft "Apache 64D". Please select a basic configuration or perform a manual setup.

Available basic configuratons:

( ) Joystick as fixed wing stick

( ) Joystick as helo cyclic

(*) Rudder or anti torque pedals

( ) Multi function display

( ) other / manual configuration

 

[Ok] [Cancel]

Edited September 7, 2014 by Flagrum

[Red Dragon-DK]

+1 good point.

[upupandaway]

I agree, a very good suggestion.

Even the simple option to deactivate auto-configuration would facilitate mapping of new devices or complete remapping of the setup. I recently had to do this and a large part of the time was spent just removing pointless and conflicting button and axis assignments.

[MadDog-IC]

+1 , agreed, this would be a most welcome addition

[Demon]

It would be nice to see this. At the very least, it would be nice to have it not auto-bind any axes/keys, and instead when you start the game with a new controller, it would just prompt you "new device detected, please configure it in the controls menu."

That way you'll have to set it up yourself and you don't have to go through and clear all the keybinds.

 

I don't know about you guys, but when I get a new module it always maps the weapon release, gun trigger, roll, pitch, and throttle to my pedals :P

[cichlidfan]

I don't know about you guys, but when I get a new module it always maps the weapon release, gun trigger, roll, pitch, and throttle to my pedals :P

 

My favorite is all of the stuff that is mapped to my (one axis, no buttons) trim wheel. :P

 

I am used to clearing every controller before I set up anything but it would be nice if I did not have to do it.

[Home Fries]

+1

[nickexists]

+1

everytime I get a new module I have two forms for a list of useful hotas bindings. the developers already know which commands or going to be useful to have an app to controller, each module should just come with a script to help map these commands.

[Spasticatedtoad]

+1

I really like this idea too. Recently, when I bought the Warthog and Saitek Pedals, I was not very familiar with any of the modules.

As I own all the modules, I found that I spent far longer deleting duplicate commands from my new equipment, than I did setting up the few basic controls I knew.

I can imagine, that someone who is brand new to DCS, would have a lot of hassle figuring out what command is needed where.

[lxsapper]

There is the option to clear all assignments of a particular controller. Doesn't that end up beeing the same?

[Flagrum]

There is the option to clear all assignments of a particular controller. Doesn't that end up beeing the same?

Not quite. It helps atm as we have no better means to deal with it, but it is still tedious and error prone. Do that accidentally while you are in category "All" ... you do that only once. :o) Then you will do it category by category and controller by controller... (--> tedious)

It helps for the most important categories, like the axes. But there are also so many "hidden" mappings that you probably want to get rid of (view control mappings on Saitek MFD1, on Saitek MFD2, Fire buttons on your CH Keyboard-thingy, etc.)