


Other than the mouse pointer being inacurrate (found a fix for that), all other functions of the game performed flawlessly. No other issues
mangohud %command%
The game starts in Fullscreen, but the mouse cursor is not centered. In order to click something, you must click to the side of the icon. My fix was switching to "Windowed" and then back to "fullscreen". I am running Bazzite. So, for my specific Distro, once I went into "windowed" mode, I had to double click the title bar of the Flight Sim application to get it to recenter. Once it was recentered, I could then revert back to fullscreen and the mouse is aligned properly.
The normal Proton layer provided by steam will work, but I personally found much better performace using the GE-Proton10-4

PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
Found a few missing textures in Career mode, but they cleared up quickly enough.
If you're having problems with MSFS 2024 detecting your HOTAS, I would recommend double-checking the udev
permissions for the devices. There is a huge chance that they're set so that only root
can see the hidraw
(/dev/hidraw*
) devices and this means that MSFS 2024 cannot use them properly.
To remedy, I added the 60-steam-input.rules
file to /etc/udev/rules.d
with the following contents:
# VKB Stuff
KERNEL=="hidraw*", ATTRS{idVendor}=="231d", ATTRS{idProduct}=="0126", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="231d", ATTRS{idProduct}=="012d", MODE="0666"
Your Vendor/Product IDs will be different depending on your HOTAS setup. A quick lsusb
will show you what the Vendor/Product IDs should be.

mangohud PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
Starts by default in Window mode. Have to use Alt+Enter to toggle FS on and off, it then it switches to full screen
Works pretty smooth on my AMD 9070 GPU, and the frametimes are smoother than on Windows.

The game launches after SU2, but requires proton experimental to run. Do not put your Steam Deck into sleep mode when in game or your game will be disconnected. Once connection is reestablished, you'll be sent to the main menu.

I only do free flight, but so far everything works except for the video during the startup screen (but who cares?). My WinWing joystick works fine. No major graphical or stability issues yet. Loading and scenery download does seem maybe a little slower than on Windows. In some dialogs, the hovering the cursor directly over the button doesn't work, and you have to move it away a little bit to get it to focus on the button. Annoying, but not a big deal. I haven't tried VR, because my experience with that on Linux hasn't been great.

opentrack-launcher %command% -FastLaunch VKD3D_CONFIG="enable_experimental_features" PROTON_ENABLE_NVAPI=1
My VKB HOTAS & Throttle do not work anymore
My HOTAS is not being detected after working just fine for months. thanks microsoft & asobo again for ruining every euro i spent on this game over and over again.

Have been waiting for quite some time, seems to be infinitely loading
Go to free flight, pick a spot, set departure, try and start Maybe it will work after 20-30 mins or smth but I would call this unplayable.

Textures are slower to load and download
Initial loading times are degraded
Rolling Cache doesn't appear to function
On Proton Experiemental (Bleeding Edge); opening videos are broken. These appear to be fixed in GE-Proton9-27; however both experience some loading issues compared to Windows.

runs perfectly at first the loadingscreen video wasnt showing but it was a easy fix after seeing a youtube video how to fix it

Works now on Steam/Linux
The assertion window box is now gone, game plays fine in Linux ^_^

It works fine with Proton Experimental Bleeding Edge (select Proton Experimental/Betas/bleeding-edge) from 18th of March.
PROTON_ENABLE_NVAPI=1 %command%
I am not sure if PROTON_ENABLE_NVAPI=1 %command% is still needed

VKD3D_CONFIG="enable_experimental_features" %command% -FastLaunch
After the SU1 update, the game started to crash. But Proton Hotfix fixes this problem and the game worked without any problems.
fails to launch after SU1

game doesn't start since the update
with different Proton or GE-Proton versions i get at best a short blackscreen bevore the game crashes or exits

Update 1 broke it. No longer starts.
Tried multiple flavors of Proton and several command line options, nothing works. The game looks like it's about to start for a few seconds (the screen briefly flashes / adjust resolution), then it crashes back to steam.

The big update that just released has broken the game on Linux mint; the game fails to launch entirely, eventually just returning to Steam.

The big update that just released has broken the game on Steam Deck; the game fails to launch entirely, eventually just returning to Steam.

One big downside: LOADING. It takes a literal 10-15 minutes for the game to fully load EACH time you boot the game. But once you're in, stuff loads pretty quickly - much more quickly than the awful 2020 load times. Also the loading UX is awesome, it basically zooms in on your plane, giving you a real sense of scale before you start flying.
Outside of that initial loading, this was pleasantly better looking and performing than the Steam version of MSFS2020. I have been playing a bunch both docked and undocked. Very fun experience.

text in flight panels/control menus is borked at times
Game chugs hard when on the ground
some random crashes and infinite loading screens

Loading video doesn't loop

now after new release the game is playable - works good on nvidia
after the new game update 30.01.25 microsoft flight sim is now playable without any big errors - performance could be better. a small crash when exiting the game.
I am using the game in fedora/steam standard without any parameters.

