Quoting: kokoko3kYeah, older proton is not a long term solution, but just a way to isolate the problem,

QuoteIs it because I installed the games and the libraries in another directory which is on my HDD not the SDD where my arch is installed?

Please, elaborate "and the libraries".
If you mean Steam runtimes and proton as shown in the screenshot, I don't think so.

-EDIT-
Before going deeper, you have to verify that vulkan works.
I see you're on Arch, I never used bumblebee/primus so, please try to start vkcube from vulkan-tools package via primus and verify that it works and that it uses your nvidia gpu.
If it does, keep reading.
-/EDIT-

It is an interesting topic i'm exploring, here is some background (also this:

QuoteThe core of all of these compatibility tools is pressure-vessel, which combines application-level libraries from the Steam Runtime with graphics drivers from the host operating system, resulting in a system that is as compatible as possible with the Steam Runtime while still having all the necessary graphics drivers to work with recent GPU hardware.
The Steam Play compatibility tools automatically run pressure-vessel when necessary.

...something is obviously not running good about mixing native gpu drivers and pressure-vessel filesystem. "Recent GPU hardware" may sound worrysome though.

Just some shoots in the dark:

• Are you running steam from your distro package or through flatpak? My gut feeling smells troubles if the latter is true.


• What if you run the whole steam through optirun and then try to start a game with and without optirun startup option with a newer proton, Something changes?


• What if you use Proton-Ge instead? I'm not sure at all, but it could be a way to skip pressure-vessel and a more robust alternative to proton 4, if it works.
  If you're not familiar with it, follow the installation "Native -> Manual" way.

Other related things i found:

QuoteUsing Bumblebee and Primus (optirun, primusrun, pvkrun, primus_vk) adds an extra layer of complexity that does not work reliably with the container runtime. We recommend using NVIDIA Prime Render Offload or DRI PRIME offloading instead, if possible.

If you don't manage to solve the issue, i strongly suggest you to seek for help here, by providing the output of /tmp/proton-issue.log after trying to start (and so fail) to run your game by starting steam as follows:PRESSURE_VESSEL_VERBOSE=1 PROTON_LOG=1 steam 2>&1 | tee /tmp/proton-issue.log

Quoting: mr-victoryOof. Then your best bet is nvidia-xrun or running your entire session on nvidia.

...Good luck!

Quoting: redneckdrowThe NVS 5200m is an entry level Fermi-based chip from 2012. The Fermi architecture does not support vulkan. Therefore, you're stuck with WINED3D, because you can't run dxvk.

In the launch options for the game, put

 
PROTON_USE_WINED3D=1 %command%
and it should work. But with that GPU, I doubt the performance will be great.