Proton icon indicating copy to clipboard operation
Proton copied to clipboard

HELLDIVERS™ 2 (553850)

Open NTMan opened this issue 1 year ago • 256 comments

Compatibility Report

  • Name of the game with compatibility issues: HELLDIVERS™ 2
  • Steam AppID of the game: 553850

System Information

  • GPU: AMD Radeon 7900XTX
  • Video driver version: snapshot of future 24.01 from main branch
  • Kernel version: 6.8-rc3
  • Link to full system information report as gist
  • Proton version: experimental-bleeding-edge-8.0-78688-20240207-p2dd0a6-w22132b-dab3593-ve1e961-unstripped

I confirm:

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

steam-553850.log steam-553850.log

Symptoms

After selection language in the game, I observe black screen with freezed MangoHud counters and Gnome notification that "steam_app_553850" is not responding. Screenshot from 2024-02-08 14-16-27

UPD:

Now the game freeze after change Graphic settings. Screenshot from 2024-02-09 22-09-12

steam-553850.log

Reproduction

Always

NTMan avatar Feb 08 '24 09:02 NTMan

I can get in game but hitting esc to bring up the menu or opening the social menu crashes the game for me.

LuxLucian avatar Feb 08 '24 09:02 LuxLucian

Same issue than the initial one. Starts and hangs to a black screen.

  • GPU: NVIDIA RTX 4080
  • Video driver version: NVIDIA 545.29.06
  • Kernel version: 6.7.4-arch1-1
  • Proton version: Proton Experimental / GE-Proton8-30

WhiteEyeDoll avatar Feb 08 '24 11:02 WhiteEyeDoll

Got the game to launch with GE-Proton7-55. :tada:

WhiteEyeDoll avatar Feb 08 '24 11:02 WhiteEyeDoll

Got the to launch with GE-Proton7-55. 🎉

How is it going? Game running well?

caniko avatar Feb 08 '24 12:02 caniko

Proton 8.0-5 worked just fine on desktop Kubuntu 23.10 here, no crash got into tutorial just fine.

Proton Log: steam-553850.log

For Steam Deck, GE-Proton7-55 worked (other versions did not) but you must launch it in Desktop Mode.

LiamDawe avatar Feb 08 '24 12:02 LiamDawe

Has someone played a game "online"?

alosarjos avatar Feb 08 '24 13:02 alosarjos

on my system it works image

VladimirMrzv avatar Feb 08 '24 14:02 VladimirMrzv

Running on proton 8.0-5 with -d3d11 and it's aight. 55-60+ frames pretty much all the time in a mission no craashes or weird artifacts (Running on lenovo laptop with arch/hyprland ryzen 75800h and nvidia 3060mobile) played 1 mission online no issues there

Yamy1020 avatar Feb 08 '24 14:02 Yamy1020

Game is runnin good on GE-Proton7-55. Servers had some hickups early but no issues currently. Multiplayer works.

WhiteEyeDoll avatar Feb 08 '24 15:02 WhiteEyeDoll

Can confirm it works with GE-Proton7-55 on Nixos running Hyprland. I could play and finish mission.

Going into the main menu (ESC) crashes instantly for me however.

Edit: The menu crash was present on windows as well and has since been hotfixed.

SchnozzleCat avatar Feb 08 '24 16:02 SchnozzleCat

