


Stuck
installed, started, but stuck on "LOGGING IN"

Didn't run at all, I got to the loading screen but not the main menu. Tried with and without Proton, aswell as 9.4 and experimental.
Didn't even load, couldn't get to the main menu with&without proton.
Didn't work

Could basically never get into a match. 5% success rate to not get booted back to the lobby screen.

gamemoderun %command%
I love native games! Only thing was I couldn't see a list of resolutions in the video settings. But it was defaulted at 1440p so I didn't mind.

Well, because not alot of people have 2 monitors, they alt-tab. Thats what i did. 3 times of 9 it crashes my gpu (amd) and eventually my pc
If you use AMD gpu, Alt-Tabing somehow crashes process amdgpu and eventualy, it crashes the whole pc. It doesnt happen everytime, but very often
Sometimes it lags for a couple of seconds

Le jeu reste en écran noir via le mode jeu, mais fonctionne en passant par le mode bureau.

mangohud %command%
Being near your open portals could be a bit laggy.

Text in menus might be a tad small for some people.
Game can normally maintain 60 fps during gameplay. However, portal quality needs to be dropped to medium or lower to avoid significant framedrops. Performance also sometimes tanks in menus, down to ~10 fps and stays there. Restarting the game fixes this.
Game installs, then blank screen on launch. After a few minute wait Unreal engine will crash every time.
gamemoderun %command%

Native + BattleEye + EAC
Stay as Native. Install Proton BattleEye Runtime and Proton EasyAntiCheat Runtime.

overall great experience, some issues with multi monitor setup
sometimes my mouse would just go to my 2nd screen. opening the escape menu and closing it again fixes it but it can be pretty annoying when it happens like 5 times in one match
Works great. There were issues in the past, but developers seem to have updated whatever caused their historical issues.

When the anti cheat starts to install had to disable firewall to get it to work after which i can activate it and leave it
sometimes the mouse would click over to other monitor even though im fullscreen

Crash on launch with Steam Overlay enabled
Works flawlessly with Steam Overlay disabled.
Resolution box is empty in settings. Defaults to full display resolution, so not a problem for me.

The game doesn't launch natively anymore without forcing the use of Proton, updating the game, attempting to launch it with Proton compatibility enabled (it doesn't launch - anticheat/missing DLL error). When turning off forced Proton compatibility in the game's properties, and updating the game again, it works fine natively. Very strange issue. Changing this value in the .ini file for the game doesn't seem to do anything > https://forums.gentoo.org/viewtopic-t-1140849-start-0.html
Game window opened, but continuously threw "not responding" errors

worked as expected
runs natively without proton and works fine

Did not have any issues now, but as previous reports show, it was broken for some time

Resolution option in settings is broken; need to edit that using GameUserSettings.ini
Unreal Engine did not like my iGPU mostly for being Intel; I had to patch this by going to the Splitgate>PortalWars>Binaries>Linux area of the gamefiles and drop in a text file named dvxk.conf with the contents "dvxk_custom_vendor_id=1002." Game didn't launch otherwise.
This issue is not Splitgate exclusive; not going to fault the game for it, it's an issue with the engine.

Works perfectly out of the box
Forced SteamPlay to use the "Steam Linux Runtime"
Graphics: Everything set to epic
FPS: 140 - 190, average about 160, no fps drops.
Requires SteamOS v3.5 to play this game w/out issues!
Works without any issues.
I finnaly found a multiplayer game where my system didnt explode when playing.
this is finnaly game that didnt crash or blow up my system, typpically games like apex wan't to destroy my pc, and me by try-hards. But in this game matchmaking system is not broken and somehow faster even with thosand times lower online than apex or cs:go.
Launch the game once and let it crash
Edit the file at ~/.config/Epic/PortalWars/Saved/Config/LinuxNoEditor/GameUserSettings.ini
change bHasRunAutoCalibration=False to bHasRunAutoCalibration=True
When alt+tabbing out of the game, the resolution will occasionally be set weirdly when you re-enter the game. alt+tabbing out again fixes it
Occasionally had some jitter, and there is a tiny bit of lag at the start of a match
Overall, this is a very stable game on Linux. You may have a few graphics issues, and it does require a bit of tinkering to get to launch correctly, but it takes about five minutes to get set up and you're ready to play.
A playable game
Portals are blurry and it reduces the games fps when you take a look at them.
Runs natively without issue after editing 1 line in the config. Does not launch with Proton.
edit ~/.config/Epic/PortalWars/Saved/Config/LinuxNoEditor/GameUserSettings.ini
and change bHasRunAutoCalibration=False
to bHasRunAutoCalibration=True
when playing in windowed mode or with multiple monitors, the cursor can escape out of the window. a bit annoying, but it is simple enough to make it a non-issue by playing in fullscreen and turning off your other monitors if need be.
Game launches then shows an Unreal Engine error, causing the Steam Deck to crash and forcing a hard reboot of the system.
Currently borked on Deck, no patches or fixes have been made to address this and this issue has persisted for months.
Fast pace FPS with Portal elements. It's crazy.
Surprisingly everything work out of the box.

uhhhhhhh i dont know how to describe it
after trying to start the game,my screen looks like the deep fried laughing emoji meme
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
Works well with tinkering, without tinkering launching soft bricked my computer requiring a hard restart.
gamemoderun %command%
Crashed during initial loading screen
Going to "~/.config/Epic/PortalWars/Saved/Config/LinuxNoEditor" and editing "GameUserSettings.ini", changing the "bHasRunAutoCalibration" to "True" resolved an issue causing crash on launch.
No issues.
No multiplayer issues.
The game runs great there are no problems with it at all. I had fun and recorded some nice clips
gamemoderun obs-gamecapture %command%
Unique and fun game. Combines Halo and Portal into one good FPS.
Some stuttering but it's probably the shader cache.
Recent update (likely Steam Runtime or maybe the glibc problem) has borked the game on Steam Deck and desktop Linux.
Attempted running with proton and the native Linux version. No dice with either.
Emailed their support, posted on Discord. No responses. Splitgate isn't actively under development, so there's no indication of if or when this may be fixed.
# Games runs smoothly. ## Mesa 22.3.2 | distro: EndeavourOS-gome ### I had problem in Manjaro, PopOS, Problem was in mesa drivers 22.0.X .
Games runs smoothly.
Mesa 22.3.2 | distro: EndeavourOS-gome
Install Mesa 22.3.2 or above for fixing UE4 error.
Game runs smoothly in Mesa 22.3.2 - EndeavourOS
Any issue related UE4 then Install Mesa 22.3.x or above
gamemoderun gamescope -h 720 -H 1080 -U -f %command%
bHasRunAutoCalibration=True
The game with the default config launches and continuesly crashes on first loading screen, also causing problem to the desktop environment(gnome) freezing it. But i figure out how to fix it thanks to https://forums.gentoo.org/viewtopic-t-1140849-start-0.html
goto: ~/.config/Epic/PortalWars/Saved/Config/LinuxNoEditor and open GameUserSettings.ini, The fix was to set:
bHasRunAutoCalibration=False to bHasRunAutoCalibration=True
And this fixed it, the game started normally as it should.