Unknown
game-performance %command%
I added the launch option due to the screen dimming or turning off while playing with a HOTAS. Playing with KBM or gamepad doesn't have this issue.
Installing mods for the 2.0 build is much more feasible on Linux, as there is less reliance on Project Sicario Merger (and thus Vortex). However, whenever new textures (eg. plane skins) were added, the frame rate would drop to sub-15 FPS unless all the settings were turned down. I'm assuming this is compiling Vulkan shaders for the mod content, since it does evenually even out, and it performs as expected going forward. Launching the game does take noticably longer when a significant amount of mods need to be loaded.
Slightly lower performance than on Windows, but everything works as expected.
Small artifacts at border. Overall illumination seems off but I corrected it setting the gamma to max.
Had a crash once in the Frontline 59 campaign.
gamemoderun %command%
I set the launch option due to KDE Plasma dimming or eventually turning off my screen due to not detecting mouse/keyboard input (I play with controller) and this game doesn't seem to inhibit screensaver like others do. Not everyone will experience this. On launch all settings were automatically maxed out. Had a brief minor slowdown in Mission 3 while fighting over an airfield. I since turned down the resolution scale and cloud distance to see if it helps. Again, not everyone will experience an issue like this depending on your own settings.
Crashed once after switching to GE-Proton, but shortly after a misson failure, so no notable progress was lost
When running with Proton 9.0-3, the game crashed right at the end of the first mission without saving progress. Not sure if this had to do with the Proton version or was just an anomaly, but it worked fine after switching to GloriousEggroll Proton, save for the one less-consequential crash mentioned above.
GE did some things automatically, haven't chosen anything myself
Sometimes getting artifacts at screen edge, only post current update
Other Proton versions give a black screen and "serialisation error" (game doesn't run).
Desktop mode worked straight out of the box.
VR had an issue with my existing install and Gnome 47 upgraded OS.
Probably not an issue on fresh installs if the game.
Reinstalling the game fixed it.
Dont know what caused it, dont care.
Was a simple "fix".
gamemoderun mangohud %command%
Occasionally a slight graphics flicker
Beta branch is unplayable due to the clouds glitch. Sadly it offers also a lots of new QoL changes and performance fixes.
Limited TDP to 15W
Heavily artefacted volumetric cloud and smoke effects greatly reducing the overal targets and terrain visibility
Beta branch has many QoL fixes and should be considered as definitve way to play the game.But it's unpleasnt experience due to visual bugs.
Limited TDP to 15W
Heavily artefacted volumetric clouds and smoke effects in the Beta branch
flickering on planes and environment with DXVK
I recommend to use HUD Only camera if you're uncomfortable with the flickering. Proton 7 WineD3D used to fixed this, but it has a massive performance cost. Proton 8 WineD3D only shows red on the whole screen so it doesn't work.
Works really well, could play the whole game
Fullscreen has some glitches, but putting it in windowed borderless made it the same and worked perfectly
Game works, but doesn't run as well.
Game performance is signifantly worse compared to running on Windows with the same hardware.
If you play on a potato, then don't bother.
Some text in the menus is hard to read, but when in missions it's fine. Doesn't significantly affect gameplay.
Navigating menus with the default layout can be a bit awkward but in the missions (which is what you'll be actually playing) there weren't any issues. Lowered down the graphics settings and performance was good. Had a good time playing it on the deck.
proton 8. runs flawlessly for now
will update once i finish.
Playing OOB
Disregard my previous report. Updated graphics driver, added necessary configuration and it worked without any issues.
Strange, but not working at all
Tried every proton version, that I could, even GE one. No results at all, even no error...
Aircraft loadout selection can be hard to read
Worked almost flawlessly, had to change my graphical settings from my synced save to achieve a smooth 60fps
runs just fine just lower resolution or graphics settings for a higher fps
Game runs perfectly fine on SteamDeck, keep it at 720p Don't put it on 150% resolution for more fps
Works perfectly fine
haven't played a whole lot of it but literally no idea why it's tagged as unsupported
Runs out of the box, played the entire campaign with no issues.
Very rare frame drops, I suspect it would've happened on Windows too.
I am not sure how well it runs on Windows 10, but framerate was smooth and stable on my playthrough, so it's good enough for me.
The intro cutscene appears correctly with the current Proton 3.6x and experimental builds. Gameplay is mint.
Undetects my HOTAS sometimes. The binds are still there, but I guess device IDs changed. Controller input is fine.
Splash comes up, doesn't run beyond that
Tired with multiple GE and stock proton versions...they all load the splash screen, but will not advance past that point.
Works well out of the box!
Game tested on both Flatpak and LXD(Ubuntu 21) containers running under a Funtoo(Gentoo) linux 1.4. The game doesn't have any problems with the newest proton version and launches as usual, on older versions it needs the following protontricks command in order to work
protontricks 895870 d3dcompiler_47
