Losing throttle control when approaching Airfield

[Magneto]

Hi Everyone,

Using a Logitech X56 HOTAS.

In Single Player, Quick Missions I am a Newbe trying to learn how to land. Everthing works fine in the mission except occasionaly the view changes to the bomber target or the landing gear deploys though I haven't touched those controls but I have a bug that occurs very frequently. I am approaching the Airfield to land when I will suddenly lose throttle control and it is stuck at a high level making it so I have to abort. Even if I engage the Autopilot, it can no longer control the throttle either.

Please Help!

[jollyjack]

Might be something i am experiencing but occasionally since game version 4.702c.

 

Just popped up in my mind: Can it be that you use or have used NVDIA experience? I just threw it off again, i don't like it at all.

I am now going to remove and cleanup all NVDIA stuff. Got suspicious now that it might have left some keybinding data behind in the registry.

 

[56RAF_Roblex]

It sounds like a double keybind eg whatever key you use to lower the flaps or trim the nose up has also been programmed to set maximum throttle or autopilot.  Are you doing anything just before the  bug happens eg Selecting flaps or pressing a keyboard or joystick button to change view or open the canopy?  It could be anything.   If there is something then go into your key settings and look at that function to see if there is a little red X next to whatever key/button/axis you use for that.  That indicates two functions set on the same key. If there is then hover your mouse over the X and it will tell you what two functions are on it so you can go and unset or change the other one.     If you can't think of what you might be pressing then it might be worth looking through all your key assignments to see which ones have an X next to them.  It is not always a problem; I frequently put two things on one button when I know they wont cause problems eg 'unlock tailwheel' on the same button as 'reload gun'.

 

It is also possible that a key you use for an external program like Discord or TrackIR shares a key that IL2 uses.

Edited March 8, 2022 by 56RAF_Roblex

[Magneto]

9 hours ago, jollyjack said:

Might be something i am experiencing but occasionally since game version 4.702c.

 

Just popped up in my mind: Can it be that you use or have used NVDIA experience? I just threw it off again, i don't like it at all.

I am now going to remove and cleanup all NVDIA stuff. Got suspicious now that it might have left some keybinding data behind in the registry.

 

It is a new nvidia GPU but I have never installed NVDIA experience.

8 hours ago, 56RAF_Roblex said:

It sounds like a double keybind eg whatever key you use to lower the flaps or trim the nose up has also been programmed to set maximum throttle or autopilot.  Are you doing anything just before the  bug happens eg Selecting flaps or pressing a keyboard or joystick button to change view or open the canopy?  It could be anything.   If there is something then go into your key settings and look at that function to see if there is a little red X next to whatever key/button/axis you use for that.  That indicates two functions set on the same key. If there is then hover your mouse over the X and it will tell you what two functions are on it so you can go and unset or change the other one.     If you can't think of what you might be pressing then it might be worth looking through all your key assignments to see which ones have an X next to them.  It is not always a problem; I frequently put two things on one button when I know they wont cause problems eg 'unlock tailwheel' on the same button as 'reload gun'.

 

It is also possible that a key you use for an external program like Discord or TrackIR shares a key that IL2 uses.

I already removed any double Keybindings. However you make me consider that it could be that I am running Photoshop at the same time (to show me a diagram of my Keybindings!) I will test without PS open. It may be doing something in the background that is generating these actions. Thanks.

[Magneto]

I have been testing with nothing else running and a clean re-boot but I still have the same issue.

[Panzerlang]

Sounds like a hardware issue to me. Loose wire or cross-contact or something.

[Magneto]

Changed from the USB 2.0 to the USB 3.0 Ports, seems a waste but it works properly now so far.

[-332FG-Gordon200]

@Magneto Open Device Manager and expand the line that reads Universal Serial Bus controllers. Double click an item and select Power Management tab. Make sure the box "Allow the computer to turn off this device to save power" is NOT checked.

You will need to do this for each item in the Universal Serial Bus controller section.

[56RAF_Roblex]

9 hours ago, Magneto said:

Changed from the USB 2.0 to the USB 3.0 Ports, seems a waste but it works properly now so far.

 

You can sometimes get conflicts with USBs as well.   The PC uses things called IRQs to tell the OS that a particular device wants a signal processed.   It can happen that you install a new device and it gets assigned an IRQ number that is already in use by another device so random things start happening on one or both of the devices.  Google 'IRQ conflict'