Problem with key bindings/joystick/hotas bindings not being recognized when in game

[71st_AH_Gamecock]

Since the last update 4.505, My key bindings/ joystick/ HOTAS settings in game for Logitech X56 are not being recognized properly. I have played IL2 BOS since it came out and have used either an X55 or 56 castle switch without ever having any issues. In fact, It works flawlessly on DCS and CLOD. I first noticed  a problem after the latest update when my rudder and elevator trim switches wouldn't work. I deleted them and rekeyed them to my joystick castle switch, and they would be recognized in the setting menu, but wouldn't work in game. I tried keying them to keyboard buttons and they still wouldnt work. I tried P51, Russian planes with trim. The only way I could found I could control them was with the HOTAS rotary switches and binding them via an elevator trim axis and yaw axis command instead of rudder and elevator switches individually. I normally use these for oil and water rads. So I tried keying oil and water rads  to my castle switch on my joystick and it the game wouldnt recognize it in play even thought the key binding menu would recognize inputs to key the castle switch binding. I have used the Windows device manager and Windows recognized all key presses. Both my HOTAS and joystick work in DCS and CLOD. Any help would be appreciated. VERY FRUSTRATED!!

Edited January 2, 2021 by 71st_AH_Gamecock

[THERION]

10 minutes ago, 71st_AH_Gamecock said:

Since the last update 4.505, My key bindings/ joystick/ HOTAS settings in game for Logitech X56 are not being recognized properly. I have played IL2 BOS since it came out and have used either an X55 or 56 castle switch without ever having any issues. In fact, It works flawlessly on DCS and CLOD. I first noticed  a problem after the latest update when my rudder and elevator trim switches wouldn't work. I deleted them and rekeyed them to my joystick castle switch, and they would be recognized in the setting menu, but wouldn't work in game. I tried keying them to keyboard buttons and they still wouldnt work. I tried P51, Russian planes with trim. The only way I could found I could control them was with the HOTAS rotary switches and binding them via an elevator trim axis and yaw axis command instead of rudder and elevator switches individually. I normally use these for oil and water rads. So I tried keying oil and water rads  to my castle switch on my joystick and it the game wouldnt recognize it in play even thought the key binding menu would recognize inputs to key the castle switch binding. I have used the Windows device manager and Windows recognized all key presses. Both my HOTAS and joystick work in DCS and CLOD. Any help would be appreciated. VERY FRUSTRATED!!

 

Well, if you tell us that your buttons are recognized in the key mapping, then to me it is obvious that in the realism settings some of the bloody assistance are active.

 

Check your whole configuration and settings, because after the first of the last two hotfixes, my settings were screwed up - and this until now never ever happened to

me. Maybe you have your settings screwed up too.

[71st_AH_Gamecock]

The main thing I first noticed was my castle switch on my X-56 that I have ALWAYS used for IL2, DCS, etc for elevator and rudder trim. I noticed that when I played 1/1/2021 the rudder trim was not working on the Hurricane when on WOL MP server. I tried rekeying but to no avail. I don't have anything double bound either. When in the key mapping menu I am able to set my castle switches to control elevator and yaw trim switches. But when in MP it is not seemingly working. I have tried this morning to key elevator and yaw trim again to my castle switch- its keying, but not being recognized in QMB, MP, or single player missions. I have always used this configuration. Also, I can key a keyboard command to L/R trim switches to no avail- wont recognize it in game althought it allows me to set binding. I can get trim to work using an axis binding but I use to rotary dials on HOTAS for oil and water rads usually- always have with not problem. So basically, all buttons are recognized in key binding menu, but are not working in game after I bind them and accept new settings (green button). I do not feel this is an assistance issue because in MP servers like WOL its not recognizing the key bindings for elev trim and yaw trim (non axis bindings) I verified this by going on WOL a few minutes ago. I have even shut my pc down pulled usb connections and blew any dust off and reseated them. Sometimes that fixes things that are quirky like this, but not this time. 

[Soarfeat]

Hello,

 

I had received a new joystick as a gift and when trying to map the buttons , I had the exact same problem. The buttons would bind properly in the controller set-up, however would not work when flying. I tried a bunch of different things via researching the internet and was going to just do a reinstall of the sim. I found something however, that I decided to try and it worked. I have the sim completely backed up and would recommend the same before doing this. Also, just for simplicity sake, I backed up my "updates" folder and my "input" folder located in " data " folder for a quick fix if things really went bonkers. 

So, all I did was to go into the main Il-2 folder---  path is ,  IL-2/updates,   delete the contents of this "updates" folder and retstart your sim and let it refresh everything and then try mapping things again. Please note, there is an "updater" folder located in the "data" folder, do not mistakenly delete contents of this one. Again "updates" folder is the one you will see when you open the IL-2 main folder.

It worked great for me and everything mapped and worked fine.  

Hope this may be of some help.

---Cheers---      

     

Edited January 3, 2021 by WWSoarfeat
edit

[Sokol1]

Rename/Delete the file "Devices.txt" in game \Data\Input folder and assign again.

[Soarfeat]

2 hours ago, Sokol1 said:

Rename/Delete the file "Devices.txt" in game \Data\Input folder and assign again.

Hey Sokol1,

Interesting fact is that I had tried this in regards to key bindings not working and as my luck is, it did not work. 

Thanks though for posting this as a possible solution, I should have stated that this is one I had tried however without success.

 

 

[71st_AH_Gamecock]

I tried deleting update and it didn't work, but thanks for the response.

[SakerVVS]

Are they bound in the first column of the 3?

[Grisby]

