
Łąm
Published
A game that needs 2 minutes to show a window will make anyone grind their teeth, and most people will just refund and be done with it.
PROTON_NO_ESYNC=1 %command% +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
The game doesn't start when told to run. Instead, an "id Software Launcher" appears and does nothing for a minute, then a black screen appears for another. Honestly I can play the "DRM-free" version that they released "by mistake" initially with no issues, but not current patch for months now.
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 MANGOHUD=1 %command%
Unfortunately, two very different games are bundled in this single page: Metro Exodus and Metro Exodus PC Enhanced Edition. The former is an old game running everywhere without issues. The latter is a raytracing-only game demanding Nvidia RTX, experimental Proton versions (when I played through it back in May-June) as well as launch options to run well.
You can buy both in a bundle, but once you start testing the Enhanced Edition, you can't get its saves to work in the normal rasterized version.
Therefore, I have finished the RTX-only version and its DLC on Linux, in Proton. It needed manual setup, it kept crashing until I figured out what it needed. People are posting GE-Proton versions and their settings for a reason, but those keep changing with both Proton and game updates. And I had to google a setting to edit in the game's config file for it to stop crashing in certain scenes.
But again, I played through the whole Enhanced Edition and a DLC. Bit painful to set up initially, even without the setup it's definitely not worth it (game looks worse than non-RT version which combined with the huge FPS hit is simply idiotic), but other than that, no different to native Windows.
Still, the worst thing is bundling the two very very different games on a single page. You get people reporting work-arounds that aren't necessary for the actual Metro Exodus. Then you get people mad that their Enhanced Edition doesn't work out of the box as advertised. Seriously, who made this decision?
PROTON_ENABLE_NVAPI=1 %command%
I've tried just playing with the default Proton (no dice), then found this page recommending enabling NVAPI (thanks guys!), tried current Proton Experimental and Proton-GE 8-3 - every time the same issue: the game randomly hangs every few minutes. You have to kill it externally and restart, and hope it even saved (first time there was no save, so I had to listen to the whole intro again, then raced to some checkpoint before it crashed again ;))
The whole idea of adding RT to such a technical mod is just wrong anyways. If you're a gamer, don't wait for updates. Skip this title and try the non-RT version.
Completely broken since the Spring update
__GL_SHADER_DISK_CACHE_PATH='/home/lam/.nv/SteamQC' __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 DXVK_ASYNC=1 PROTON_NO_ESYNC=1 MANGOHUD=1 gamemoderun %command%
Used to work with Proton Experimental. Now doesn't work with Experimental, 7.0, 6.3 or GE-Proton7-10. Starts loading, but hangs or crashes after a few short seconds (before the flashing lights warning is supposed to disappear). So it technically starts, but never gets to the menu.
+gfxapi D3D12 +sfxapi OpenAL
OpenAL works, forced with the command line argument.
On Vulkan, the game had constant shimmering of black triangles on all leaves. So I forced DX12 (which went through VKD3D) as advised by previous commenters.
After quitting the game and coming back to it, sometimes it couldn't start the mission after loading a saved game - it loaded, I hit "Continue" and the game crashed.
Work-around was to fiddle with graphics options before loading the save. In fact, last time I only switched from "full screen" to "borderless" and then the save loaded just fine (after 10 crashes in a row trying to test if it's related to other things).
It's Serious Sam, there's no reason to mention draw distance and constant texture pop-in, because that happens on Windows, happened in SS3 and the Talos Principle, it's how the game is :) With just a few tweaks, the game runs excellent. The only big stutters I've experienced were exploding 50 enemies at once ;) Just think about it as a bullet time slo-mo ;)
Needs manually settings OpenAL in the sound options, otherwise there's no sound.
Changed to Vulkan. Tested Proton 7, Experimental, GE-7-38 - all have the same issue: game completely hangs when switching virtual desktops (I have separate workspaces for non-game stuff but IIRC, I've tested switching windows after reading the reports here and IIRC, GE-Proton fixed that, but not switching desktops). I finished the game on GE-Proton and everything worked fine, but had to exit out of the game each time I needed to do anything else.
However, this is probably an issue with Nvidia driver, because there's always an error in dmesg: "[drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event". I haven't tried work-arounds like blacklisting nvidia_modeset module, but I still blame the driver (520.56.06 at the time of writing) - user-mode program can't be allowed to cause kernel errors.