bonkmaykr
Published
Dualshock controller through Steam Input would not pick up again after a momentary cable failure caused a disconnect. I had to restart the game to reconnect my controller
WSOD when leaving a race on Proton 8, use Proton Experimental to fix this
The game will not be able to connect to the server when first installed. This is a weird glitch that happens with the game's settings files. It happens for some Windows users, but consistently occurs each time the game is installed on Linux.
To fix this bug, you must switch server regions (if you're in america for example, switch to europe) then switch back. This rewrites your server config and lets the game connect properly. It only needs to be done the first time you play.
Everything else runs perfectly out of the box.
gamemoderun gamescope -W 3440 -H 1440 -f -e -r 165 -- %command%
Tweaks made for precise mouse sensitivty control, FOV adjustments (didn't work), setting as read-only causes the game to freeze if on ext4 and is not possible on NTFS so there is only so much config editing you can do.
The older Call of Duty games are not compatible with some XOrg multi-monitor setups, depending on the DE you use. Older DEs and WMs which don't correct mouse snapping bugs (your cursor snapping to the center of the virtual X display across all your montiors) will cause the game to be unplayable since the camera can't be controlled. This can be fixed with Gamescope, but that causes other performance issues.
Framerate felt inconsistent, even when aiming for a low framerate target.
Freezes on occasion especially when saving/loading config, force quit breaks Proton permanently until system restart.
Networking was an absolute nightmare, more packet loss than you can shake a stick at and it got worse and worse the higher the framerate was.
Only works for me on Steam Deck w/ controller input, significant game-breaking issues on desktop. Requires Gamescope to function.
xinput set-prop 'SteelSeries SteelSeries Rival 3' 'Coordinate Transformation Matrix' 1 0 0 0 1 0 0 0 1; DXVK_AYSNC=1 PROTON_NO_ESYNC=1 gamemoderun %command%; xinput set-prop 'SteelSeries SteelSeries Rival 3' 'Coordinate Transformation Matrix' 0.43 0 0 0 0.43 0 0 0 1
When playing at non-native res, the game frequently forgets what resolution it's running at when going back to the menus and/or when alt-tabbing out of the game, and so the mouse input will be offset from where your cursor is. Only an issue for ultrawide displays. Navigate menus with the keyboard to avoid problems.
Gamescope can fix this on XWayland-compatible hardware. Xephyr can fix these issues as well but CoD crashes on startup when using Xephyr. NVIDIA users should seek other, more performant solutions.
If you set your desktop mouse sensitivity using xinput instead of the desktop environment's own sensitivity adjustment, X11 will get confused and you will spin around endlessly. Changing the sensitivity scale back to 1 before launching the game fixes this, but mouse input can flick around sporadically on rare occasions anyway. Something to keep in mind for users using very old desktop environments without sensivity settings built in.
Framerate was tolerable but was at least 70% less than on Windows. 140+ FPS average instead of 350 - 800. Could be a much bigger deal on a weaker card.
Input lag on X11 fixed by using PROTON_NO_ESYNC=1
Softlocks and freezes at random particularly before or during loading screens.
If you don't have the aforementioned mouse sensitivty problem then you can delete the xinput commands from the launch options above.
gamemoderun %command% -w 3440 -h 1440
Since switching to KDE 3.0 (Trinity) CS2 has a difficult time figuring out which monitor to appear on and what resolution your monitor actually is--it can pretty easily get confused if you have a multi monitor setup with varying resolutions and refresh rates and since the option to select a display doesn't exist in the game's settings it can take a bit of coercion to get the game to behave. After that first hurdle though, it typically works as expected.
Source 2's Vulkan implementation evidently is not finished yet, but runs okay enough.
How well this game runs depends heavily on the way your system is configured. If you're playing on a Steam Deck you don't need to do anything but set up the controller.
The game runs okay, but you may need to jump a little above the system requirements.
Bloodstains in the final boss fight near slipgates have too low of a render distance.
Extra framerate fluctuation. Game runs worse at 720p lowest settings on Linux than it does on Windows at 900p to 1080p with the same settings. Using a GTX 1050 2GB (underpowered, but able to play the game fine under Windows.)
Using the latest NVidia Geforce proprietary driver, but the game does not detect it, it detects a much older version.
Game was run using Lutris and Steam + Wine.
Audio needs work. CPU maxes out at all times.
Audio crackles like it's nobody's f'ing business. When pulling up the performance metrics overlay from the game settings, it shows the CPU is at 100% usage at all times. Something I did not experience on Windows (even on a considerably less powerful system). Running the game on the i5-8400 and a freshly installed GTX 1060 3GB.
It does detect the right graphics driver, but the game's launcher will say otherwise, often mistaking the latest NVIDIA proprietary driver for an older version.
Runs great.
The game will not run using the DirectX 7 API, you must use OpenGL.
The new anticheat update completely destroys all Linux support.
Epic Games bought Easy Anticheat and discontinued linux support last I heard, not to mention that EAC does NOT WORK WHATSOEVER as I have seen many cheaters bypass it with ease in games like Robocraft. EAC is not Wine-friendly and therefore will detect if you are using a linux machine and promptly prevent the game from being played. You MUST run the game natively on linux (some EAC games have managed to do this, Robocraft is a good example.) or else the anticheat will not let you play. Until the developers either find a new anticheat, disable it (which they won't, considering the large number of cheaters in Fall Guys), or add native linux support using a Linux version of EAC, the game is litterally unplayable.
Additionally, the game runs less favorably than I remember. On windows, the GTX 1050 could push out Fall Guys at 60 fps on the highest settings in 1920x1080, but under Wine with the same hardware and drivers, it begins lagging the moment a single 3D model appears on the screen, no matter your ingame configuration.
Playable with Nightly Proton Experimental. Minor features are broken or unreliable, but nothing really that inconvenient.
Certain controls get confused while NumLock is enabled. To my knowledge, this only affects the keybinds menu and for some reason the ability to use voice chat. Just turn NumLock off while playing.
Video recordings generated from demo files did not save. You'll need your own recording software to share match demos with friends.
Unreal Engine 5 games require Proton Experimental to run correctly, sometimes nightly builds. Playing with the default Proton 9 is a painful experience.
Works out of the box usually but has some drawbacks.
Attempting to change to non-native resolution while in fullscreen causes the desktop environment to softlock (KDE Plasma).
Slower performance than normal, especially compared to Windows. For some reason it cleared up after opening the game a few times again. However, one map in particular happened to have horrible framerates regardless of settings. Overall very inconsistent performance where the game otherwise would run just fine. Using a GTX 1050 2GB
5.21 GE
VSync is enabled by default, disable it.
If you need to reduce screen tearing, use your DE's compositor.
Game refuses to render at even a remotely decent resolution, everything is blocky and pixelated despite it recognizing my display fine.
See below
Crashed the game mode DE the first time when attempting to get through the main menu, basically caused the system to restart. No further stability issues.
EAC fails to load. Linux binaries were disabled right before launch.
It was working fine back in open beta so I have no clue wtf they did or why. Once again just like with Paladins they have zero excuse since Unreal has native Linux support and so does EAC.
Another game boned by a lazy developer and EAC
Literally all Evil Mojo had to do was flip a switch for Linux support and they won't do it. But they'll go out of their way to block ultrawide displays because "le competitiveness".
I love this game but if you want a hero shooter on Linux you're going to have to stick to Overwatch.
5.21 GE
The RECOMMENDED graphics card is the GTX 1050 2GB. I am using a somewhat more powerful card, the 1060 3GB, and it runs like garbage.
6.1-GE-2 GloriousEggroll
add "+r_rhirenderfamily opengl" to your launch options if the game crashes immediately after clicking play and doesn't get to the Bethesda logo.
The menu FPS cap going nuts is a huge annoyance and makes going from one event to another an absolute slog.
This doesn't technically count as an input issue (my controller worked fine) but any controls that had custom binds were wiped clean and unbound after running the game from my Steam Cloud save, even though I was using the same controller I always use.
Framerate caps itself and becomes nearly unusable when returning to the menu from an event, will go back to normal when graphics settings are changed.
Performance with Proton is not perfected enough to run this game at a decent framerate, even far above recommended specs.
Game would start out fine. After each loading screen the performance would take a massive hit. Lower settings. Performance hit again. Lower settings. Performance hit again. Restart.
VR modes were not tested. Oculus support on Linux is pretty garbage at the moment so don't expect to play this game in VR anyway.
Community forks did not help the performance of this game.
The game runs in the Unity engine, making it very easy to run under Proton or Wine. It runs just like the Windows version should.
Runs amazingly but has some problems with KDE Plasma.
Attempting to change to non-native resolution while in fullscreen causes the desktop environment to softlock (KDE Plasma).
The Linux port is a serious hackjob but it does work.
Game doesn't center cursor correctly. Seems like Freejam just dropped a Linux port hoping Unity would handle it all. Still technically playable though. Just maybe don't use the map ping key and you're fine.
As good as this dead game will ever get.
If you were planning on playing this game, I would do so now before it's too late. I can't see Freejam supporting it for too much longer. Been playing since 2017 and it has seen better days.
Performance was at least double that I was getting on Windows. Getting "competitive" framerates was impossible until I played using Proton.
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %process%
Mouse would snap to left side of screen whenever the game unlocked the mouse cursor, this made using the ping wheel extremely annoying. Might have to do with my dual monitor setup on TDE...?
Launch options required to get EAC working. NVAPI might need to be force enabled for GeForce users (have not tested).
Some distributions ship with a low memory map limit, The Finals requires this be set very high or it will crash very often. If you're on Arch or eOS you do not need to do anything but for anyone else I would suggest running sudo sysctl -w vm.max_map_count=2147483642 to take care of this.
New update broke the game.
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %process%
:/ right after i spent 20 dollars on skins, funny enough.
Please just launch a native Linux port already. UE5 and EAC are both native to linux. it takes you like zero effort, Embark.
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %process%
DLSS is no longer detected.
2.8 update broke the game on all builds of proton except for the bleeding edge build. You need to go to Proton Experimental in your steam library and set it to the beta branch in order for the game to work. DLSS no longer seems to work at all
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %process%
Anticheat fails to initialize during some sessions.
When using Proton Experimental, DLSS no longer works. When using Proton 9, DLSS works but the Steam Overlay does not, at least for me.
Certain features are unstable and the anticheat in particular has issues initializing correctly around 50% of the time the game is launched so restarting the game is sometimes necessary to avoid being kicked. DLSS and the Steam Overlay are unreliable. Updates frequently break older Proton versions.
Latest patch crashes at startup.
gamemoderun PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 %command%
Playable out of the box usually but prone to breaking a lot. Needs tweaks to keep running.
gamemoderun PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 %command%
Some kind of update to either Proton or Trinity Desktop has made my mouse not lock into the window 24/7 so sometimes the game just spontaneously loses focus. It hasn't happened mid-firefight yet but it is annoying. This isn't really a THE FINALS issue and more of just an issue with tons of Windows games this past month.
Sometimes your config file will get corrupted, and you will be permanently unable to play until you delete it. You will know this has happened when after 5~ consecutive restarts the game still gives you "Kicked from Server" "TFGE0027". To fix this, backup your EmbarkOptionSaveGame.sav and EmbarkSaveGameClientKeyBindings.sav plus your graphics settings, then delete the Proton prefix to completely reset everything.
Very miniscule loss in performance in-game. Drastic FPS drop in menus but nothing that really matters. Most players probably won't notice it or won't even experience this at all.
EAC fails to initialize 50% of the time the game is launched and you will need to restart THE FINALS at times to avoid getting kicked immediately with "TFGE0027" after joining a server. Always queue for practice range at the start of your session to check for this.
If Idle Energy Saving or Out-of-focus energy saving are enabled the game will sometimes randomly cap itself to 20~ FPS until the next restart. Disable these settings to fix it.
Usually after major updates the game will just randomly crash due to the UE5 crash handler or some other binary incompatibility, these are almost always fixed within 12~ hours by Proton upstream in Proton Experimental's bleeding-edge branch which is why I play on that. You can definitely play using the stable branch of Proton but you shouldn't expect it to be reliable.
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %command%; pkill xpointerbarrier
Window managers that rely on xinput for setting the sensitivity will cause input problems when using the communication wheel, reset your sensitivity to 100% if this affects you. If your cursor escapes the edge of the screen, use xpointerbarrier with a margin of 15 pixels.
Very rarely, your settings may get slightly borked and this can cause an integrity check to fail when loading into a server. This is one of the causes of TFGE0027.
Starting with update 3.8, game freezes are not uncommon and happen in something like 8% of tournaments.
Do not play this game on an NTFS drive. EAC really does not like it. Moving it to EXT4 drastically reduces the chance of you getting the TFGE0027 error.
Please read my guide as I will be updating it with a comprehensive list of fixes and workarounds for every problem this game has: https://bonkmaykr.xyz/content/discovery_lin.htm
Runs amazing on latest Proton, Origin has some problems but overall it plays just like on windows a majority of the time.
Used pre-existing Origin install script available from Lutris.net and launched the game by using Steam to run Lutris to run Origin, this is so that the Steam overlay will start. Steam will still show game status until Wine and Lutris are killed, this is a Steam bug. Proton version: 5.21 GE
FPS drops now and then, although very rarely. Game still runs great as long as fsync is enabled. DO NOT DISABLE FSYNC!!!!
Game crashes randomly during multiplayer matches. It's very rare but it can be annoying since there is no Rejoin Match feature.
Rarely, the game will show an error saying "File Corruption Detected, please reinstall", this is a file read/write error which can be fixed by killing Wine and restarting Origin.
At another point Origin actually got corrupted (legit) and I had to reinstall it manually and reinsert the game files into the Origin Games folder.
Both of these problems only occured once.
Make sure to disable the Origin overlay in Origin's settings or else it will cause a lot of jankiness, as Origin's UI uses some very unconventional methods that Wine and Proton do not fully support yet. However, keep in mind, you will not be able to make in-app purchases with the Origin overlay disabled.
ABSOLUTELY RUNS GREAT! Just disable VSync. Don't worry, the screen tearing shouldnt be noticable.
Enabling VSync can cause noticable extra latency, although this should be expected. It is slightly higher than it normally was for me when running the game on Windows, though.
5.21 GE
Game crashes when the player dies in Cybergrind mode. I'm pretty sure this is an issue with Unity's UI system, because this same crash happens on other games such as Among Us and always happens when a specific menu shows up.
The game crashes every time I die in Cybergrind mode on my Ubuntu gaming rig, but does not crash on my Arch laptop. I'm not sure what exactly the prerequisites are for this crash to happen. Nothing I did seemed to fix the issue.
Wallpaper Engine relies on Windows dependencies, including Windows Aero graphics features. It will not integrate into a Linux desktop.
There are alternatives out there, and KDE has shader wallpapers built in. Use those instead.
