The Surge 2 (644830)

[Reifam]

Compatibility Report

• Name of the game with compatibility issues: The Surge 2
• Steam AppID of the game: 644830

System Information

• GPU: AMD RX 5700
• Driver/LLVM version: Mesa 19.3.1
• Kernel version: 5.4
• Link to full system information report as Gist:
  https://gist.github.com/Reifam/d91174379488044ec745dc51f7cfadaf
• Proton version: 4.11.11

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-644830.log
steam-644830-ignore.log

Symptoms

When launching the game, it immediately crashes with the following message: "Failed to execute Vulkan command 'result' (file 'D:\BuildAgents\buildAgent_pc\work\git_checkout_per_agent_branch\FledgeRenderer\renderer\src\vulkan\FledgeRendererSystemVulkan.cpp' in line '353'), returned: VK_ERROR_INCOMPATIBLE_DRIVER' "
This is what it looks like:

It presents this in a window with three options: Abort, Retry, and Ignore. Abort will just close the window and stop the game from running. Retry and Ignore both do the same thing. The game will technically be running, seeing as I can see the .exe running in top, but it doesn't actually launch into a playable or viewable state (just a process running in the background). After a minute or two, that process ends and the game quits. Above, the first log is from an abort, and the second is from an Ignore.

Reproduction

Launch the game.

[kisak-valve]

Hello @Reifam, the error message and log appears to be accurately telling you the game failed to initialize the vulkan driver. Assuming mesa/radv is otherwise healthy on the system, maybe the game bundled vulkan-1.dll (....local\\share\\Steam\\steamapps\\common\\The Surge 2\\bin\\vulkan-1.dll) is interfering with the vulkan driver stack, similar to https://bugs.winehq.org/show_bug.cgi?id=47640#c2.

[Reifam]

Hello, Kisak.
I see the issue about a bundled vulkan-1.dll In my The Surge 2/bin directory, I deleted the vulkan-1.dll that was there. However, the game crashed with the same error and the buttons have the same effects. The only copies of this dll in the .local tree are now in the common/Proton [version]/dist directories and in the compatdata directories. Any advice?

[aeikum]

It works on Nvidia. I believe this needs to be fixed in Mesa.

[Leopard1907]

Tbf ,that "it works on Nvidia" doesn't certainly mean it is a Mesa issue imo.

Just like it happened with World War Z game ( non Steam , DX11 and VLK game ). Everybody said it is a Mesa issue since VLK works with NV at initial release builds and today VLK renderer of this WWZ game doesn't even work with NV on Wine.

https://bugs.winehq.org/show_bug.cgi?id=47562

[Reifam]

Update
Update on The Surge 2. Proton hit the big 5.0, which is great! I also ran a bunch of system updates recently so all my stuff is on different versions, so I figured I'd try it again. Unfortunately these updates and changes did not improve the ability to play the game

Mesa is now 20.0.0_rc1
Kernel is now 5.5.2 (-gentoo-r1)
Proton version is 5.0-1
Nothing has changed about my systems specifications/hardware
Here's the new crash dump. Ran with just the PROTON_LOG and not the other stuff
steam-644830.log

[hakzsam]

@Reifam Are you still able to reproduce this crash with Mesa 20.0.X?

[Reifam]

Hello, I have updated my Mesa and Kernel several times since last post, and The Surge 2 works much better now. Not exactly perfect, but I was actually able to play through the game from start to finish.
The issues I've noticed now are twofold. First, after playing for about an hour, the game's framerate gets incredibly slow and choppy. Quitting the game and starting up again resolves that, but it's weird that it happens. Also, I had about 2 major instances of the game just straight up resetting my computer. Everything would go black, and soon enough I would be back at GRUB. First was randomly in some area of the game, and second was whenever I'd try to start New Game + mode.
My current versions now:
Mesa 20.0.4-r1
Kernel 5.6.4 (-gentoo)
Proton 5.0-6
New dump. I'm not sure how the proton log works so this could either be my most recent forced hard reboot or the entire log from a full NG playthrough of The Surge 2:
steam-644830.log
Like I said, aside from these occurrences of hard reboots and slowdowns, the game is actually quite playable for me.

[hakzsam]

@Reifam I think the situation with Mesa 20.1 should be even better. Does it work fine now with RADV_PERFTEST=aco ?

[Reifam]

Hello, I updated mesa to 20.1 and my kernel to 5.7.1. Unfortunately, the problems persist. When starting the NG+, I get screen freezes. This thankfully is not the entire computer rebooting, but it does require me to go into another TTY and kill X and restart it. Here's my latest proton log.
steam-644830.log
I also figured I'd include a tail of what dmesg is saying.
dmesgsurge.txt

[hakzsam]

@Reifam Can you please attach the whole dmesg log next time? It looks like you got a GPU hang. What GPU is that?

[nentibusarchitectura]

Hi,

I've just tried to run The Surge 2 and while the game runs and the menus are shown, once the game load all graphics are rendered with black textures, the geometry seems to be working as I can see the silhouette of the protagonist if I move around and get a dialog behind the character. Other Indicators, health and hud elements work fine.

I was wondering if anyone has experienced this, I tried with LLVM and the result is the same.

I'm running: Ubuntu 18.04.x,

Proton version 5.13-4 and Experimental

Linux host 5.10.0-4.3-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.10-5ubuntu1~bionic (2021-01-01) x86_64 x86_64 x86_64 GNU/Linux

OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.40.0, 5.10.0-4.3-liquorix-amd64, LLVM 11.0.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.2 - kisak-mesa PPA

Vulkan Instance Version: 1.1.70
VK_LAYER_MESA_device_select (Linux device selection layer) Vulkan version 1.1.73, layer version 1
Device Properties and Extensions :
VkPhysicalDeviceProperties:
deviceID = 0x67df
deviceType = DISCRETE_GPU
deviceName = AMD RADV POLARIS10 (ACO)

[ZereoX]

@nentibusarchitectura We've been able to reproduce your issue and an associated ticket has been entered into the Mesa tracker: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4347

We found that you can revert to Mesa 20.2.6 (https://gitlab.freedesktop.org/mesa/mesa/-/tree/20.2) stable if you want to continue playing.

[ZereoX]

Hi @kisak-valve,

The issue reported above has been resolved (https://gitlab.freedesktop.org/mesa/mesa/-/commit/43bb5f818ae407bc55945506455845ed68b457e2) and is available in the latest stable Mesa (21.0).

We've retested with latest Mesa (RX 590 and RX 5700 XT) and experience no graphical or stability issues (Crash on NG+ or during extended game play sessions [1+ hour]).

@Reifam if you are still expericing the same issues as reported previously #3426 (comment) on the latest Mesa, please provide additional details as requested above #3426 (comment).

Otherwise I think it's safe to remove the AMD / RADV labels.

[Reifam]

@ZereoX I am no longer experiencing the crashing issues on the latest Mesa. The labels can be removed.

[kapsh]

Doesn't even start here with Unhandled exception: assertion failed in 64-bit code (0x00007f8a258a13dc).
Full log:
steam-644830.log
System info: https://gist.github.com/kapsh/d1ed6eae0f256e397ae8df85aa3ce2f9

[ZereoX]

Doesn't even start here with Unhandled exception: assertion failed in 64-bit code (0x00007f8a258a13dc). Full log: steam-644830.log System info: https://gist.github.com/kapsh/d1ed6eae0f256e397ae8df85aa3ce2f9

You appear to be on Mesa 20.3.4. Might be worth updating to the latest stable release (22.2.2) or at the very least 21 or above since it was known to have issues on prior versions.

[kapsh]

@ZereoX thanks for the fast answer! I have mesa 22.2.1 here. Double checked in package info and glxinfo -B:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1) (0x731f)
    Version: 22.2.1
    Accelerated: yes
    Video memory: 8192MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 6745 MB, largest block: 6745 MB
    VBO free aux. memory - total: 7631 MB, largest block: 7631 MB
    Texture free memory - total: 6745 MB, largest block: 6745 MB
    Texture free aux. memory - total: 7631 MB, largest block: 7631 MB
    Renderbuffer free memory - total: 6745 MB, largest block: 6745 MB
    Renderbuffer free aux. memory - total: 7631 MB, largest block: 7631 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 16368 MB
    Currently available dedicated video memory: 6745 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Now I see that Steam shows mesa 20.3.4 in system info, which is weid. What else should I check?

Upd investigated a bit, this comes from installed 32 bit stuff (which I haven't updated in ages) and can be found under architectures.i386-linux-gnu json key. architectures.x86_64-linux-gnu shows current 22.2.1 version correctly.

This game is 64 bit only I think, shouldn't be an issue.

[kisak-valve]

Hello @kapsh, looking at your system information, the Vulkan render path is broken inside the Steam Linux Runtime - Soldier container environment (https://gist.github.com/kapsh/d1ed6eae0f256e397ae8df85aa3ce2f9#file-gistfile1-txt-L1064) This is the key detail to focus on while troubleshooting. This is most likely a Exherbo-specific issue and something that should be pondered on the runtime's side (https://github.com/ValveSoftware/steam-runtime/).

[rapenne-s]

Worked fine on Deck and NixOS, except on the Deck, the fonts are all gibberish but it seems to be due to fonts not scaling down well... :(

[NTMan]

The game start crashing after change VSync option from "Adaptive" to "Off":

steam-644830.log

I used mesa built from git-master https://gitlab.freedesktop.org/mesa/mesa/-/commit/03ff3c0027267240d116df5e1593ffaa974690e0

Steam Runtime Diagnostics

[kisak-valve]

Hello @NTMan, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[NTMan]

Done

[kisak-valve]

The Surge 2 (644830)

Issue transferred from #7079.
@wiscoinferno posted on 2023-09-06T14:54:39:

Compatibility Report

• Name of the game with compatibility issues: The Surge 2
• Steam AppID of the game: 644830

System Information

• GPU: Nvidia 3080 10GB
• Video driver version: nvidia 535.104.05
• Kernel version: 6.4.10-202.fsync.fc38.x86_64
• Link to full system information report as Gist: https://gist.github.com/wiscoinferno/9b92e081614444ff8c6d9a6326de2ef4
• Proton version: Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

When conversing with NPCs, and navigating menus, the option to navigate via controller (dualsense wired) randomly drops. Still able to use the face buttons to choose the top most option (or exit dialog) but cannot move up/down to choose other options. Often exiting and re-entering dialog will enable movement, but it often drops again mid conversation.

Reproduction

This happens at random using Proton Experimental. Will attach log files this evening after work and converse with an NPC.

[wiscoinferno]

Note: this appears to be an issue in windowed mode only. Switching to fullscreen seems to have corrected the issue in testing for uploading my logs.