Bilbo Fraggins
Published
This game launches and plays, but you're unable to play any missions due to EAC anti-cheat.
Proton-6.14-GE-2 GloriousEggroll
Proton-6.14-GE-2
Game launches and you can move around the main camp, but matchmaking, text chat, and online play are completely broken, presumably due to Easy Anti-Cheat
If Valve fixes Easy Anti-Cheat support when the Steam Deck comes out, I expect this game to work flawlessly. However, in its current state, the game is totally unplayable due to broken multiplayer, which is a shame because the game seems to perform pretty well when you're running around in the base camp.
Proton-6.14-GE-2 GloriousEggroll
I used Proton-6.14-GE-2
Game keeps saying "Lost connection to chat server". Not sure if this is because of the beta or if its some issue with Proton
Currently the early access beta works in Proton, even with EAC anti-cheat. No guarantees that it will work when the final version comes out though.
Works great with DX11 renderer, slow performance with Vulkan renderer ever since Patch 2
Ever since Patch 2, using the Vulkan renderer results in poor performance compared to DX11. I've tested it in Windows and it works fine, so there's something weird with how the Vulkan renderer behaves under Linux and Proton.
__GL_13ebad=0x1 %command%
If you're on Nvidia and you want to use the Vulkan Renderer, it is imperative that you use the __GL_13ebad=0x1 %command% launch parameters otherwise your framerate will be halved! This game has the same issue as Doom Eternal and Indiana Jones where the GPU does not properly clock up, causing low performance unless you specify that parameter. Nvidia has specified custom profiles for those two games to address the performance issues but has never done the same for BG3 so you have to manually do it yourself. After that the Vulkan renderer works great!
Game runs fine, but you have to disable DXR on Nvidia cards due to a driver bug that causes a crash.
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=nodxr %command%
Slight shader stutter, but it clears up after a while
Disable DXR via VKD3D_CONFIG=nodxr, otherwise DX12 with raytracing on will crash the game on startup.
Game runs, but you can't change graphics settings without the game crashing. Changing graphics settings will also make the game unbootable until you clear the "460790" folder in compatdata.
With the upgrade to Proton 4.11-1, the graphics settings now saves properly and doesn't cause the game to crash. The game seems to work perfectly!
PROTON_OLD_GL_STRING=1 %command% +set r_mode -1 +set r_customwidth 3840 +set r_customheight 2160 +set r_fullscreen 1 +set cg_fov 106 +set com_maxfps 110 +set r_ignorehwgamma 1 +set com_introplayed 1
You need to use launch options or edit the game configs to get widescreen resolutions
The only issue is the inability to switch to a widescreen FOV like I can in singleplayer. Also I have not tested Punkbuster, but most of the servers that are still up today do not use it.
IMPORTANT: You need to use an old version of Proton in order for the screen to not be rainbow colored.
Launch options explained:
"PROTON_OLD_GL_STRING=1" - Necessary for United Offensive expansion to not crash
"+set r_mode -1 +set r_customwidth 3840 +set r_customheight 2160 +set r_fullscreen 1" - Necessary to get widescreen resolutions. Modify as you see fit.
"+set cg_fov 106" - Set FOV for widescreen resoutions. Only works in SP.
"+set com_maxfps 110" - Limit framerate so it stays under your Gsync or Freesync range. Make sure to turn off vsync in-game.
"+set r_ignorehwgamma 1" - Works around the game being too dark by default.
"+set com_introplayed 1" - Intro movies don't work with widescreen resolutions so just disable them.
This game used to stutter like crazy for me with old versions of Proton, but all of those issues have been resolved. It works great out of the box now with smooth frame delivery.
PROTON_OLD_GL_STRING=1 %command% +set r_mode -1 +set r_customwidth 3840 +set r_customheight 2160 +set r_fullscreen 1 +set cg_fov 106 +set com_maxfps 110 +set r_ignorehwgamma 1 +set com_introplayed 1
You need to use launch options to get widescreen resolutions
Some funkyness with the mouse acceleration in multiplayer. Nothing too major though.
Can't change FOV in MP. Have not tested Punkbuster but most servers nowadays don't use it anyways.
IMPORTANT: You need to use an old version of Proton in order for the screen to not be rainbow colored.
Launch options explained:
"PROTON_OLD_GL_STRING=1" - Necessary for United Offensive expansion to not crash on startup.
"+set r_mode -1 +set r_customwidth 3840 +set r_customheight 2160 +set r_fullscreen 1" - Necessary to get widescreen resolutions. Modify as you see fit.
"+set cg_fov 106" - Set FOV for widescreen resoutions. Only works in SP.
"+set com_maxfps 110" - Limit framerate so it stays under your Gsync or Freesync range. I have a 120Hz monitor so 110 is the right value for me. Adjust as you see fit. Make sure to turn off vsync in-game.
"+set r_ignorehwgamma 1" - Works around the game being too dark by default.
"+set com_introplayed 1" - Intro movies don't work with widescreen resolutions so just disable them.
Loading times are significantly improved if you disable Shader Preload in the Graphics settings. However, this will incur significant stuttering during gameplay until all the shaders have been cached. The stuttering makes the game almost unplayable. When the game isn't stuttering, it performs admirably. I get around 80-100 FPS on my Vega 64.
Very playable with the Nvidia 510.47.03 drivers. Minor performance bugs that are easy to workaround
There's a bug where performance drops dramatically when loading a new level. However, going into graphics settings and then immediately backing out and clicking Yes to "Apply new settings?" seems to temporarily reset game performance until the next level load. Otherwise the game performs flawlessly, even with raytracing.
There's a reproducible game crash the first time you see a "slab" with the Nvidia 495 drivers. However, with the 510.47 drivers, this crash no longer seems to happen.
PROTON_ENABLE_NVAPI=0 %command%
It works really well, especially in coop multiplayer. I tested with both Proton 8 and Proton Experimental. The only issue I ran into was that if you have NVAPI enabled, the game will refuse to get past the first loading screen. If you have NVAPI enabled in your environment variables, you have to pass in PROTON_ENABLE_NVAPI=0 %command% just to get the game to launch.
Game starts, but all videos (intro cinematic and any in-game displays) show a grey screen. Additionally, first level loads with broken shadows. Half the screen is pitch black. Tried all three Proton tweaks, had zero effect. Game is unplayable.
Works great out of the box. Already played 127 hours of this game, all on Linux.
It launches using SteamDeck=1, but mouse look doesn't seem to work. Playable with controller though.
SteamDeck=1 %command%
Mouse look doesn't work. This may be a side effect of using SteamDeck=1
It launches using SteamDeck=1, but mouse look doesn't seem to work. Playable with controller though. Set Atmospherics to Medium for FPS
SteamDeck=1 %command%
Mouse look doesn't work. This may be a side effect of using SteamDeck=1
Atmospherics set to a setting higher than "medium" causes framerate dips. My Nvidia 3090 can only go at 40fps whenever it is higher than medium.
VKD3D_DISABLE_EXTENSIONS=VK_NV_device_generated_commands_compute %command%
Performance in general seems to be a bit slower than in Windows. There's also a weird bug that causes bad framepacing and lower framerate until you toggle in-game Vsync on and off.
If you have Steam's background shader processing turned on and it's actively processing shaders while you launch the game, it will usually crash at the intro progress bar. I find that if you just let the background shaders finish and then launch the game, it usually works.
There's also a crash with Nvidia drivers right when you load into the singleplayer campaign, but this can be worked around by using the launch option: VKD3D_DISABLE_EXTENSIONS=VK_NV_device_generated_commands_compute %command%
It's definitely very playable, but beware of crashes and weird raytracing performance and glitches
VKD3D_CONFIG=dxr11 PROTON_ENABLE_NVAPI=1 %command%
Raytraced reflections have flickering square-shaped glitches in them
Turning raytracing on really tanks the framerate from 70-80 fps to 35-60 fps. I have not tested this in Windows so I can't say if this is just the game or a Linux-specific issue.
Game seems to have a high chance of crashing when loading a save or during major level changes. Best to save frequently before and after quests.
It's definitely very playable, but beware of crashes and weird raytracing performance and glitches.
VKD3D_CONFIG=dxr11 PROTON_ENABLE_NVAPI=1 %command%
Raytraced reflections have flickering square-shaped glitches in them
Raytracing seems to have lower than expected performance. I have not compared with Windows though.
You need to increase your system's vm.max_map_count to avoid crashes during level loads. See https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422699309 for details.
I increased my value to 2147483642, which is the same value that's on the Steam Deck. This seems to help game stability a lot. You can easily do this before you run the game with sudo sysctl -w vm.max_map_count=2147483642
It is extremely important to increase your system's vm.max_map_count otherwise you WILL get frequent crashes! Otherwise, it's very playable.
To enable DLSS, you need "PROTON_ENABLE_NVAPI=1 %command%" in your launch options and "dxgi.nvapiHack = False" in your dxvk.conf.
Game crashes on launch unless Wine D3D11 is used.
This game used to work before, but ever since the Epic Account integration, Knockout City has been unable to login. I get a netcode error.
Game works well in DX12 mode. Just don't use VKD3D_CONFIG=dxr11
If you have raytracing enabled via VKD3D_CONFIG=dxr11, the game will refuse to start. Otherwise, the game works really well in DX12 mode.
VKD3D_CONFIG=dxr11 PROTON_ENABLE_NVAPI=1 %command%
It is amazing that this works so well out of the box on day 1. Valve, Proton, Wine, and Linux have come a long way.
Metro Exodus Enhanced Edition crashes at a specific part in the game. Can't get past it.
Occasionally there will be intense lag spikes, frequently after meleeing an enemy
Crashes whenever I try to go down the bunker elevator after meeting Giul.
Metro Exodus Enhanced Edition runs really well when Hairworks is disabled. You need the listed launch options to enable raytracing and DLSS
VKD3D_CONFIG=dxr11 PROTON_ENABLE_NVAPI=1 %command%
Like others have mentioned, enabling Hairworks causes crashes, especially when going down the elevator after meeting up with Giul. Disabling it allowed me to get past that part.
Game works pretty much out of the box with the Vulkan Renderer now. I get 115fps with Vulkan vs 90fps with DX12.
The retail Quake 2 installer needs your system libcurl.so.4
When running the retail Quake 2 data importer, you may get an issue saying version /usr/bin/zenity: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libcurl.so.4: version CURL_OPENSSL_4' not found (required by /usr/lib/libappstream.so.5).
Temporarily rename that libcurl.so.4 in the steam run time to something else for backup purposes and then copy the libcurl.so.4 from your system's /usr/lib into the same location. Then rerun the data importer. It should ask where your retail Quake 2 install directory is. After it completes, you should see the retail Quake 2 paks under ~/.quake2rtx. Restore your old libcurl.so.4 just to clean up and launch the game.
When the game actually runs, performance is great. However, it is currently too unstable to be playable. AsyncComputeDisable did not help.
Proton-6.14-GE-2 GloriousEggroll
Proton-6.14-GE-2
Alt-tab crashes the game. Any OSD elements that pop up (volume OSD, notifications, etc.) will cause the game to freeze for 5 seconds.
Game crashes on alt-tab. It also crashes randomly during the game and also when accessing the in-game menu via Tab.
Any OS level notifications or OSD will cause the game to freeze for 5 seconds.
Game runs smoothly when it isn't compiling shaders.
There's definitely shader stutter happening and it will pause the game/interfere with cutscenes. Once the shader cache has been built up, performance is very good.
Game works out of the box with Proton Experimental
The game works and is playable, but has the black water graphics bug that occurs on AMD hardware.
Water is rendered in a dark black color instead of the usual deep blue
Performance is mostly good, but certain particle effects really affect performance dramatically.
Certain particle effects, like the lightning dash and the quick reload on the shotgun seem to affect performance dramatically. On my 3090, the framerate usually hovers around 135+, but when those effects occur, it can dip below 30fps for 2 seconds. It can be very distracting especially since this game is a fast paced rogue-lite shooter.
Works out of the box. Slight shader cache stutter at the beginning but goes away after a minute.
It mostly works. There's a few issues with the game getting stuck on loading screens but there are workarounds.
The game once in a blue moon will decide to freeze during level transitions, but you can get past most of these freezes by restarting the game. There's one particular loading screen after getting past Addair, successfully restarting the generators, and talking with Brodie over the phone that absolutely refuses to work. It just gets stuck on a black screen. The workaround for me was to disable FSR 3 and Frame Gen and switch to DLSS. Once I did that, it got past the loading screen. I am not sure what exact setting was causing the issue, whether it was vsync, frame-gen, or just FSR 3 in general, so try a bunch of them out to see if you can get past. It is doable.
Runs perfectly out of the box. Disable Steam Input to get vibration on your Xbox One controller though
If you're using an Xbox One controller with the xone driver, disable Steam Input to get vibration support
Dropping the Max TDP to something like 8 or 9 gave noticeable battery life improvements without sacrificing much performance.
Works out of the box. Slight shader cache stutter for the first 15 seconds but runs well afterwards.
Big shader cache stutters
Game crashes frequently and randomly, usually during cutscenes
PROTON_ENABLE_NVAPI=1 %command%
Works super smoothly at 120fps
PROTON_ENABLE_NVAPI=1 %command%
Enabling voice chat causes the game to crash after 5 seconds
Disable voice chat to prevent crashes.
It works very well out of the box. No tweaks necessary.
However, there is obviously no DLSS support as that has not been implemented in VKD3D yet so if you enable raytracing it will incur a heavy hit, especially if you're running at native 4k.
It works very well out of the box. No tweaks necessary.
You should add "VKD3D_CONFIG=dxr %command%" to the launch parameters in order to enable raytracing. However, enabling raytracing will incur a heavy hit at high resolutions since there is obviously no DLSS support in VKD3D yet.
Game works really well, but disable Physx as it causes a huge framerate dip.
Enabling Physx drastically slows down game framerate and it remains for the rest of the play session until you restart the game. Performance is otherwise fantastic when Physx is disabled.
Ambient Shadows cause major visual artifacts but besides that the game seems playable. Might be worth waiting for patch on your high-end PC.
SteamDeck=1 %command%
If you set Ambient Shadows under Shadow Quality to anything higher than Low, you'll see weird blocky circular shadows around many objects. There's clearly some shader error happening here.
Sony continues their idiotic behavior of requiring SteamDeck=1 on non-Steam Deck Linux PCs to disable their non-functional PSN overlay. You need that parameter otherwise the game will not launch. SteamDeck=1 should not be abused in this way by game devs.
Game starts up, displays progress bar, continues on to around 80%, starts playing a sound that sounds like rushing water, and then hangs indefinitely. Pressing ESC quits the game.
Game runs well on High Settings @ 2560x1440 out of the box. Ultra settings renders at 200% resolution and runs much slower.
PROTON_ENABLE_NVAPI=1 %command%
You HAVE to use PROTON_ENABLE_NVAPI=1 in order to launch it on Nvidia cards, otherwise it will crash on startup.
WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command%
This game doesn't like CPUs with high core counts. Out of the box, the game will stutter like crazy. I had to use WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command% as a launch parameter in order to get rid of the stutter. Afterwards, performance was great at 4k Max settings.
WINE_CPU_TOPOLOGY=12:0,1,2,3,4,5,6,7,8,9,10,11 %command%
This game doesn't like using the SMT cores on my Ryzen 3900x. Out of the box, the game will stutter like crazy. I had to use WINE_CPU_TOPOLOGY=12:0,1,2,3,4,5,6,7,8,9,10,11 %command% as a launch parameter to limit the game to physical cores only. That seemed to get rid of the stutter. Afterwards, performance was great at 4k Max settings.
You need to check your CPU topology using a tool like lstopo. Then use the first CPU thread on each core. For my Ryzen 3900x, it seems like the first threads on each core are labeled 0-11, which is why I used those for WINE_CPU_TOPOLOGY. Your system may be different so make sure to check!