I have key binding problems too. Using VR and failing to bind the aileron trim control, the Spitfire is practically unflyable.  Although the aileron trim control shows bound (green) when setting it has zero effect when flying.  With other planes I can compensate enough to fly level using rudder and elevator trims but there is not enough rudder range alone to trim out the Spitfire.  Tried settings to default and redoing the bindings but with same result.

[71st_AH_Gamecock]

I tried all suggestions and ended up having to rekey the trim to rotary dials on the hotas. It simply will not allow me to key trim to the castle switch. Something in the last update caused a conflict.

On 1/3/2021 at 10:40 AM, 6./ZG26_Saker said:

Are they bound in the first column of the 3?

I tried to key them on each column and none worked

 

[Sokol1]

6 hours ago, Grisby said:

I have key binding problems too. Using VR and failing to bind the aileron trim control, the Spitfire is practically unflyable.  Although the aileron trim control shows bound (green) when setting it has zero effect when flying.  With other planes I can compensate enough to fly level using rudder and elevator trims but there is not enough rudder range alone to trim out the Spitfire.  Tried settings to default and redoing the bindings but with same result.

 

Spitfire has no aileron trim, only elevator and rudder trim.

[cardboard_killer]

6 hours ago, Grisby said:

Using VR and failing to bind the aileron trim control, the Spitfire is practically unflyable. 

 

You can find each a/c's available bindings on this spreadsheet.

 

 

 

[Grisby]

Thanks, that's very useful and explains why I can't trim the ailerons in the Spitfire. The question is why not as it affects fly ability so much.  Did it not have it irl?  If not, why is rudder trim insufficient to compensate, any other workaround?

Edited January 7, 2021 by Grisby
updated

[cardboard_killer]

50 minutes ago, Grisby said:

Did it not have it irl? 

 

It did not. I don't know why, or even if anyone knows why. These were very short range a/c so it may be that aileron trim was deemed as not worth the extra weight.

[Sokol1]

Spitfire only fly "hands off" more or less leveled whit adjust of elevator and rudder trim at cruise power - for what the aileron fixed trim tabs has been adjusted by ground crew.

 

So if you keep throttle "firewall'ed" all time, the plane start drift for a side, in this case use the "gamey" AI-Autopilot for level flight.

[LLv34_adexu]

Coming back to this game from long break. First thing I did remapped some of my controls and then noticed that they wont respond ingame. I have zoom in and zoom out on my Fignterstick, works. I have fire all weps there, works. I have superchargers stage, doesnt work, neither do trims. everything works in the game mapping software tho.

 

I get my RPM to 99% only with my throttle, sometimes it goes up to 100% during flight, but I have to try to geit it there, thats bound under a button, so there is no possible deadzones or anything, it goes to 99%. Dunno if that is plane related as it is Yak-1 s69.

 

If there is only solution to reinstall the game or something, I rather just uninstall it and go play sims which work.

[cardboard_killer]

Welcome back. At least one of the updates in the last ten months did have some impact on mapping. I'd recommend deleting your mapping files altogether and remapping everything.

 

Any particular reason you choose this thread to necropost?

[LLv34_adexu]

Well, seems like similar problem, found this thread, so why create new topic. Maybe ppl who posted here found solution.

 

I actually gave it a go and reinstalled whole game, deleted everything and did rebinding. Now if before my Fighterstick left hat didn't work properly during flight, now it moved to the right hat and POV. So if before I had problems with supercharger stages, now I cant trim. And it is only trimming which doesn't work. I have rudder on right hat, where La-5 should have rudder trim. Nothing happens. Up and down I have stabilizator.. and it works on FW190.

 

Seems like software issue to me, almost a year and still not fixed.

[cardboard_killer]

6 minutes ago, LLv34_adexu said:

And it is only trimming which doesn't work. I have rudder on right hat, where La-5 should have rudder trim. Nothing happens. Up and down I have stabilizator.. and it works on FW190.

 

Please post a screenshot of your trim bindings and of your realism settings.

[LLv34_adexu]

How that could help with solution? Most of the time flying online, so don't see point of posting realism settings at all. Neither do with binds, as the keyboard bindings work, but not bound joystick bindings.

[cardboard_killer]

Well, it could rule out user error.

[Burning_Bridges]

What this game missing is a notification when keybinds collide.

 

I thought that many keys were not working but in fact they were assigned differently than I had thought, and adding new assignments on top made matters only worse.

Edited January 2, 2022 by Burning_Bridges

[Chief_Mouser]

1 hour ago, Burning_Bridges said:

What this game missing is a notification when keybinds collide.

 

I thought that many keys were not working but in fact they were assigned differently than I had thought, and adding new assignments on top made matters only worse.

 

Duplicate key bindings are shown with an orange square in the settings for each key. Hover over it to see the conflicts/duplicates. Been there since the beginning.

[pawnmaker]

Has anyone heard of a solution to this?  I have a new X56 that I am trying to setup for IL2 but I have the same problem that the castle switch doesn't work properly.  I can assign it to elevator or rudder trim for example and it is detected properly in the settings, however it doesn't function in-game.  If I assign the same castle switch to say, firing the guns it does work properly. 

[pawnmaker]

Nevermind, I think I figured it out.  You have to bind them to the elevator/rudder trim access for them to work, hope that helps if anyone has this issue.

[JumpnShootman]

I've got this same problem, I can bind axis and buttons fine, but even when I go into the "curves" menu and move them nothing happens. No input in game either.

Edited October 2, 2022 by JumpnShootman

[Ghost666]

I've seen this too, does not mean the binding didn't take. Go see if it works in the plain. Or sometimes it works after you get out of the key binding menu and come back in.