True_Fakts
Published
Rock Solid 60FPS at all times
Played on Fedora 35 KDE using Wayland. No tinkering, rock solid 60FPS at all times including cities.
Using a Logitech G27 with force feedback provided via https://github.com/berarma/new-lg4ff. Just unzipped the download to /usr/src/new-lg4ff and rebooted. If doing this on Ubuntu based distros, follow the instructions including the DKMS install
Same as Windows. Works perfectly
No issues at all after the first launch. When I launched it the first time, the 2K Launcher said I had no games and advised me to relaunch the game from Steam. I did what it said, closed the launcher and clicked Play in Steam. After that I never had any issues.
I don't think that's a proton thing, probably a weird 2K thing which I would imagine would be the same as on Windows. Never had any issues outside of that. Just clicked Play and was in game right after
gamemoderun %command% -vulkan -high -nojoy -novid -maxMem=7000k
Without launch options, the game is really stuttery and generally difficult to play
There’s a pretty bad VRAM memory leak in the native version of the game, which means performance will degrade rapidly after joining a game. It seems like the game isn’t detecting the amount of usable memory on the graphics card, causing the framerate to drop to unplayable numbers (like 30fps) after about 2 minutes of gameplay.
This issue is fixable via launch options, specifically by specifying the amount of memory to use. After trying every launch option on ProtonDB, I found that the -maxMem launch option was the only one that fixed CS2 and made it playable.
My Setup
I have an 8GB graphics card, so I set -maxMem to 7000MB. Setting it to the full 8GB still resulted in stuttering, but capping it at this slightly lower value made the game run perfectly smooth. I played for about 2–3 hours and enjoyed competitive games with friends.
Recommended Launch Options
Here are the launch options I used:
gamemoderun %command% -vulkan -high -nojoy -novid -maxMem=7000k
In Game Settings That Worked Best For Me
Windowed fullscreen (default)
Vsync disabled (default)
Set the FPS cap to something that your PC can maintain (120fps for me on Medium settings @ 2560x1440)
I haven’t played CS in Windows for many years, back when it was CSGO so I don’t know what FPS I’d get in Windows. But a rock solid 120fps is perfectly playable as far as I'm concerned. I had no issue with the taskbar displaying on top of the game. But that might be because a KDE issue that's specific to the desktop version that Kubuntu 24.10 uses. If that happens to you, another user mentioned right clicking on the icon on the taskbar and setting "Keep Above Others". But I didn't have this issue, even Freesync worked for me in windowed mode
On first boot, the application does not launch in full screen mode properly. The Gnome top bar pushes the application down a handful of pixels, offsetting the window down. As a result, the cut-scene at the beginning of the game cannot be exited since the "Exit to Menu" button is off the screen.
NOTE: I played the native version, not the proton version
There is a bug affecting how Full Screen launches on startup. If you're using the default Gnome desktop with the top bar present, the application window is offset by a couple of pixels. To launch the game and fix this permanently is a 7 step process:
- Install the game, and set the following in the game's launch options:
-w 800 -h 600
- The game will launch in Windowed mode at 800x600
- During the startup sequence, allow the cut-scene to complete.
- Click the "Do not show again" checkbox and exit to the main menu
- Go to the graphics options and enable Fullscreen mode then save and exit
- Exit the game
- Remove the "-w 800 -h 600" flag from the launch options
The game should launch and play properly in full-screen mode
-nosplash -skipintro -noLogs -nolauncher
2 issues:
- The game's launcher runs really slowly and will lock up. You definitely want to bypass it and use the in-game server browser.
- During initial loading, the game will crash unless you set a kernel flag in terminal. This has to be done on every boot. Launch terminal and run this command:
sudo sysctl -w vm.max_map_count=1048576
No issues connecting to official servers, even with battleye
At minimum you're going to need to set the launch options, and that kernel flag I pointed out to get the game to run. You'll be able to connect to all official and some community servers and play as if you were on Windows. Unfortunately this kernel flag is reset every time the machine reboots, and thus DayZ won't run. That destroys the Wife Acceptance Factor, so heed my advice if you're setting this up on someone's computer. I wrote a quick 1 liner shell script which runs on boot via cron. Totally invisible to the end user, he/she/they simply reboots their machine to their hearts content and DayZ just "works"
- Step 1: Open a text editor, then copy+paste this into a text file.
#!/bin/bash
sysctl -w vm.max_map_count=1048576
- Step 2: Save the script file in your home directory (honestly it doesn't matter for root cronjobs but whatever) and call it:
set_vm_max_map_count.sh
- Step 3: Make it executable by launching Terminal and running:
(side note: you might have to put
sudoin front of this command depending on your distro)
chmod +x set_vm_max_map_count.sh
- Step 4: set up a cron job to run this script at system boot. To do this, open the ROOT crontab configuration using the following command, followed up by pressing Enter:
sudo crontab -e - Step 5: Add a line to the crontab file to run the script at system boot. To run it as root, add the following line:
@reboot /home/<your_username>/set_vm_max_map_count.sh - Step 6: Save (ctrl+s) and exit (ctrl+x)
- Step 7: Test that this works by rebooting the computer and launching DayZ. It should take you right to the menu
NOTE: I have not had an opportunity to explore 3rd party launchers/mods for connecting to community servers. Apparently one does exist, and this is the documentation for it:
https://aclist.github.io/dzgui/dzgui.html The information I have about the launch options and kernel flag came from here
VSYNC toggle in the launch does not do anything. This could be a symptom of my hardware, as my machine is an Nvidia Optimus laptop, with the game running in a PRIME offload configuration. As a result, >120FPS is the norm.
HDR and Bloom must be disabled in the launcher, else the game will crash on launch
Like all Bethesda titles, alt-tabbing will cause the game to crash. This is the same behavior on Windows so not a Proton problem. But be warned, as moving to a different desktop does not work as a workaround
Utilizing the Intel GPU (as opposed to discrete Nvidia) will cause the title to crash to desktop immediately upon loading a game save. This could be a symptom of Ubuntu's graphics libraries as opposed to a game-bug.
Play the first mission in Windows. Then copy the game save to Linux and you'll never need Windows again
Must Copy a Game Save from Windows due to Game Breaking Bug
Only DirectX9 works. Setting DirectX10 will cause the game to crash on launch. This is fixable by manually reverting to Platform="d3d9"in the GamerProfile.xml
Game breaking bug after the hotel fight causes your player to freeze in place, which prevents you from actually creating your first game save. Thus you can't actually start the game
As I mentioned earlier, there is a game breaking bug which prevents you from progressing passed the first hotel fight. It's incredibly annoying and VeNoM's report from 3 years ago helped me passed this part. To play this game, you need to do a couple things:
- Boot into Windows
- Disable Windows Protected Folder Access in the Windows Defender settings (Super Important, otherwise you'll get an error saying the game can't save.)
- Play through the intro, and the hotel fight
- Get to the first save point, where you use the blue save icon on the wall and create a save. To play it safe, I did the first actual mission in Windows too
- Go to C:\Users\your username\Documents\My Games\Far Cry 2\
- Copy the folder, specifically the \Saved Games\ folder to somewhere safe
- Boot into Linux, and install the game. In my case I installed it on my root () disk in my home directoy
- Launch the game once, just to get the folders created. Setup you graphical settings. DO NOT SET DIRECTX10. Everything else should be fine though
- Copy the \Saved Games\ folder from Windows to "/home/$USER/.steam/steam/steamapps/compatdata/19900/pfx/drive_c/users/steamuser/Documents/My Games"
If you do the copy using terminal, then the $USER variable will work as-is. If not, change the $USER to be your username.
After all that, you'll never have issues with this game again. Thanks for the help VeNoM!
PROTON_NO_D3D11=1 %command% -dx10
Game breaking bug after the hotel fight causes your player to freeze in place, which prevents you from actually creating your first game save. Thus you can't actually start the game
To play this game on Linux, you need a gamesave from Windows
To play this game on Linux, you need a gamesave from Windows. This is because of a game-breaking bug
- Boot into Windows
- IMPORTANT: Disable Windows Protected Folder Access in the Windows Defender settings (otherwise you'll get an error saying the game can't save.)
- Play through the intro, and the hotel fight
- Get to the first save point, where you use the blue save icon on the wall and create a save. To play it safe, I did the first actual mission in Windows too
- Go to
C:\Users\your username\Documents\My Games\Far Cry 2\
- NOTE: Change "your username" to what it actually is on your computer
- Copy the folder, specifically the
\Saved Games\folder to somewhere safe - Boot into Linux, and install the game. In my case I installed it on my root () disk in my home directoy
- Launch the game once, just to get the folders created
- Copy the
\Saved Games\folder from Windows to/home/$USER/.steam/steam/steamapps/compatdata/19900/pfx/drive_c/users/steamuser/Documents/My Games
If you do the copy using terminal, then the $USER variable will work as-is. If not, change the $USER to your username.
After all that, you'll never have issues with this game again. Thanks for the help VeNoM!
Additional Information About DirectX10
Use the launch option I provided to play this game with DirectX10, if you change the setting in the in-game options without this the game will crash on launch. However it's optional, DirectX9 will run fine if you want to go that route.
Ubisoft Connect Launcher will not connect to Online Services. Game will not launch
I tried a variety of proton versions, could not get the launcher to connect to the online services. Thus you can't launch the game. I tried experiemental, proton 8 and finally proton 7 which prevents the launcher from even rendering. At no point will you be able to actually start gaming.
Avoid this title
Played the normal title, and DLCs in Steam Big Picture mode with a wired Logitech F310. No issues. Plug and play, without the need for launch options.
Needed to use a keyboard and mouse to sign into the R* launch during the initial setup
Indistinguishable from Windows
Installed the game, and played it as if I was on Windows. Story and GTA Online worked right out of the box. Set all the graphics options to Ultra and enjoyed a silky smooth experience playing with my friends. My controller is a Logitech F310
Indistinguishable from Windows
Just click play, hop onto GTA Online and have fun with friends who are also playing on Windows and Linux desktops. Just works
Wake up, it's Christmas 2007 again. Multiplayer Halo 3 on Linux
The game will hang if you're afk in the menu for a while. I found I could play many multiplayer games one after another without issue. Then go to the main menu to step away from my computer for snacks and come back to the game being frozen. My recommendation is just close the game and return to the desktop if you're going AFK.
Multiplayer works! Halo 3 on Linux, it feels like Christmas 2007 again.
The only thing is, the Easy Anti-Cheat selection when you launch the game is reversed as of April 15th 2023. To play multiplayer, select the DISABLED option to ENABLE it. It's a minor bug with the launch options
EA Launch Update Broke the Game
This title used to work fine until an EA Launcher update in June of 2023 broke the game. Now it won't launch at all, regardless of proton version or launch option.
Assuming this gets fixed at some point, I'd recommend on passing on this title anyway. Unless it's got some real nostalgia for you there are much better games on steam for the same price EA is asking for this game. Not to mention it's hit or miss that a random update will break your existing installation leaving you with no recourse. If you already on this game, then fine. If you're reading protondb to see if you should get it, I recommend a hard pass
Indistinguishable from WIndows. Need to Alt+Tab when sending invites to close the Steam overlay
Only when using the steam overlay to send a multiplayer invite, I couldn't close the overlay with shift+tab at first. I had to alt+tab out of the game, then come back in to close it. Really weird. Literally the only issue.
Doesn't happen when launching the game in Big Picture mode so playing on the couch with a controller is perfect. This might be a Steam thing rather than a SnowRunner thing?
Recent Regression forces Ubuntu-based Distro
Crash on login if Ubuntu isn't used
TL;DR Only runs on Ubuntu-based distros as of late. I've tested Fedora 36 KDE, Manjaro KDE (kernels 5.15 and 5.19,) Linux Mint and Kubuntu 22.04 in the past two weeks. I can only run it on Kubuntu 22.04 and Linux Mint. Newer graphics stacks will crash the game on launch/during login with the following Unreal Engine error:
- VK_ERROR_DEVICE_LOST
Background: I don't think this is actually a Splitgate issue, rather it's a Mesa GPU driver issue caused by a recent regression. However I could be wrong, just based on my experience because I've played the Spligate without an issue for about 8 months on Fedora until I decided to try another distro. Two weeks ago Spligate worked like a charm on my Fedora 36 KDE install, which was only about a week out of date. I decided to try out Manjaro and did a fresh install of Splitgate but noticed that the game crashes during login. As a result I went back to F36 and noted the exact same issue as Manjaro! The only different between the F36 install from that morning and that afternoon was the afternoon install had all of the updates applied. The error in the Splitgate log is a generic Unreal Engine message which states that the Vulkan display device is no longer detected.
Long story long, I switched to Kubuntu 22.04 (which has older Mesa) and the game runs without issue. All of my testing with Fedora, Manjaro and Kubuntu were with fresh installs off Steam in the past 2 weeks and Splitgate ONLY runs on Kubuntu + Linux Mint
I did a before/after test in Kernel 5.15 and 5.19 on Manjaro and the symptom was the same. Thus, through a process of elimination I'm blaming Mesa. Btw I'm using a 6600XT with the open source drivers. I'd highly recommend using the Plasma Desktop and Wayland if you're on AMD to reduce stuttering
The game will crash on first-time launch on relatively recent versions of Mesa. The fix requires a .ini edit for the game to startup properly. Here's what I did:
- Launch the game normally and have the system crash, requiring a hard reboot
- Reboot the system and login
- Navigate to: /home/.config/Epic/PortalWars/Saved/Config/LinuxNoEditor
- Open GameUserSettings.ini in a text editor
- Change bHasRunAutoCalibration=False to bHasRunAutoCalibration=True
- Save and exit
The game will launch normally after that. This only seems to be a problem on AMD/Intel with new Mesa drivers. My Nvidia systems seemed fine
Indistinguishable from Windows in terms of user experience
When installing into your ~/.steam directory, the Oblivion Launcher greys out almost all options except for Support and Exit. A registry key edit will correct this.
Credit to this guide: https://www.reddit.com/r/linux_gaming/comments/pijhgt/fix_oblivion_launcher_has_all_options/
When installing outside of your home directory (such as on another SSD in your system) there is no need to tweak anything. When installed on a drive mounted in /mnt/ the process was identical to Windows.
When installing within your home directory (such as your ~/.steam folder) you need to perform a registry edit to have the Oblivion Launcher detect the game's installaiton location. A guide was originally posted here: https://www.reddit.com/r/linux_gaming/comments/pijhgt/fix_oblivion_launcher_has_all_options/
Can confirm this worked for me:
Step 1: This will open a regedit for your Oblivion Wine instance
- Open Terminal and run this
- WINEPREFIX=/home/$USER/.steam/steam/steamapps/compatdata/22330/pfx/ wine regedit
Step 2: Add Registry Key and Installation Location String Value
- Go to HKEY_LOCAL_MACHINE/Software/Wow64Node
- Create a new key (folder) by right-clicking on Wow64Node, name it Bethesda Softworks
- In Bethesda Softworks key, create another key and name it Oblivion
- Then, create a String value in your Oblivion key, name it Installed Path
- Finally, righy-click on the Installed Path entry, and put a path to the game's files with a Z: before it and don't forget to format the slashes as the Value data. (i.e. Z:\home<your username>.local\share\Steam\steamapps\common\Oblivion)
- Close regedit and terminal
Step 3: Launch the game
- Launch the game! If you did everything correctly, Oblivion will launch as normal, with all of the options available ** I did not have verify game's files integrity via Steam, but if you're still having issues try it
A controller is strongly recommended for this title, even on Windows. Despite the occasional audio crackle, the game works well
Dialogue audio is missing entirely if no launch options are present. NPC mouths move, but nothing is heard. The following launch option corrects this, and turns the game into a playable experience: (copy and paste with quotes)
WINEDLLOVERRIDES=”xaudio2_7=n,b”
NPC audio was corrected after this. However an intermittent audio crackle could be heard throughout the gameplay. This would appear, and correct itself without warning. Typically changing environment within the game (ie. entering a house) would present a loading screen which would fix the issue
I have the anniversary edition, which utilizes the Creation Club to add additional assets to the game. This worked flawlessly upon initial launch.
This could be an artifact of my desktop environment. But when launching this game via Steam Big Picture mode, the Steam interface jumps in front of Skyrim. To correct this, click "play" again in Steam. This will not relaunch Skyrim, but will bring it to the front/active window. If controller input doesn't work right away, tap the home/playstation/menu button to bring up the Steam overlay temporarily which sorts this out immediately
DXVK_FRAME_RATE=60 %command%
If you're gaming on X.Org, the native version of the game runs perfectly. However on Wayland the mouse input is limited to the bounds of the display which makes it impossible to spin the camera in a complete circle. Switching to the Windows version and playing through Proton has no such limitation, and otherwise runs at native speed. I did limit the framerate to 60 FPS because my monitor has a 165Hz refresh rate which seems excessive and runs my graphics card hot. Completely optional, but the launch option I used is listed above
