Quoting: DebianUser

Quoting: ripper81358

Quoting: DebianUser

Quoting: ripper81358

Quoting: BielFPs

Quoting: drlambWell the game crashes for me on Mesa-git so...

Mine doesn't even start, first it was crashing without anything, them I've forced the game to run once using steam runtime (so it could download some files) and try to run without it again.

It still crashes, but now it open a black screen before crashing, instead of not opening at all.

The MESA Fix for Metro Exodus has nothing todo with the game crashing on startup. It fixes a memory leak that appears after playing for 10-30 minutes.

For fixing crashes on startup you could try the following.

1. Avoid Wayland
2. Set the right native displayresolution in the games user.cfg file
3. Make shure that libibus is installed

Same here, game is crashing at startup.. i have a black window... 1/4 of a second.

- i'm on wayland with XWayland i think: "WaylandEnable=false" in /etc/gdm3/custom.conf
- libibus-1.0-5 installed
- no user.cfg in game folder
- weird thing, but i have tried to rename the .webm files into the game folder (i heard this could help, but not in my case, so i have renamed them back to their original name)
- i have tried "~/.steam/steam/steamapps/common/SteamLinuxRuntime_soldier/run-in-soldier %command%" with no success

In syslog, i see this when i try to launch the game:
kernel: [28873.954999] traps: A3 :: worker[592167] general protection fault ip:7f863fcdaad1 sp:7f85577fb138 error:0 in libc-2.31.so[7f863fba0000+14b000]

The user.cfg is located in an hidden folder in your home directory not in the games folder itself. Take a look into the
.local or.config folder.

Please login into a prober X11/X.Org session before launching the game. Wayland is not ready for gaming at this point.

Too bad, i'm just to dumb to make a proper Xorg configuration with my two screens...

You could try to log into an X11/X.Org session once. Then start steam and launch the game. Make sure that the display resolution is set correctly in the videooptions. After this is done quit the game and logout of the X11 session. You should now be able to launch the game from you Waylandsession.

View this comment - View article - View full comments

Quoting: DebianUser

Quoting: ripper81358

Quoting: BielFPs

Quoting: drlambWell the game crashes for me on Mesa-git so...

Mine doesn't even start, first it was crashing without anything, them I've forced the game to run once using steam runtime (so it could download some files) and try to run without it again.

It still crashes, but now it open a black screen before crashing, instead of not opening at all.

The MESA Fix for Metro Exodus has nothing todo with the game crashing on startup. It fixes a memory leak that appears after playing for 10-30 minutes.

For fixing crashes on startup you could try the following.

1. Avoid Wayland
2. Set the right native displayresolution in the games user.cfg file
3. Make shure that libibus is installed

Same here, game is crashing at startup.. i have a black window... 1/4 of a second.

- i'm on wayland with XWayland i think: "WaylandEnable=false" in /etc/gdm3/custom.conf
- libibus-1.0-5 installed
- no user.cfg in game folder
- weird thing, but i have tried to rename the .webm files into the game folder (i heard this could help, but not in my case, so i have renamed them back to their original name)
- i have tried "~/.steam/steam/steamapps/common/SteamLinuxRuntime_soldier/run-in-soldier %command%" with no success

In syslog, i see this when i try to launch the game:
kernel: [28873.954999] traps: A3 :: worker[592167] general protection fault ip:7f863fcdaad1 sp:7f85577fb138 error:0 in libc-2.31.so[7f863fba0000+14b000]

The user.cfg is located in an hidden folder in your home directory not in the games folder itself. Take a look into the
.local or.config folder.

Please login into a prober X11/X.Org session before launching the game. Wayland is not ready for gaming at this point.

View this comment - View article - View full comments

Quoting: BielFPs

Quoting: drlambWell the game crashes for me on Mesa-git so...

Mine doesn't even start, first it was crashing without anything, them I've forced the game to run once using steam runtime (so it could download some files) and try to run without it again.

It still crashes, but now it open a black screen before crashing, instead of not opening at all.

The MESA Fix for Metro Exodus has nothing todo with the game crashing on startup. It fixes a memory leak that appears after playing for 10-30 minutes.

For fixing crashes on startup you could try the following.

1. Avoid Wayland
2. Set the right native displayresolution in the games user.cfg file
3. Make shure that libibus is installed

View this comment - View article - View full comments

On Ubuntu (and official flavors) and ubuntubased distros the fix already available via the kisak mesa fresh ppa:

https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa [External Link]

This contains the latest stable bugfixrelease with the fix backported.

View this comment - View article - View full comments

From a linuxusers perspective i must say that i am mostly using opensource software. The only exception in my case is gaming where i am in proprietary land. So i choose the store that supports my OS of choice best. And that is without a doubt steam. It might be a good idea to lower the 30% cut at least for indie developers to keep steam attractive for them. I am not a fan of having different gamelaunchers on my system. Even if Epic and others would support linux i would rather stick with steam to keep the gaming stuff all in one place. Having multiple tools to do the same thing is useless from an endusers perspective. In my opinion all "secondary" launchers (Origin,Ubisoft..) should be removed from games distributed over steam.

View this comment - View article - View full comments

Quoting: Leopard

Quoting: ripper81358

Quoting: Liam DaweAMD fix coming to Mesa for Exodus: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 [External Link]

I still wonder how the game was tested before it was released. This problem should have been noticed. The systemrequirements of Metro Exodus are telling nothing about drivers. The game might run well with AMDGPU-PRO, but nearly all AMD GPU owners are running MESA for gamingpurposes for more than one good reason.

