flight stick compatibilty

[Mannawar]

I have a Thrustmaster T.Flight Stick X that is working properly, and has been worked fine in other flight sims, but, IL2 BOS  doesn't seem to recognize it properly.  Axis and throttle are ok.  The button assignments are not right..............I assign button #7, and game assigns  #6..............I assign button #12, game assigns it as #11, etc.

 

Then, in-game, none of the buttons work at all..........though axis, throttle, and trigger are fine.

 

How do I calibrate my flight stick to this game???

 

Still trying to get up and flying, so I'd appreciate your experience/input,

 

mannawar

[216th_Jordan]

I have a Thrustmaster T.Flight Stick X that is working properly, and has been worked fine in other flight sims, but, IL2 BOS doesn't seem to recognize it properly. Axis and throttle are ok. The button assignments are not right..............I assign button #7, and game assigns #6..............I assign button #12, game assigns it as #11, etc.

 

Then, in-game, none of the buttons work at all..........though axis, throttle, and trigger are fine.

 

How do I calibrate my flight stick to this game???

 

Still trying to get up and flying, so I'd appreciate your experience/input,

 

mannawar

This is weird. Just for formality: You hit apply settings and nothing happend? what kind of buttons did you assign (radiator commands for example wont work in normal mode as they are controlled automatically). That indexing thing is typical, like in C where you create and areay of [5] and it goes from [0] to [4] ^^

[Mannawar]

Thanks for your reply "Jordan."   Yes, I hit apply settings...nothing.  I don't quite understand what you mean about "that indexing thing"  I'm trying to assign certain flight stick buttons to specific camera and weapons commands.  No Progress yet.

 

Ta

[dburne]

It is not unusual to see BoS assign different numbers to your buttons than your actual dx button numbers.

It did the same on my Warthog as well.

 

However not sure why none of your button assisgnments are working in the game though, sounds like there might be  a conflict in there somehow.

[Thad]

Salutations,

 

I have a Thrustmaster FCS HOTAS. The games keymapper assigns the joystick as the number 0 controller and the throttle as the number 1 controller.

 

There is a file one can change in the game that will assign the controllers as 1 and 2. The information is somewhere in the forums. 

 

I just kept it as 0 and 1.

[Thad]

Found it.

 

Go into your IL2/data/input folder.

 

You can edit your "devices.txt" file to have joy1 for the joystick and joy2 for the FCS throttle.

[Warpig]

Be sure not to have any other controllers plugged in. Having an X-Box controller plugged in while trying to assign joystick buttons, fudged me up before.

[Field-Ops]

Yea having any other joys, pedals, xbox controllers plugged in at the time of binding keys to them, then unplugging said excess controllers will result in your system re-assigning joystick numbers. So say your joystick was device 2, it would now be device 1 and all your bindings will be thrown out.

[Mannawar]

Hey Thad,

Thanks for your reply.  I've already been in the "input folder," but I was too hesitant to change anything..........I don't want to change something that I can't  undo.

 

There seems to be some kind of conflict.  When I go to key mapping,  instead of trying to assign commands to the flight stick, I assign the commands to specific keys (not used by any other commands.)  I try things that would be obvious, like:  flyby, combat camera, reset external cam, etc.    The commands do not work on the keyboard either.  I'm about ready to chuck this.........I've spent waaaaay too much time on it, and still can't fly.  Bother, Bother, Bother!

[dburne]

Regarding the external views, you are not flying in Expert Mode are you? Externals are disabled in Expert.

[Mannawar]

No,  not flying in expert mode.      Would just like to fly in Kindergarten Mode!!

[FlyingH]

Make sure the folder or the files aren´t set to "read only"! Right click and choose properties to check.