I’ve been using a T.Flight HOTAS One successfully with FS 2020; but that changed this afternoon after the latest patch was applied.
Before starting the sim, I checked the controls in the control setup area - the throttle and joystick were both responsive and bound correctly. However, once I start the simulator, the engine throttles up and the airplane starts rolling down the runway immediately. In game, there’s no throttle, no braking and no way to control the flight surfaces. I can’t even control them through the keyboard.
Any suggestions? At this point, the simulator is unplayable.
6 Likes
I’m having the same problem with my Honeycomb Alpha. Everything shows correct in settings, but as soon as I launch, nothing. When I went back to setting to verify the changes had taken effect, it did not read any input from the yoke. Verifying function in Windows shows that windows detects it, but the game does not.
1 Like
I had this happen when going to change some bindings. None of the binds worked after I went into the menu and I tried for a few minutes to get them back. About half the time no bindings were showing in the menu and sometimes they would.
Closed and restarted the game and they were working again.
Tried a few times, this is day two of the issue.
1 Like
Have you tried setting all controls back to default?
Did you unplug all your input devices including mice and keyboard and them plug them back in? That should force a reassignment in your internal usb hub.
My Honeycomb Alpha works fine after the update.
Also make sure in Win 10 devices it still sees the Alpha fine and not a driver error for some reason I sometimes have to unplug and plug in the cable to again to get Win 10 to recognize the yoke. A telling sign is that the LEDs are not lit on the Yoke then I know the Yoke and Win 10 are not talkiing to each other.
I have encountered similar issues. On occasions nothing is recognized; keyboard, mouse nor joystick… although the options menu shows all as correctly bound and tested working.
Restarting MSFS solves it.
Definitely not driver issue as the Option menu shows correct bound and tests okay.
I’ve had this a few times.
Can’t even use mouse to control the camera, although I can select stuff on the menu at the top.
If I quit out to the menu and go into controller settings everything responds as normal, back to the flight, nothing works.
Quitting MSFS completely and restarting fixes it, but it’s not exactly quick restarting, waiting for it all to load and getting back to the point you’re in the cockpit ready to fly again.
I will add that this has happened across three separate FS installs, across two different PCs, my old one and a brand new build and with my previous wired Xbox controller and my new X56 HOTAS, so pretty certain it’s not hardware related.
I developed the same issue 2 days ago, Nov 26. Following latest update, unable to use FS2020, throttle stuck in full power, no flying surface control, most cockpit clickable cockpit functions do not work, on all planes, Plane takes off and cannot be controlled. It is not a hardware issue since all work on XPLane. Keyboard functions do not work, mouse and Cam views work. FS2020 totally unusable at the moment. Replaced keyboard to test, same issue. Uninstalled and re-installed FS2020 no change. I just reported it to the Zendesk. No idea what has caused this. Anyone has observed this behavior?
1 Like
It’s nice to see the problem is more WIDESPREAD (tongue firmly in cheek). My Saitek has been doing this all along since day one. Maybe now they will find and fix it.
Ah…problem is that even without any joystick i cannot use FS2020. It stays full power and unable to control. This happened post mandatory update 2 days ago. I am only using keyboard and mouse to eliminate any 3rd party devices. Most if not all clickable switches and handles do not work either. This happens on all planes, all activities etc so must be related to the internal " engine" of FS. STRANGE…
I still cannot get the game to work. Un-installed a few times and re-installed. What is even more weird is that if i start a plane from cold at a gate say, it pushes back by itself and starts the engines by itself but i cannot do anything since it will not accept any keyboard or joystick commands however at this stage the clickable button in the cockpit will work. The whole thing seem very messed up.
Would be nice to figure this out because as it stands FS2020 is just taking hard drive space and totally unusable.
Check that Charlie the AI Co-Pilot is not enabled, in the in-flight taskbar at the top of the screen. I’m guessing this because T/O was automatic, as opposed to a stuck bind.
Thank you that resolved a lot of issues. I was focused on changing under assistance and never thought of AI. Thanks again, strange how it switched itself post upgrade.
Good deal. Please consider marking the post that helped you as the “Solution” so others when reading your post know that it was resolved and how.
1 Like
I am not able to. I did some reading and the … when i click on them to select Solutions it only gives me Delete option only.
Same thing here …logitec extreme pro joystick, Saitec pedals, plus mouse and keyboard controls stick randomly. , very annoying. It was fine until the latest update. Restarting msfs does not help me and that’s the other thing…it now takes 12 minutes to load msfs…80% longer than it used to. And I have a fast system
Plus one more thing…every time I want to purchase scenery through msfs I usually have to go through the purchase process twice for it to work. COME ON MS GET WITH IT AND FIX THIS MESS !
Ran into similar problem yesterday: Copied a 2 prop binding into a 3 prop file (for JU52) and wanted to modify this. However new bindings were accepted while previous bindings came back, no matter how often I tried to clear them.
Work around: Set new bindings, get into the “assigned” mode, clear all nonsense left-over bindings, save immediately(!) and resume flight mode. Come back to setup and check validity.
Possibly - that’s what I’m gessing, only! - MSFS is synchronizing with cloud data, always re-installing bindings while user is in setup mode. This synchronizing is something I’d really like to suppress. I’m flying on one machine only: I don’t need no cloud synch at all!