1 Profile for all USB devices

[SturmovikPilot]

On the Systems Options menu under controls there is a column for each device example in my case is:

 

Keyboard | XBOX 360 Controller | Razer Tartarus | Siatek X55 Rhino Throttle | MFG Crosswind Rudder Pedals | Saitek X55 Rhino Stick | TrackIr | Mouse

 

Is there one single profile for each flyable that includes all devices along with the ability to cause the system to prevent errant inputs from the unused devices? Don't want a hardware solution (unplugging devices) want a software solution.

 

Respectfully,

Gregory (aka Fossil)

[cichlidfan]

Is there one single profile for each flyable that includes all devices along with the ability to cause the system to prevent errant inputs from the unused devices?

 

No. I don't think it would be possible without ED making changes.

[PiedDroit]

What you can do at the moment is to clear the assignement for every controller you don't want to use, for every aircraft.

Example to clean XBOX controller for A-10c:

1 - go to options, controls, select A-10C

2 - click in column "XBOX Controller"

3 - click button" Clear Category", confirm (yes)

4 - select "Axis commands"

5 - repeat 2 and 3

 

That quite a tedious process I know but it works.

You'll have to to it every time you plug a new controller you don't want to use in DCS, because every new controller gets a default profile that messes up with your existing profiles.

 

I think it's possible to have a blank default profile but I didn't look for a way to implement it yet, I'll have a look a it soon.

Edited March 4, 2015 by PiedDroit

[cichlidfan]

That quite a tedious process I know but it works.

You'll have to to it every time you plug a new controller you don't want to use in DCS.

 

Which is why I went with USB hub with switches on the ports.

[SturmovikPilot]

Is there a block diagram that shows how the system works regarding controllers and profiles.

Where does the column header come from. Does a profile get associated with a selected game (UH1-H) when launched?

[cichlidfan]

No such block diagram exists AFAIK. Each aircraft maintains it's own profile for each controller, including mouse and keyboard. Also, aircraft like the A-10C have a sim and game mode, which are maintained separately as well.

 

If you had 3 aircraft setup with stick, throttle and rudder pedals, then you would end up with a total of nine profiles that you would need to save.

[SturmovikPilot]

Hey thank you all for the responses.

Have exhausted forums and whatever I could think of.

Is there a way to restart a training mission after a crash without having to quit and restart?

Is there a way to move further back in cockpit with Field Of View?

[PiedDroit]

No.

Yes.

But you really should create a new topic to avoid polluting this one with new questions :)

[SturmovikPilot]

Appreciate the advice for posting

Respectfully,

Fossil

[PiedDroit]

No problema,

 

Back on topic, I found a way to have a blank default profile.

Spoiler: it's not magic and what follows is more informative than really useful, except at the end, read everything :smartass::

 

----------------------------------

--- A little background -----

 

In your DCS install folder, each aircraft has a set of default profiles for each controller type:

For example, for the A-10C:

DCS World\Mods\aircraft\A-10C\Input\A-10C\headtracker

DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick

DCS World\Mods\aircraft\A-10C\Input\A-10C\keyboard

DCS World\Mods\aircraft\A-10C\Input\A-10C\mouse

DCS World\Mods\aircraft\A-10C\Input\A-10C\trackir

 

In each folder, there is a default.lua which the profile that is used for unknown devices and other lua files that are pre-configured for certain controllers, for example, in DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick:

CH PRO PEDALS USB .lua

default.lua

F16 MFD 1.lua

F16 MFD 2.lua

Joystick - HOTAS Warthog.lua

Saitek X52 Pro Flight Control System.lua

Saitek X52 Pro Flight Controller.lua

Throttle - HOTAS Warthog.lua

Thrustmaster Combined.lua

 

This the reason why the TM Warthog is pug-n-play with the A-10C, it has a preconfigured profile.

 

----------------------------------------------------

--- What to do to have a blank profile -----

 

Open default.lua for which aircraft you want to modifiy the default profile (you'll do the same for other controllers you expect to plug but not use for DCS, for example if you have a X-52 you don't want to use for DCS).

Make sure to do backups before.

 

Each line in the default.lua consist in some lua code for the command plus some occasional bindings:

 

{combos = {{key = 'JOY_BTN2'}}, down = iCommandPlanePickleOn, up = iCommandPlanePickleOff, name = _('Weapon release'), category = _('HOTAS')},

What you will do is to remove the combos assignments:

 

{down = iCommandPlanePickleOn, up = iCommandPlanePickleOff, name = _('Weapon release'), category = _('HOTAS')},

Axis assignments are represented as follow (with default device assignement):

 

{combos = defaultDeviceAssignmentFor("roll") , action = iCommandPlaneRoll, name = _('Roll')},

 

Or (without the default assignment, found this in MiG-21 default.lua)

 

{combos={{key='JOY_X'}},action=iCommandPlaneRoll,name='Roll'},

 

I didn't test it but it should work by removing only the combos, just like the buttons (check how the non-assigned axis are written).

 

After that, every time you plug a new controller, it will have no default mapping (for this aircraft).

 

----------------------------------------------------

--- WARNING -----

 

Attention, the files in the game directory are the default files.

As such, they will not hold any of the mappings you configure in the options.

Your mappings are stored as diff files (against the default files), in your Saved Games\DCS directory.

 

In conclusion, this process is even more tedious and risk-prone than the previous one.

It might be interesting if you have A LOT of different controllers so you won't have to manually clear the controls everytime you plug a new controller.

But in my opinion it's not worth using this method since you still have to manually edit the files for every module, there is no "unified" profile that is valid for *all* modules (sort of, see below).

----------------------------

---- There is hope -----

 

Well, there is actually some unified stuff in DCS World\Config\Input\Aircrafts\Default, but it does not cover everything.

In the file DCS World\Config\Input\Aircrafts\Default\default.lua you'll find some interesting mappings that may be worth modifying:

 

-- joystick axes

{combos = {{key = 'JOY_X'}}, action = iCommandPlaneRoll, name = _('Roll')},

{combos = {{key = 'JOY_Y'}}, action = iCommandPlanePitch, name = _('Pitch')},

{combos = {{key = 'JOY_RZ'}}, action = iCommandPlaneRudder, name = _('Rudder')},

{combos = {{key = 'JOY_SLIDER1'}}, action = iCommandPlaneThrustCommon, name = _('Thrust')},

However they won't work for every aircraft, the A-10C uses them (see above), but the MiG-21 doesn't for instance (you can tweak the default.lua of the MiG to make it use them though - don't forget to backup).

Good news is most of the time it's only the axis that are problematic for multiple controllers.

 

In conclusion, you will find some stuff to fiddle with in DCS World\Config\Input\Aircrafts\Default but that's pretty much it.

 

Cheers!

Edited March 6, 2015 by PiedDroit

[SturmovikPilot]

Thank you for the assistance.

Would it be possible for you seasoned/knowledgeable folk to create two different threads? One for the X55 Rhino *.lua files and one for x55 Rhino *.pro files.

Edited March 8, 2015 by SturmovikPilot

[PiedDroit]

Thank you for the assistance.

Would it be possible for you seasoned/knowledgeable folk to create two different threads? One for the X55 Rhino *.lua files and one for x55 Rhino *.pro files.

Just create the thread yourself (only one will suffice) and tell exactly the files/profiles you're looking for, people will help for sure :thumbup:

 

But first you can use the search engine of the forum, what you need might be a couple of clicks away already.