Metro Exodus Mac and Linux Thread

[Deep Silver]

Hey guys a thread where you can discuss/troubleshoot Mac and Linux versions of Metro Exodus.

If you do encounter issues - please report it to https://support.deepsilver.com/en/games/metroexodus giving as much detail as possible so we can investigate properly.

Recommended specs: https://www.metrothegame.com/pcspecs/

[x_wing]

Originally posted by Masacre:

Ok, so I am almost 100% sure that this is a problem with the open source MESA drivers. I changed my launch options to run the game with amdvlk instead of RADV and the memory allocation sticks to 3.3GB. I let it run for enough time that it should have frozen but it did not. Just to make sure it was not something else I changed, I removed the launch options and ran the RADV drivers again and sure enough, the memory allocation kept going up.

So, you can probably run the game with amdvlk, albeit poorly (worse FPS than RADV, by quite a bit) but you will probably at least be able to run it (I've not yet tested for a longer period of time). How to do this if you do not know:

Make sure the following packages are installed:

amdvlk
lib32-amdvlk

Use the following launch option for Metro: Exodus:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json %command%

[edit] I should add that this obviously only works for AMD cards, not Intel nor Nvidia.

Yup, I can confirm. AMDVLK seems to stop the continuous allocation.

[Xpander]

Originally posted by Masacre:

[edit] I should add that this obviously only works for AMD cards, not Intel nor Nvidia.

Great find about the mem leak!. On nvidia i haven't noticed any leak at least with 465.24.02 drivers. Played 1h30 min with no issues.

[ripper81]

My system is also affected by the memory leak. After playing for 15 minutes the game starts stuttering and the system freezes. I am also using MESA 21.0.2 for my AMD Radeon RX 5700.

I wonder how this game was tested on linux before release. I bet they have used Ubuntu 20.04 LTS with the AMDGPU-PRO or AMDVLK driver. I hope this will be fixed soon since nearly no one uses these drivers. On Ubuntu AMDVLK will replace MESA RADV by default if it is installed. You have to set a startoption for each game that should use MESA RADV. That means i have to set this option for every game except Metro Exodus. MESA RADV is the Vulkandriver supported by Steam and 99% oft the games available for linux, it is also the driver that is available on most linuxdistributions.

[Panda Hug Monster]

I'm not having entrypoint executables!!! I have reinstalled, reset cache, reinstalled, still there is no the entrypoint executable. How do you run it?! I want to see already how it will crash IN THE GAME, and not on the level of steam :)!

[Ysblokje]

Okay, to get it to work on wayland : start the game once on X11.
Find the user.cfg file .local/share/Steam/userdata/<our steam id number>/412020/remote

Set

r_vsync to 1]

Start game.. play.... maybe....

Seriously @deepsilver you need to fix this nonsense!

[[Linux] Samsai]

Originally posted by Ysblokje:

Okay, to get it to work on wayland : start the game once on X11.
Find the user.cfg file .local/share/Steam/userdata/<our steam id number>/412020/remote

Set

r_vsync to 1]

Start game.. play.... maybe....

Seriously @deepsilver you need to fix this nonsense!

I confirm this method works. I cannot vouch for any effect past the main menu, but this at least gets the game running. Combined with the AMDVLK trickery it might even be fully playable.

[Herr Orange]

Originally posted by higuita:

Well, you have to give more info, i'm running a AMD RX480 with mesa 21.0.2, kernel 5.11.13, slackware 15 with X11 and works perfectly

I'm running Fedora 34 KDE, Radeon RX5700XT, X11 with mesa 21.0.2. Kernel 5.11.13

I actually also missed that one:

Apr 16 11:28:30 <hostname> kernel: MetroExodus[27342]: segfault at 0 ip 0000000000000000 sp 00007ffff5f85bf8 error 14 in MetroExodus[400000+8000]
Apr 16 11:28:30 <hostname> kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.

[Ysblokje]

Originally posted by Ysblokje:

Okay, to get it to work on wayland : start the game once on X11.
Find the user.cfg file .local/share/Steam/userdata/<our steam id number>/412020/remote

Set

r_vsync to 1]

Start game.. play.... maybe....

