C96Alia
Published
Worked flawlessly- some Steam reviews have reported bugs, but I haven't seemed to find any yet.
Settings/controls configuration menu may take multiple tries launching to open.
Game runs out of the box with no issues, however the multiplayer servers appear to be down and singleplayer is non-locatable.
The (Original) versions that run on DOSBOX seem to have stuttering and freezing issues. Not the fault of proton.
Otherwise, version that runs on proton work perfectly.
Had to use steamtinkerlaunch to enable the game to start with Wine (wine-8.9-amd64 to be specific, although no changes so I suspect anything new-ish would work.), and then switched back to Proton Experimental.
Isolated instance of game crash.
The game was pretty random that the game worked- I used the trick where you copy the anticheat into the binary folder as well on Steam. Game did not launch without Wine (that is without crashing after trying to load EAC), and after my trick with steamtinkerlaunch EAC seemingly complained until it randomly decided all was well. Overall got it working by luck.
Overall it's easier to get this working on the Heroic laucher using that method (much less headache) but I had issues with friend systems on there.
Created a file named "dxvk.conf" where the game's shipping executable is located with the content "dxgi.customVendorId = 1002". This was to get around a driver issue with the Mesa drivers for Intel, with a not-yet-implemented part of Vulkan the game tried to use.
Severe stuttering when using X11 on KDE Plasma. Did not occur on any other window manager or mode.
Game crashed frequently when using Wayland on KDE Plasma. Using GNOME Wayland fixed this.
Updated report from my previous one; that one was fairly inaccurate.
Game is enjoyable without tinkering for most graphics cards; the DXVK workaround must be done with Intel cards (iGPU and dedicated.)
Would be enjoyable on newer systems. I ran DBD on this weak of a system as an experiment, and play it on a newer system.
Created a file named "dxvk.conf" where the game's shipping executable is located with the content "dxgi.customVendorId = 1002". Otherwise, the game will not launch on Intel GPUs/iGPUs due to a Mesa driver issue.
Did not load into custom bot matches. Would sit near the end unresponsive until crashed or force quit. (Granted, DBD is not typically run on this weak of hardware)
Severe graphical issues that shouldn't be occuring.
Intro video plays fine, but anything beyond has severe graphical glitches. Everything is red tinted and flashes colors, then the game crashes with vulkan errors shortly after. Graphical issues are slightly less severe with lower graphics settings.
This isn't a hardware issue; other games run fine on this Linux install, and Enlisted ran fine when this system had Windows.
Some bugs, excessive RAM usage/a couple lock ups. Just the normal Paradox issues.
Animation heavy areas of the novel can stutter slightly, but unless watching for it its not always noticable. Still more than fully playable, as this is a visual novel.
Attempted multiple proton versions. Experimental, 7.0.6, 6.3.8, 5.13-6, and Hotfix. All times game failed to get past the launching stage.
Audio slightly crackles and occurs out of sync when running on Proton 7.0-6. Still occurs on GE-Proton7-49, but with significant reductions in noticability and frequency. (No such issues occur when running on Windows 11.)
Tinkering not required, but assists with minor audio issues. (It should also be noted that the DVD version of the game was used, and installed through Wine.)
Game runs awesome, but only under Proton (tested 7.0.6/Experimental). Native version has major issues.
Ran the game under Proton 7.0.6 and Experimental, as both work much better than the native Linux port.
All issues listed here only occured on the native Linux version of the game.
Severe texture issues occured on the Icebreaker map, the first minute after loading in being just random colors. This cleared up by itself, although the bad textures would re-occur randomly. (Did not occur using Proton. Only native version.)
Other maps also had insignificant artifact/texture issues, as well as insignificant texture refreshes upon using the Esc menu. (Did not occur using proton. Only native version.)
All issues listed here only occured on the native Linux version of the game.
The game ran much choppier and slower than expected, to the point of lowering the settings to 1024x768 and below/Lowest settings to get smooth performance.
(Did not occur using Proton, only native version. Running under Proton the game performed much better, with being able to run at my native 1600x900 as well as medium graphics without issue. Did not test high/anti-aliasing.)
If you're experiencing lag issues, try changing the server region to what is closest to you. The game auto sets the server region to sub-optimal settings.
I personally had a small chance to crash when using Proton Experimental; use a stable or GE version of Proton.
Tinkering not required; I personally just wanted to use a GE Proton.
Did not launch on this specific laptop without GE Proton (on default Experimental just crashed)
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.
Some cape/jacket rendering issues when using GE-Proton7-55.
Matches are prone to freezing and crashing when using Proton 8-0.2.
Stick with Proton Experimental; GE-Proton7-55 often refused to launch the game and had rendering issues, and Proton 8-0.2 has stability issues.
In other notes, AMD FSR 2.1 seems to be working fine for me (have not tried the FSR 1.0 option.)
