Simon McVittie

If this is a native Linux game, then the vast majority of the libraries it's loading should be coming from your host system anyway, assuming the same SONAME for the...

We specifically don't support the "native runtime" from Arch. However, it's sometimes a useful way to find and fix issues in the official Steam Runtime. If you install all the...

> So by diffing these two logs it seems that with steam-runtime it is somehow using the system version of libSDL2 and not the one that Metro Exodus ships with,...

OK, so this is a 64-bit game. That makes things easier. If you try changing the Launch Options for Metro Exodus to each of these, which ones get good performance...

`steam-native` is not supported by Valve, you're on your own with that version. Installing `lib32-libnm` might help. > Bundled libSDL2 (2.0.8, you think): 15fps > System libSDL2 (2.0.14): 15fps >...

What is *meant* to be happening is that in the common case where "most" of your libraries are newer on the host system than in the Steam Runtime, you will...

OK, that's really useful information. It's a `RUNPATH` and not the older/mostly-deprecated `RPATH`, which means `LD_LIBRARY_PATH` is treated as "more important". From the `/proc/*/maps` it looks as though none of...

It's probably best if you ask the Metro Exodus developers to talk to Valve about the best way to solve this, either on this issue report (I can help) or...

With recent changes to our container runtime environment, you might find that selecting the **Steam Linux Runtime** compatibility tool is also a way to work around this.

> I do not wish to link everything via z:/mnt/xxxx This wouldn't help: the problem is that the container used to run Proton didn't have access to your `/mnt`, so...