Once you get the graphics dialed in for your setup, (including turning off grass for all nvidia cards) it behaves great.
PROTON_ENABLE_NVAPI=1 PROTON_LOG=1 VKD3D_CONFIG="enable_experimental_features" %command% -FastLaunch
had to turn off Grass in advanced graphics or game would crash every time you render in grass. I turned off all other ground items as well, but grass seams to be the big issue.
The errors when loading seem to go away with bleeding-edge proton.
Beta caused game to abort even when FastLaunch is specified
%command% -FastLaunch

Works perfectly on a NVIDIA GPU if you completely disable grass in the advanced graphics settings
%command% -FastLaunch
I'm getting an assertion failed "!status && "vkCreateGraphicsPipelines"" when starting the game but it continues to load regardless and works perfectly

I can start and get in to a plane but when taxiing to runway the game crashes
-FastLaunch
The error that I got "Assertion failed! Expression: "!status && "vkCreateGraphicsPiplines""

Still needs a lot of work...
%command% -FastLaunch
It seems like its having a hard time processing all of the streaming content that 2024 does. For those not in the know, 2024 streams a lot of the game in from the servers in addition to all of the 'live' or time based data. This on top of the existing weather, environment, maps, ets data that the prior version had. This would explain why the sim seems to work fine, but then chokes and WINE freezes up when processing something after a few shudders. Likely something in the netcode, decompression, or processing of the streamed data.
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" gamemoderun mangohud %command% -FastLaunch

-FastLaunch
Audio crackles and breaks up when flying at high speedsl
The game opens in full screen, except the area where GNOME's top bar is, which is blank. Toggling full screen fixes that issue.
It could not detect my Saitek X45, whereas it detects it on my windows install.
When flying at high velocities, I get stutters and slowdowns, especially over populated areas.
- opening video doesn't loop, freezes.
- Live traffic fails to load
- assests load in slower than on windows on the same hardware and network
Overall, this is running in much better shape than it was at launch. Still got issues but perfectly playable now.

HOTAS/Joystick, mouse/keyboard detected, rudder pedals do not show up as a valid controller.
I can only run one mission per game launch. I complete one, once I open another to briefing window the game crashes to desktop. Only workaround is to restart game, make sure there are no lingering processes running before restarting (ps -aef | grep -i steam).
As noted in previous posts make sure bleeding edge beta version of proton experimental is enabled or game will crash to desktop on launch.

Not really playable if you use a NVIDIA GPU, which causes a freeze when starting at an airport
Crackling and cutting out audio during intro
Major stutters in the intro movie and the menus
Crashes by freezing whenever starting on the ground when airplane und runway is loaded and in view (with Assertion failed! File: ../src-wine/dlls/winevulkan/loader_thunks.c Line: 2971 Expression: "!status && "vkCreateGraphicsPipelines"").
This does not happen when starting a flight up in the air (by selecting Departure on a non-airport point on the map). You can even touch down and land on the oceans (probably a bug) which does not cause a crash.
Looking at other reports suggests that this issue is impacting most NVIDIA systems.
Mouse cursor is slightly misaligned with the actual pointer location
Used bleeding edge proton experimental

PROTON_HIDE_NVIDIA_GPU=0 PROTON_USE_DXVK=1 PROTON_ENABLE_NVAPI=1 %command% -FastLaunch
Crashes if you get close to ground, or when you are on ground at airport, once you start to taxi.
You will get an error as it loads, but if you ignore it and click the game again, you will eventually load into the menu. You can fly as long as you start airborne and don't land.
Menus and career character creator work fine, but game freezes when trying to start a flight
PROTON_ENABLE_NVAPI=1 PROTON_LOG=1 VKD3D_CONFIG="enable_experimental_features" %command% -FastLaunch

This game runs fine. I was getting around 50-60 fps, it was a little laggy, but my graphics card only has 4gb of vram, so I understand.
I'm not sure if there have been significant updates, but the problems people have been reporting aren't with proton and may be with hardware. If the game runs on my crappy harware, it should run fine on better hardware.

PROTON_ENABLE_NVAPI=1 PROTON_LOG=1 %command%
Converted videos in Startup to vp9 https://www.youtube.com/watch?v=YkdbNlJR84k
Reduced quality of geometry and co on same settings. Significantly less sharp rendering than on windows
Random lagspikes
during loading and after getting into the world

PROTON_ENABLE_NVAPI=1 PROTON_LOG=1 VKD3D_CONFIG="enable_experimental_features" %command% -FastLaunch
Only works when I start flying. When I start flying from the ground I get a crash. I also seem to get a crash when I get a little too close to the ground (but I don't hit the ground, for those wondering.)
It seems that part of the crashing problem on Nvidia cards comes from the terrain generation.
The problem clearly comes from NVidia cards, since the bugs do not seem to be present on AMD cards.
There is not much missing for the game to be usable.

WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=2 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG="enable_experimental_features" %command% -FastLaunch
I needed to activate the "Bleeding-Edge" beta channel for Proton Experimental. As mentioned by Madame Presse-étoupe in another comment below.
quote of Madame Presse-étoupe:
- search "Proton" in your library and find the experimental flavour,
- open properties as you would for a game,
- go to the Betas tab, and pick the bleeding edge channel,
- Profit.
After that the game runs flawlessly.