Jump to content

Controller Assignment (untested)


Recommended Posts

Damn, wish I had known this a long time ago.  Every so often, one of my devices somehow gets unplugged, or a hub screws up, and next thing I know my throttle is controlling my radiator and a ton of other stupid things.

I have to resort to my cheat sheet and edit current_actions

find and replace joy0_ with joy9_

find and replace joy1_ with joy0_ and so on till things are right.

but if a post on IL2 is correct, there is one file (devices.txt) in data/input that lists all the devices, and what controller ID they have, and all that is needed to do is make sure I know what id I want each controller to be set to for my assignments to work as intended.  Like I said, untested, but if my stick and quadrant get mixed up again, this is the first way I will try and fix it.

configId,guid,model|

0,%2281c35d80-fcc5-11e6-0000545345440180%22,Saitek%20Pro%20Flight%20Rudder%20Pedals|

1,%22c8fd9b30-30ef-11e7-0000545345440180%22,Flight%20Throttle%20Quadrant|

2,%22933e50e0-6b83-11e4-0000545345440680%22,X52%20H.O.T.A.S.|

3,%22be2684d0-31b0-11e7-0000545345440280%22,Flight%20Throttle%20Quadrant|

4,%2251e54230-d0b4-11e8-0000545345440380%22,USB%20Gamepad

 

Link to post
Share on other sites

That's exactly how I use the devices.txt to figure mine out.  Was a boon when I was trying to decipher issues with my warthog throttle (not that it's working).  You can also delete the whole file and GB will rebuild it the next time you fire up GB, done that a few times while trying to get all the controllers sorted out.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

Please confirm you have read and understand the rules above