Seriously @deepsilver you need to fix this nonsense!

Ok not sure if it's an engine problem or not... If it's mesa at fault then I apologize.

see : https://gitlab.freedesktop.org/mesa/mesa/-/issues/4650

[AbhishekPapanna]

Originally posted by higuita:

Originally posted by abhishek.papanna:

Hi Everyone,
Is anyone else experiencing Sound issues? I am hearing a lot of crackling and noise in sound.

That is usually a issue with pulseaudio and the cpu/audio card, try adding this to the game steam command option and finetune the value

PULSE_LATENCY_MSEC=60 %command%

Originally posted by Herr Orange:

So, what's the trick to run it with Radeon graphics? It crashes right away with:

Well, you have to give more info, i'm running a AMD RX480 with mesa 21.0.2, kernel 5.11.13, slackware 15 with X11 and works perfectly

This doesn't do anything, I have already tried this. The noise I mention is more like a constant pulse in the audio like da,,,da,,,da,,,da,,,. It is disturbing and causes lot of stutter in both music and dialogue.
I even did a fresh install of the game today but, it didn't help, still seeing this issue.

[御竿義信 yoshi]

Originally posted by Ysblokje:

Okay, to get it to work on wayland : start the game once on X11.
Find the user.cfg file .local/share/Steam/userdata/<our steam id number>/412020/remote

Set

r_vsync to 1]

This also fixed it for me.

Also, I'm only able to run the game using RADV. I never used AMDVLK for anything, but after installing both amdvlk and lib32-amdvlk, trying to launch the game using their libraries hangs the system for me. Since running the game + radv results in a memory leak, I guess I'll have to wait a little longer to beat the game in ranger hardcore.

[Masacre]

Originally posted by 御竿義信 yoshi:

Originally posted by Ysblokje:

Okay, to get it to work on wayland : start the game once on X11.
Find the user.cfg file .local/share/Steam/userdata/<our steam id number>/412020/remote

Set

r_vsync to 1]

This also fixed it for me.

Also, I'm only able to run the game using RADV. I never used AMDVLK for anything, but after installing both amdvlk and lib32-amdvlk, trying to launch the game using their libraries hangs the system for me. Since running the game + radv results in a memory leak, I guess I'll have to wait a little longer to beat the game in ranger hardcore.

This also happened to me the first time I tried running it with amdvlk. I removed all other launch options (only had gamemode) and did a reboot (I had just installed the drivers, figured they might not have been loaded in properly). After that it worked for me. So if you have any other launch options you could try removing them and do a reboot. Worth a shot.

[Rob-Retro(Linux)]

Originally posted by Xpander Linux:

Originally posted by Masacre:

[edit] I should add that this obviously only works for AMD cards, not Intel nor Nvidia.

Great find about the mem leak!. On nvidia i haven't noticed any leak at least with 465.24.02 drivers. Played 1h30 min with no issues.

I get memory leaks on I7 -16GB Ram and RTX2060 with Driver 460.67, And i not alone, but we are all on blob driver 460.67.

[julek]

Do you experience lots of crashes with NVidia driver 460.67 (I'm on Debian Bullseye, RTX 2070 SUPER)

[ripper81]

Originally posted by TheReaperUK:

Originally posted by Xpander Linux:

Great find about the mem leak!. On nvidia i haven't noticed any leak at least with 465.24.02 drivers. Played 1h30 min with no issues.

I get memory leaks on I7 -16GB Ram and RTX2060 with Driver 460.67, And i not alone, but we are all on blob driver 460.67.

So the memory leak issue is not limited to AMD and MESA.

[Rob-Retro(Linux)]

Originally posted by julek:

Do you experience lots of crashes with NVidia driver 460.67 (I'm on Debian Bullseye, RTX 2070 SUPER)

No crashes, i'm on Manjaro if that matters, I played the whole game in 3 sittings and also played 1 of the dlc in 1 sitting and the only reason i may not be crashing because of memory leak is i have a Swap partition of 45GB, did see 1 nasty graphics issue, long coloured polygons from the ceiling to the floor, which i think might have been a broken chandelier that fallon to the ground.

Looks like Google Stadia version has memory leaks as well.