I’m running a completely stock version of FS2020 from the Microsoft Store.
After the recent “mandatory” update, I can not select an airport from the world map upon start up. The map just keeps rotating westward slowly (rotating towards the right, moving the view westbound). If I try to select an airport, the option to select “departure” or “arrival” just flicker on and off, and I can’t select anything. The map just keeps rotating no matter what I do. I can grab the map and move it with my mouse, but as soon as I release hold on the mouse button, it goes right back to rotating, or drifting, to the west.
PC Specs:
- Ryzen 5600x, ASUS ToughGaming B550 Motherboard, OC 4.4ghz
- MSI Core Liquid 240r Cooler
- 64gb DDR4 Neo Forza 3200mhz
- 1TB m2 Dedicated to FS2020
- Nvidia RTX 2070 Super 8gb
Game Controllers:
- Honeycomb Alpha
- Honeycomb Bravo
- Logitech Flight Rudder Peddles Pro
Monitors:
- 5 Standard 1080p Monitors, working independent (not nvidia surround)
- 2 10" touch screen monitors, also independent
I have not reported this to ZenDesk yet. Looking to see if others are having the same issue first. After this update though, I have lots of issues to report… Aside from the map drifting, my touchscreen monitors don’t work right anymore in game, I cant turn dials in the cockpit with my mouse anymore, had a CTD after I was 80miles out from my destination on an 8 hour flight… I’m sure I’ll find many more. Runs smooth though…
Do you have a gamepad hooked up? For now I have left mine unplugged which fixed map floating around for me. Also for selecting dep/arr, i found that at various zoom levels it will let you select them, but not when zoomed close up.
2 Likes
Thanks for the Suggestion.
Zoom level doesn’t make a difference for me. In fact, if I use my mouse to look around, the map rotates even while holding the mouse button. The only way I can select an airport is by doing a search and selecting it from the drop down while the map keeps spinning.
I don’t have any real gamepads hooked up. What I mean by that, is I have a keypad (like a mini programable keyboard) that I use a program called UCR with, which makes my keypad emulate a game controller. I use this so I can have functions such as ATC through “gamepad” buttons, rather than keystroke. The keypad does not have an “axis” programmed on it. Just buttons.
I can try to disconnect the keypad and see if it makes a difference… But if I can’t use it anymore, than that’s $80 down the drain along with loss of many quick action functions that I used to use. If I can’t use that anymore, than that’s just another hardware investment into this game that is now useless. So far this update has killed functionality of both my touchscreen monitors… If it kills the gamepad too, now thats around $300 of hardware I purchased that used to work that I can no longer use… No bueno…
1 Like
Had same phenomenon. Checked my graphic settings (I have a record of what it was prior to SU5, on paper…) and found that changes have crept in. Reset all to what it was prior to SU5. Problem solved. Don’t ask how can, no idea. Hope this helps you too.
Well even though it took them months to implement functional rudder control after the game was released, they did so im sure they will eventually have this stuff fixed. If not then a lot of people who paid over a hundred bucks for the game will be very unhappy.
In game graphics settings, or Nvidia Control Panel graphics settings?
Well, looks like @OutEquation2905 was on the right track. I disabled my virtual gamepad (for my keypad) and the spinning stopped. I’m guessing since it’s a “virtual 360 controller”, FS2020 wants to make it the default menu controller (probably because of Xbox). In the FS “Controller Options” menu, I have all the menu functions cleared out for the “controller” (always have), but FS still wants to use it for menus.
I’ll just have to retire my keypad for now, I guess. I think the best way to fix this would be for the developers to make an option to select the default menu controller, or even better, disable certain controllers from being able to have any menu control at all.
Thanks for the input guys. I’m off to figure out if it’s possible to get my touch screens going again…
Well does your keypad have any analog inputs? For me, adding 10 percent deadzones to each analog stick direction solved it for me, well until the game crashes lol.
1 Like
The keypad is literally just a mini blank keyboard. It’s a bunch of black and white keys in a square shape that I’ve slapped some stickers on - nothing more. There aren’t any axis assigned to it. However, when it becomes a “virtual gamepad”, there might be a “virtual” axis’, even if they’re not assigned…
Raising the dead zone is a good idea. I’ll see if FS is recognizing an axis and try raising the dead zone up all the way on the “Controller Options” page, and see if that deadens it out. If there’s an axis on it, it’s not used anyways!
Please mark the post that solved your problem by using the checkbox icon immediately below it. This marks the thread as solved and helps future readers with similar problems. Thanks.
It worked! It looks like the virtual controller had both stick axis, even though they weren’t in use. I maxed out the dead zones, and no more spinning! I’ll mark your answer as the solution.
Now I just need to get touch screens working again (probably need to wait for an update).
Thanks for the suggestions!
It’s 2024 and I’m playing this game with just a keyboard and mouse and I still have this problem