The 1.3 GB patch allowed me to play a full game in multiplayer on GE-7-55 and Esc didn't crash the game. That said the game crashed after loading back to the ship and now can't be run anymore without hanging on load (I have a feeling it's because I changed windowing to full-screen).

zrooda avatar Feb 08 '24 20:02 zrooda

New update now has me stuck in a black screen while booting.

LuxLucian avatar Feb 08 '24 21:02 LuxLucian

Sadly, not working for me. Start video is running, then one female Soldier speaks to another and it freezes. Most times even before the soldier starts to speak. Sometimes opens the nProtect Gameguard FAQ Website by itself, maybe it could not be loaded?!

GPU: NVIDIA RTX 2070 Super Video driver version: NVIDIA 545.29.06 Kernel version: 6.6.10-76060610-generic Proton version: Proton Experimental / GE-Proton8-30 / GE-Proton7-55 / Proton 8.0-5

stevebalk avatar Feb 08 '24 21:02 stevebalk

Still working after update using GE-Proton7-55.

Found issues so far:

  • Anything newer than GE-Proton7-55 crashes at launch.
  • If the game window goes behind an another window, game window goes black and restart is required.
  • Borderless fullscreen has tiny margin of white pixels around it.
  • If game is launched with window setting set to fullscreen, the game window is black and hangs. Recovery requires editing the game configuration file manually.
/<LIBRARY_DIR>/SteamLibrary/steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/user_settings.config

fullscreen = false
borderless_fullscreen = true

WhiteEyeDoll avatar Feb 08 '24 23:02 WhiteEyeDoll

New update now has me stuck in a black screen while booting.

I fixed it by modifying the config file and dropping the quality settings /steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/user_settings.config

I went in and muddled a bunch of numbers until the game booted, then I used the menu to config my settings. Changing "graphics_preset" to 1 or 2 should also work too.

LuxLucian avatar Feb 09 '24 00:02 LuxLucian

I fixed it by modifier the config file and dropping the quality settings

@LuxLucian Just a tip, if you've fixed it by modifying something then probably also put the location of the file and the modification that you made. Because that's the first thing someone is going to ask about a comment such as yours.

chookity-pokk avatar Feb 09 '24 00:02 chookity-pokk

On Steam Deck I was able to just download the game and run it now, didn't have to switch to desktop mode or switch Proton versions at all.

On desktop I still need to use GE-Proton7-55 but it runs fairly well with that. Proton Experimental and Proton 8 run into the blackscreen issue.

ESC menu works as well since the last game update.

DomiStyle avatar Feb 09 '24 13:02 DomiStyle

GE-Proton8-30 works now!

Seems that something has been updated with the GameGuard configuration server side as no patches have landed to the game nor Proton.

Also all of the issues I mentioned in my earlier comment got fixed with the newer Proton version.

WhiteEyeDoll avatar Feb 09 '24 15:02 WhiteEyeDoll

FYI game still hangs on launch with fullscreen even on GE-8-30

zrooda avatar Feb 09 '24 16:02 zrooda

GE-Proton8-30 works now!

Seems that something has been updated with the GameGuard configuration server side as no patches have landed to the game nor Proton.

Also all of the issues I mentioned in my earlier comment got fixed with the newer Proton version.

I'm still seeing the white border even with GE 8-30.

Also, as of today the game is consistently crashing my system at random intervals (not just the game process). Hard to track down what might be causing it because all background processes that I can see also freeze/die alongside my keyboard and mouse - only way out is a manual reboot.

It might be the vague AMD issue floating around as I have 7800x3d CPU / 7800xt GPU but difficult to say. I implemented the 'fix' (for windows users at least) listed in some discussions of disabling anti-aliasing and global illuminations which had no impact. Getting the crashes on 8-30 as well as 7-55 despite not having these issues yesterday.

calvinbull avatar Feb 09 '24 19:02 calvinbull

FYI game still hangs on launch with fullscreen even on GE-8-30

Yes, seems it's 50/50 that the game launches or hangs to a black screen with fullscreen enabled.

WhiteEyeDoll avatar Feb 09 '24 19:02 WhiteEyeDoll

Was there a proton Hotfix release for this game?

alosarjos avatar Feb 09 '24 21:02 alosarjos

~~I am currently trying it out with GE-8-30. Unfortunately, I have been met with nothing but crashes during the initial menus. I can't get far along enough without it crashing. The game starts in full-screen mode, so I see the white border. I did notice a proton hotfix that came with the initial game download.~~

Update Switched to Proton Hotfix in the compatibility drop-down and re-validated the game. The game launched without crashes, but I only played with it after finishing the training zone. I switched back to GE-8-30, and I was able to run around on my deck. I did notice that changing the graphics setting makes it crash, however (e.g., Anti-aliasing), regardless of Proton version.

My system

  • Video Card:
    • Driver: AMD AMD Radeon RX 6750 XT (navi22, LLVM 15.0.7, DRM 3.57, 6.7.3-060703-generic)
  • OS
    • Ubuntu 23.10 (64 bit)
    • Kernel Name: Linux
    • Kernel Version: 6.7.3-060703-generic

Screenshot from 2024-02-09 23-13-33 Screenshot from 2024-02-09 23-14-46

Voronsky avatar Feb 10 '24 04:02 Voronsky

GE-8-31 just released, I'm seeing ~10% more fps but take it with a grain of salt

updated wine to latest bleeding edge, allows helldivers to run

zrooda avatar Feb 10 '24 09:02 zrooda

It might be the vague AMD issue floating around as I have 7800x3d CPU / 7800xt GPU but difficult to say. I implemented the 'fix' (for windows users at least) listed in some discussions of disabling anti-aliasing and global illuminations which had no impact. Getting the crashes on 8-30 as well as 7-55 despite not having these issues yesterday.

What helped me reduce the crashes (7900xt GPU) was generally reducing graphics settings. Disabling global illumination is just one of the possible settings but for example while having ultra texture details the crashes were extremely frequent and since I reduced it to medium and lowered a few other settings it did not crash yet, but I still have to test it a bit more.

This seems to point to a bug in amdgpu, and the same issue also happened to me 3 times while playing A Plague Tale Requiem, but a friend of mine was having similar crashes on Windows with the same GPU and reducing graphics settings also helped him.

This is what I logged while remotely connected to the system via SSH:
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=1751122, emitted seq=1751125
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process helldivers2.exe pid 20850 thread vkd3d_queue pid 21005
amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
amdgpu 0000:0d:00.0: amdgpu: IP block:gfx_v11_0 is hung!
amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B53
amdgpu 0000:0d:00.0: amdgpu:        Faulty UTCL2 client ID: CPC (0x5)
amdgpu 0000:0d:00.0: amdgpu:        MORE_FAULTS: 0x1
amdgpu 0000:0d:00.0: amdgpu:        WALKER_ERROR: 0x1
amdgpu 0000:0d:00.0: amdgpu:        PERMISSION_FAULTS: 0x5
amdgpu 0000:0d:00.0: amdgpu:        MAPPING_ERROR: 0x1
amdgpu 0000:0d:00.0: amdgpu:        RW: 0x1
amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:0d:00.0: amdgpu:        Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:0d:00.0: amdgpu:        MORE_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        WALKER_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        PERMISSION_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        MAPPING_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        RW: 0x0
amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:0d:00.0: amdgpu:        Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:0d:00.0: amdgpu:        MORE_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        WALKER_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        PERMISSION_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        MAPPING_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        RW: 0x0
amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:0d:00.0: amdgpu:        Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:0d:00.0: amdgpu:        MORE_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        WALKER_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        PERMISSION_FAULTS: 0x0
amdgpu 0000:0d:00.0: amdgpu:        MAPPING_ERROR: 0x0
amdgpu 0000:0d:00.0: amdgpu:        RW: 0x0
Failed to wait all pipes clean
amdgpu 0000:0d:00.0: amdgpu: soft reset failed, will fallback to full reset!
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
amdgpu 0000:0d:00.0: amdgpu: MODE1 reset
amdgpu 0000:0d:00.0: amdgpu: GPU mode1 reset
amdgpu 0000:0d:00.0: amdgpu: GPU smu mode1 reset
amdgpu 0000:0d:00.0: amdgpu: GPU reset succeeded, trying to resume
[drm] PCIE GART of 512M enabled (table at 0x00000084FEB00000).
[drm] VRAM is lost due to GPU reset!
[drm] PSP is resuming...
[drm] reserve 0x1300000 from 0x84fc000000 for PSP TMR
amdgpu 0000:0d:00.0: amdgpu: RAP: optional rap ta ucode is not available
amdgpu 0000:0d:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
amdgpu 0000:0d:00.0: amdgpu: SMU is resuming...
amdgpu 0000:0d:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x0000003f, smu fw program = 0, smu fw version = 0x004e6601 (78.102.1)
amdgpu 0000:0d:00.0: amdgpu: SMU driver if version not matched
amdgpu 0000:0d:00.0: amdgpu: SMU is resumed successfully!

mtorromeo avatar Feb 10 '24 11:02 mtorromeo

Still getting crashes after 30min-1hr on GE-8-31. AMD CPU/GPU. All graphics set to lowest, resolution reduced, scaling set to performance -- if this was medieval era, picture me at the alter bathed in blood, carcasses spread around me, dragging anything I can find up, red spurts appearing around me as I find another setting to reduce.

edit: joking aside, seems like these issues are on the game and seem cross-platform, only wanted to give a sample that GE-8-31 doesn't magically fix the crashes for AMD

jakswa avatar Feb 10 '24 15:02 jakswa

The GCVM_L2_PROTECTION_FAULT errors don't seem to be necessarily local to just Helldivers, you could try some of the fixes mentioned in the convos below. I seem to be having the same problem on my 5800X3D / 6700 XT, booted back to gdm after the driver hard resets, usually after ~2 hrs of playing.

https://bbs.archlinux.org/viewtopic.php?id=284076 https://gitlab.freedesktop.org/drm/amd/-/issues/2496 https://gitlab.freedesktop.org/mesa/mesa/-/issues/8241

zrooda avatar Feb 11 '24 13:02 zrooda

HELLDIVERS™ 2 (553850) No connection to server.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7491. @19Topgun93 posted on 2024-02-11T12:20:15:

Compatibility Report

  • Name of the game with compatibility issues: Helldivers 2
  • Steam AppID of the game: 553850

System Information

  • GPU: Geforce GTX 1070
  • Video driver version: nvidia 545.29.06
  • Kernel version: 6.7.4-zen1-1-zen
  • Link to full system information report as Gist: https://gist.github.com/19Topgun93/b24ea714f0ce2c0eeeafca0b246d84b5
  • Proton version: 1707597642 GE-Proton8-31-1-g6fb8c815

I confirm:

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

``

Symptoms

After a update from Helldivers 2. It starts with no problems. I have connect my Playstation account to Steam. But at the start screen, I cannot connect to servers. The attachment. Bildschirmfoto vom 2024-02-11 12-18-21

I have reinstall the game twice, but the Problem is still there. In Protondb, it has now Gold status. Can you help me please?

Reproduction

By me. I start the game and that's it.

steam-553850.log

kisak-valve avatar Feb 11 '24 14:02 kisak-valve

Right now servers are down / having issues, not related to Linux / Proton.

alosarjos avatar Feb 11 '24 14:02 alosarjos

@kisak-valve Aaaaah ok. Thanks kisak. I thought per problem. Thanks I know it now for the next time :)

Thanks for answering on sunday :D

19Topgun93 avatar Feb 11 '24 14:02 19Topgun93