Simbax
Published
Playable but with some minor performance issues
DS4 controller is not detected when connected wirelessly, even when the game is started from Big Picture mode. Wired works fine at least in the menu, the game even shows PS4 button prompts.
Non-disruptive frequent stuttering and frame drops lasting no longer than a few seconds, especially at the beginning of levels and after moving to/looking at new locations.
6.21-GE-2 GloriousEggroll
There was no audio in cutscenes and intro videos on Proton 6.3.8. Proton GE works perfectly out of the box without any launch options.
gamemoderun %command% -nostartupmovies
Edited ini file to reduce mouse sensitivity (there's no slider in the settings). Also, disabled D3D11 and enabled D3D10, otherwise fast travel to batcave would result in infinite loading screen.
Huge FPS drops (from 300 to 50) during in-game benchmark in some locations. Fortunately, disabling PhysX helps with this. Still experienced some slight stuttering, but only for a moment or two in new locations, or during saving.
Annoying random crashes, sometimes after an hour, sometimes after 15 minutes of playing. Disabling D3D11 and PhysX doesn't help. Lost experience points after a predator mission once - the goons were gone after restart but level up and challenge unlock too. At least the game saves frequently, so not much progress is lost, but it might be a good idea to make frequent save backups in case they become corrupted.
With the amount of restarts required to play this game, the -nostartupmovies launch parameter basically becomes a necessity.
I'm not sure if it's Proton, maybe the game itself is just a horrible PC port.
gamemoderun %command% -nostartupmovies
Edited ini file to reduce mouse sensitivity (there's no slider in the settings). Also, disabled D3D11 and enabled D3D10, otherwise fast travel to batcave would result in infinite loading screen.
Remote batarang is uncontrollable with the mouse when using Wayland. Works fine with the controller and when using X.org.
The game doesn't save challenge progress after predator encounter but saves the fact that it ended. But it is most probably the game's issue, not Proton. Save backups before each predator encounter recommended though if you care about the Worst Nightmare challenges.
Huge FPS drops (from 300 to 50) during in-game benchmark in some locations. Fortunately, disabling PhysX helps with this. Still experienced some slight stuttering, but only for a moment or two in new locations, or during saving.
After switching to Wayland crashes stopped happening as frequently as in my previous report. Or maybe it was a system update or planetary alignment, I don't know. Now it crashes only once every few hours.
The game does have a lot of bugs. Not really Proton's fault.
Works surprisingly great, which cannot be said about CoDs released later
DXVK_ASYNC=1 gamemoderun %command%
In the level with underground tunnels, inside the tunnels everything looked weird but it's a short enough section.
The mouse sensitivity is tied to FPS. Combine this with low and unstable FPS, the game is barely playable on higher difficulties and not very enjoyable.
Ridiculously low and unstable FPS.
All the issues combined make this game not a particularly great experience even though it is technically beatable at least on the lowest difficulty. I gave up halfway anyway due to being too annoyed, and decided to beat the game on Windows.
Changed my mouse's polling rate to 125 Hz by using Piper to fix stuttering aiming.
Aiming is stuttering if mouse's polling rate is >125 Hz, but as far as I know this issue happens also on Windows.
Stuck at connecting to IWNet when trying to play Spec Ops. Not sure if Proton issue.
Aiming is stuttering if mouse's polling rate is >125 Hz
FPS locked to ~40 FPS due to DRM
The game has reduced FPS because of DRM. With crack the campaign works fine and is beatable, but Steam Achivements obviously do not work, probably multiplayer too.
DXVK_ASYNC=1 gamemoderun %command%
Crashes semi-consistently on some missions: Shock and Awe at the beginning shortly after leaving the helicopter, Mile High Club pretty much always before getting up the stairs.
Works mostly fine except for crashes in some missions. As stupid as it sounds, I managed to workaround the Shock and Awe crash by tinkering randomly and lowering the graphics settings temporarily, choosing different paths, going slower etc. to somehow get pass the place which consistently crashes. The rest of the game worked fine until the bonus mission, Mile High Club, which just kept crashing soon after the initial cutscene. It was somehow getting worse and worse after every restart and I did not manage to fix it, gave up and switched to Windows to get the achievement. The game is very playable and enjoyable otherwise.
WINEDLLOVERRIDES="winmm,version=n,b" PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 DXVK_ASYNC=1 VKD3D_FEATURE_LEVEL=12_2 %command%
Used protontricks to make some mods working, although WINEDLLOVERRIDES is probably enough now.
I was switching between a lot of Proton versions at some point when I was debugging why some mods stopped working after an update. In the process I seem to have currupted most of my saves, fortunately the CDPR (not Steam) cloud saved the most recent one. So, I advice backing up saves before switching to a different Proton and/or playing with mods.
Significant FPS drop after some time playing, usually after opening the map one too many times. Seems to be related to raytracing and/or DLSS, and the game is still playable just less smooth. Easily fixed by restarting the game.
Works great with some occasional performance hiccups, but the IMU terminal doesn't work out of the box
Occasional stutters at the beginning, seem related to loading new music/models/shaders, it's hard to tell. They stop happening after playing for a while.
I also noticed that the FPS counter significantly decreases in the pause menu, although it's not noticeable if your FPS is already much above your monitor's refresh rate.
The Interplanetary Miners Union (IMU) terminal is not interactive even if Discord app is installed and open in the background. It is still possible to use it with help of the wine-discord-ipc-bridge program though.
VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command%
WINEDLLOVERRIDES='dinput8.dll=n,b' gamemoderun %command%
Installed high refresh mod https://gamebanana.com/mods/380955 to get rid of occassional stuttering.
Occassional almost unnoticeable stuttering making me missing notes sometimes. It seems to be because of the game's built-in FPS limiter and vsync. Mostly fixable with the high refresh rate mod.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%
Modified ~/.local/share/Steam/steamapps/compatdata/990080/pfx/drive_c/users/steamuser/AppData/Local/Hogwarts Legacy/Saved/Config/WindowsNoEditor/Engine.ini
[SystemSettings]
r.bForceCPUAccessToGPUSkinVerts=True
r.GTSyncType=1
r.OneFrameThreadLag=1
r.FinishCurrentFrame=0
r.TextureStreaming=1
r.Streaming.PoolSize=3072
r.Streaming.LimitPoolSizeToVRAM=1
[ConsoleVariables]
AllowAsyncRenderThreadUpdates=1
AllowAsyncRenderThreadUpdatesDuringGamethreadUpdates=1
AllowAsyncRenderThreadUpdatesEditor=1
The game doesn't seem to like Alt-Tabbing, it basically almost always crashed shortly after. Otherwise I could play it for hours without issue.
The game worked fine for me up until the first cutscene in Hogwarts, where suddenly my FPS dropped below 30 and the game just kept crashing after being assigned to a house. Changes to the ini found on the Internet and switching to new Proton-GE seem to have fixed the performance issues. I preventively set /proc/sys/vm/max_map_count to 1048576, don't actually know if did anything but have not experienced crash after fast travel so I guess it works.
I could not get raytracing to work but didn't particularly care.
7.0rc6-GE-1 GloriousEggroll
Visible texture/shadow flickering (z-fighting?) in some places. Not sure if Proton is the cause of those though.
VSync option in-game introduces noticeable input latency. GSync/FreeSync monitor recommended in order to avoid using the in-game VSync.
On Proton 6.3.8 plants didn't render correctly, that's why I switched to Proton GE for this game.
The game starts but is unplayable
In the latest version can’t get past the initial screen with the “START” button as it doesn’t react to clicks.
The 2.0.5.3 version allows to load a scenario but it’s unplayable because it doesn’t react to mouse input i.e. the camera can’t be moved and it’s impossible to shoot.
A blind guess that the issues could be related to the EQU8 anti-cheat.
WINEDLLOVERRIDES="loader=n,b;dinput8=n,b" gamemoderun mangohud %command%
The audio sometimes crackles in Astera due to performance issues.
Enabling DirectX 12 API in the settings ruins the performance. The game runs at half the FPS (50-60) compared to Windows (110-120) in Astera (oddly enough, both GPU/CPU usage seem to be capped at about 70% there). In other areas the performance is closer to Windows, but still not as good. DirectX 11 works much closer to Windows (still worse than DX12 Windows though). Switching to Experimental, -9, or -9-GE makes no difference. With Proton-7 the game is not starting at all, and with Proton-8 the game doesn't allow DirectX 12 API option at all.
The game once completely froze my system forcing full PC reset in Astera. This happened only once and I think it was probably due to abnormally high CPU usage because of Steam patching another game in the background.
Something is very wrong with Astera with DX12 enabled, which is a shame, because it's the main hub so the player spends a lot of time there.
Mods work with proper WINEDLLOVERRIDES.
Had to disable Steam Input for the controller to work.
Gleamium could not be bought because the Steam Overlay didn't work. The workaround is to use gamescope (Steam Deck) or Windows to buy it. Note: I last played in Oct 2022, so it might work worse/better now.
Works almost perfectly if not for the alt-tabbing issues
The game just shows black screen after alt-tabbing out of it, needs to be restarted. Also had trouble capturing footage from the game which also showed black screen. I only managed to do that with OBS game capture plugin, and starting recording before starting the game. Note: I'm using Gnome on Wayland, don't know if it's an issue on X.org.
Sound doesn't work in the native version and disallows using desktop cursor somehow so alt-tabbing out of the game is useless. Proton version works perfectly fine. Only played co-op.
Works fine except for occassional crashes when playing on-line, so don't host games on Linux
WINEDLLOVERRIDES="wsock32=n,b" PROTON_DXVK_ASYNC=1 PROTON_USE_DXVK=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -skip_intro
For some reason Overkill decided it would be a good idea to separate Linux native saves and Windows saves. Don't be surprised when you don't have your stuff when changing from Proton to native and vice versa. Ludicrous technical decision but it is what it is, there are workarounds to be found on the Internet.
The game works perfectly in offline mode. On-line, though, it will crash on the briefing screen after a few heists, sooner or later, regardless if I'm a client or the host. The crash is weird as it freezes the whole game and does not leave any crash log. Despite trying everything I could find on the Internet, I did not manage to fix these crashes. This is not a problem when I'm a client because I can just restart the game and join again, but this makes it very bad for hosting as it would destroy the whole lobby. So for hosting games I recommend using Windows.
After a few heists it crashes/freezes on the briefing screen while loading. Sometimes infinite loading after finishing a heist, forcing to close the game with Alt+F4.
Mods work fine, highly recommend them as they can also fix some bugs and crashes.
A note about the native version: a tried it for a moment in hope it would fix the crashing. No idea if it did because I quickly switched back to Proton version. Not all mods work with the native version and it has a lot of graphical glitches. Also, it seems it is being abandonded and might not receive new content according to the recent news https://www.paydaythegame.com/news/payday2/2023/03/payday-2-the-lawless-tailor-pack-crude-awakening-bundle/ I recommend avoiding the native Linux version.
Had to enable WineD3D or the game wouldn't start at all. I played a whole case from start to finish on full screen and vsync on and didn't notice anything wrong in the game itself except the "Cross-Examination" start animation stuttering. Could alt-tab from the game without problems but couldn't alt-tab back to it, had to "manually" restore the game's window by clicking on its icon on the dock.
Water on the second planet is sometimes blinking.
Sometimes stutters when going through some rifts, but for no longer than a second.
Game crashed on launch on default Proton so switched to Experimental. Also, the game shows a warning pop-up about too old graphics drivers even after updating them but it doesn't cause any issues.
The game showed as "running" but nothing was happening. It opened after installing wmp11 through protontricks.
A lot of stuttering during cutscenes.
Works fine
Disconnecting or connecting a controller while the game is running confuses the game so that it refuses to work with any controller. Controllers must be connected before starting the game for them to work.
Mouse sensitivity was way too high even on the lowest settings. Had to decrypt ini files by using a Windows binary from PCGamingWiki through Wine in order to lower the sensitivity. Also changed some other settings like FPS limit.
Way too high mouse sensitivity and some kind of "dead zone". The issue also seems to exist on Windows. Fixable through modifying encrypted ini files, see PCGamingWiki for details. Wine runs the decrypting program fine.
The game sometimes stutters for a moment.
The native version crashes with segmentation fault on startup. The Windows version through Proton just works.
SDL_VIDEODRIVER=x11 %command% -novid -nojoy -nosteamcontroller -nohltv -particles 1 -precachefontchars -noquicktime
Proton version isn't accepted by VAC, so native is mandatory.
It is worth mentioning the game doesn't (didn't?) work on Wayland on Nvidia drivers 525.60.11 without disabling AA and following https://docs.mastercomfig.com/page/os/linux/#fixing-bugs-with-newer-sdl2, or just downgrading drivers. Might be fixed in more recent drivers. See the following issue: https://github.com/ValveSoftware/Source-1-Games/issues/4553. On X.org it works without any tinkering.
Cutscenes before missions don't work, they only show one of the first (?) frames even though the sound can be heard.
VKD3D_CONFIG=dxr11 DXVK_ASYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
DualSense does not work at all without disabling Steam Input. Haptic feedback doesn't work at all, the game in the settings says that it is because controller audio is disabled, even though it is detected and works in Linux. Also, on Windows the LED seems to be green when on full health, and red when low, this feature doesn't seem to work on Linux too. So, switch to Windows in order to use the controller to its full potential in this game.
The mouse input is a little jittery, but not significantly, the game is very much playable on M&K. This is probably the game's issue, as seems to be typical with ports from PlayStation, and devs apparently are already working on the fix.
About 10-20 FPS less than I get on Windows.
Funny thing is, the crashes only happen on Windows and on X.org. I have not managed to crash the game on Wayland even with too high texture settings for my VRAM.
Listen mode does not highlight enemies which makes it almost completely useless even on lower difficulties. I say almost, because it seems to actually make footsteps louder helping to locate the enemies by the sound alone. It might be already fixed in new Proton Experimental though.
The game complains about drivers version upon launch, a minor annoyance.
It has problems detecting the amount of VRAM in settings, and did not allow me to use DLSS or change texture quality. These require the standard Nvidia flags PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 (but the game works fine without them). Note that the flags currently cause crashing on standard Proton and Proton-GE, but work in Proton Experimental.
The game is very VRAM hungry unfortunately so the texture quality must be reduced to medium on 8 GB cards to avoid stuttering. Not sure if it's related to crashes.
Installed fixes from this guide https://steamcommunity.com/sharedfiles/filedetails/?id=1692255530, protontricks to add necessary DLL overrides.
The game uses shadow buffers which are not available on modern hardware. Since the gameplay heavily relies on proper lighting, the game is unplayable without the fixes. With fixes it works great.
During cutscenes sometimes Gnome decides that the game is "unresponding" and shows the popup window asking whether to close the game or wait. However, the game keeps working fine and the popup just obstructs the cutscene. A minor annoyance.
The game is so old it requires some tinkering. At least dgVoodoo must be installed (and DLL override added) in order for the game to be playable. Use the guide linked above. Another helpful resource is PCGamingWiki: https://www.pcgamingwiki.com/wiki/Tom_Clancy%27s_Splinter_Cell