I am running the game with AMDVLK right now. I get 45-60 FPS with 1080p and quality set to ultra. With MESA RADV i get 75-110 FPS at the same quality. AMD should just adopt MESA RADV as their official linux vulkandriver. No one needs AMDVLK or the proprietary OpenGL and Vulkandrivers for desktopusage or gaming. AS both are not available and inferior in compatibility and/or performance.

They should realy set an end to this fragmented situation.

1-) Simply they didn't test it on RADV because none of the Steamworks docs were mentioning RADV and even worse they were recommending usage of prop drivers. An old time relic that hopefully will be fixed soon. Which when you don't mention stuff like that your usual Windows centric dev will just do the things with their usual method. Go to vendors website, install the driver.

2-) AMD can't drop AMDVLK. Due to both Windows side needs that always,Stadia needs that and it is their in house reference implementation. Radv is a third party,unofficial driver from AMD's POV,rightfully.

Potential solution would be devs sending some pre release keys to Mesa devs before release to test and fix if there are any issue. But that ultimately leads to clause 1.

I understand that the proprietary driver (AMDGPU-PRO) is needed in some cases but i do not understand why we need two opensource drivers for vulkan. AMD should adopt MESA RADV and handle things the same way as with MESA RadeonSi for OpenGL. The proprietary Vulkandriver and AMDVLK share a lot of code as far as i know. AMDVLK is always behind the proprietary driver in all benchmarks and also looses compared to MESA RADV because of it's LLVM shadercompiler backend. So why should anyone use it. I'd say one proprietary driver and one opensource driver are enough for one OS.

View this comment - View article - View full comments

Quoting: Liam DaweAMD fix coming to Mesa for Exodus: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 [External Link]

I still wonder how the game was tested before it was released. This problem should have been noticed. The systemrequirements of Metro Exodus are telling nothing about drivers. The game might run well with AMDGPU-PRO, but nearly all AMD GPU owners are running MESA for gamingpurposes for more than one good reason.

I am running the game with AMDVLK right now. I get 45-60 FPS with 1080p and quality set to ultra. With MESA RADV i get 75-110 FPS at the same quality. AMD should just adopt MESA RADV as their official linux vulkandriver. No one needs AMDVLK or the proprietary OpenGL and Vulkandrivers for desktopusage or gaming. AS both are not available and inferior in compatibility and/or performance.

They should realy set an end to this fragmented situation.

View this comment - View article - View full comments

Quoting: CFWhitman

Quoting: ripper81358

Quoting: CFWhitman

Quoting: x_wing

Quoting: ripper81358AMD GPU owners should avoid this game for now. It seems to have massive problems with the MESA drivers.

The only way to get it working without trouble is to use AMDVLK right now. The performance is not good with this driver though.

I didn't notice a big difference between AMDVLK and Radv, maybe a few less frames here and there (I'm using vsync though).

I've heard reports of running out of memory and crashing with RADV after you had played for a while. I haven't tried it yet. I just started 2033. I figure by the time I make it through that and Last Light, the issues will have been figured out for the most part.

The problems reported for AMD GPU's are ranging from instant crashes on startup to memory leaks that consume all the RAM available on the system. Metro Exodus uses Vulkan as the graphics API. The older Metro games are using OpenGL. So two different MESA drivers are used for the games.

The reports I've heard of instant crashes on startup seem to be related to running Wayland rather than actually anything to do with AMD GPUs. It's just that most Wayland users have AMD GPUs. I don't currently use Wayland, so that's not likely to be an issue for me.

I mentioned the apparent memory leak related to RADV. It seems that using AMDVLK functions as a workaround to this issue for the time being.

I'm well aware that Exodus uses Vulkan while the older games use OpenGL. I'm not sure how that's important. As I said, I hadn't played the earlier games, and I figure by the time I have played through them, the initial hiccups of the new release will be mostly ironed out. By then, I'd expect the RADV problem to most likely be fixed, but even if I did have to play with AMDVLK, it wouldn't be the end of the world.

Using AMDVLK is not the end of the world for sure. But it should not be neccesary. AMDVLK is not easily available on many distributions. If you install it on Ubuntu alongside MESA RADV the system will default to AMDVLK. That means you have to set a startoption for every game that should use MESA RADV just because one game needs AMDVLK. AMDVLK also causes trouble with the Vulkan shaderprocessing because once it is installed steam will recompile all shaders for AMDVLK instead of MESA RADV.

While i got the game working with AMDVLK performance is noticeable worse. I get stuttering while playing which isn't the case with MESA RADV.

View this comment - View article - View full comments

Quoting: CFWhitman

Quoting: x_wing

Quoting: ripper81358AMD GPU owners should avoid this game for now. It seems to have massive problems with the MESA drivers.

The only way to get it working without trouble is to use AMDVLK right now. The performance is not good with this driver though.

I didn't notice a big difference between AMDVLK and Radv, maybe a few less frames here and there (I'm using vsync though).

I've heard reports of running out of memory and crashing with RADV after you had played for a while. I haven't tried it yet. I just started 2033. I figure by the time I make it through that and Last Light, the issues will have been figured out for the most part.

The problems reported for AMD GPU's are ranging from instant crashes on startup to memory leaks that consume all the RAM available on the system. Metro Exodus uses Vulkan as the graphics API. The older Metro games are using OpenGL. So two different MESA drivers are used for the games.

View this comment - View article - View full comments

AMD GPU owners should avoid this game for now. It seems to have massive problems with the MESA drivers.

The only way to get it working without trouble is to use AMDVLK right now. The performance is not good with this driver though.

View this comment - View article - View full comments