Controls, GUI, and Text

[LukeFF]

Please post any issues with the controls, the GUI, or the text here. Please note this topic is strictly for bug reports. Any off-topic banter will be removed at our discretion. Thank you! 

[Neoproxy]

I have a Thrustmast T16000m Hotas and having a strange issue.  It's similar to other's but not exactly the same.  In quick play, everything operates as intended.  I decided to start my first career from the Flying Circus DLCs (I own all of  them).  When in Career mode, with realism set to expert, My throttle is always set to max or near max.  I can lift off and do my mission, but have 0 control of my throttle%.  The Hotas throttle does nothing nor does the -/= keys.  I have to blip just to be able to land.  It's incredibly frustrating and I can't seem to figure it out.

I have unbound all throttle settings and only bound to Main Throttle.  I adjusted realism.  I have verified files.  Nothing is working.  

I am flying the DH2 pusher plane Squadron 29, 1916 starting campaign.

[Neoproxy]

I figured it out.  For any noob like myself, the DH 2 has no throttle.  Speed is managed by blipping and mixture.

[airsheep_VR]

Hi, Im not sure this is the best topic to post this issue, maybe someone can help me:

can somebody confirm that the stabilizer trim axis (from 0 to 100, for example in the FW 190 but all planes are involved) is not using the whole scale in the corresponding gauge? It is a bug or a feature? Recently I feel that every plane have to be trimmed 100% nose heavy to fly levelled. By set the elevator trim ( or stabilizer axis no matter) neutral the planes behave like a helicopter they want to fly  vertically. Here is a picture of what I am talking about:
 

Edited November 29, 2025 by airsheep_VR

[Burnie]

Hi all!

Hope someone can help me. I'm pulling my hair out. I'm having a weird issue with my X52 Pro joystick.

I just bought a load of Flying Circus DLC in the sale and have been playing for the past week without any issue. Suddenly, all of the buttons on my X52 have stopped working in game. The pitch and roll axis work fine, but none of the buttons. The game allows me to bind the buttons and recognises them without issue, but they don't work in game.

So far I have tried reinstalling the drivers for the X52, deleting the devices.txt file and reinstalling IL2 but nothing seems to fix the issue. If I test the joystick on https://hardwaretester.com/gamepad, all buttons work fine.

I even tried binding keystrokes to the buttons using the X52 profiling tool. When I test them by putting an open text document in focus and pressing the buttons, I can see that keystrokes are being sent from the controller, but they don't work with the game in focus.

I really don't understand why this has suddenly started to happen. It's been working fine for hours.

Anyone have any ideas?

(Updated to add) I just tried using the controller in a different game and all buttons work fine, so the X52 is 100% working ok.

Also tried assigning all controls via Joystick Gremlin. IL2 recognises all the button inputs when I bind them, but they still don't work in game. It must be something silly. I just can't think for the life of me what it is.

(Another edit) Just to add that I just tried using a xbox controller to bind keys and it does the same thing. The game lets me bind the button, but it doesn't work in game. So it's safe to conclude that all input devices are no longer working. I also tried deleting the contents of the update folder, but that didn't work either.

Edited November 30, 2025 by Burnie

[Czech693]

On 11/29/2025 at 4:09 PM, Burnie said:

Hi all!

Hope someone can help me. I'm pulling my hair out. I'm having a weird issue with my X52 Pro joystick.

I just bought a load of Flying Circus DLC in the sale and have been playing for the past week without any issue. Suddenly, all of the buttons on my X52 have stopped working in game. The pitch and roll axis work fine, but none of the buttons. The game allows me to bind the buttons and recognises them without issue, but they don't work in game.

So far I have tried reinstalling the drivers for the X52, deleting the devices.txt file and reinstalling IL2 but nothing seems to fix the issue. If I test the joystick on https://hardwaretester.com/gamepad, all buttons work fine.

I even tried binding keystrokes to the buttons using the X52 profiling tool. When I test them by putting an open text document in focus and pressing the buttons, I can see that keystrokes are being sent from the controller, but they don't work with the game in focus.

I really don't understand why this has suddenly started to happen. It's been working fine for hours.

Anyone have any ideas?

(Updated to add) I just tried using the controller in a different game and all buttons work fine, so the X52 is 100% working ok.

Also tried assigning all controls via Joystick Gremlin. IL2 recognises all the button inputs when I bind them, but they still don't work in game. It must be something silly. I just can't think for the life of me what it is.

(Another edit) Just to add that I just tried using a xbox controller to bind keys and it does the same thing. The game lets me bind the button, but it doesn't work in game. So it's safe to conclude that all input devices are no longer working. I also tried deleting the contents of the update folder, but that didn't work either.

Try the Windows USB Game Controller and make sure the buttons on the stick are showing up as functioning.

Edited December 14, 2025 by Czech693

[Gutholz]

1) In at least two recordings from multiplayer, I noticed that my playername was displayed on the wrong airplane.

Screenshot: On the 109 at bottom left it says "Gutholz" but that is not me. 

(I am the distant flying plane at top left in the cloud)

 

 

2) I had a tooltip "vote ban" at the mouse pointer that did not go away, even when switching menus or in cockpit.

Not sure how I triggered it. As far I remember, I did not actually click but just mouse-hovered over the button.

 

3) "Become a gunner" in multiplayer did not work.

I could select the plane and position as normal.

But clicking the "start"-button did nothing. No error message, just nothing.

Gunner postions were not locked.

It then randomly worked at another time with a another player. I read somewhere, that is a somewhat common problem.