Proton: Hades (1145360)

[gfbett]

Compatibility Report

• Name of the game with compatibility issues: Hades
• Steam AppID of the game: 1145360

System Information

GPU: Intel(R) HD Graphics 620
Driver/LLVM version: 3.0 Mesa 19.2.1
Kernel version: 5.3.0-22-generic
Link to full system information report as Gist:https://gist.github.com/gfbett/4f54131263c7412db4d77ddef2eee470
Proton version: 4.11-9

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-1145360.log

Symptoms

The game starts to load, and the progress bar stops halftime and just gets stuck there. When filling it gets slower and slower to advance.

Reproduction

Just run the game

[kust2708]

Hi @gfbett ,

You can solve this problem using these options :
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_ESYNC=1 %command%

However, there are some random crashs between maps and when chatting with characters.

[gfbett]

For me it still get stuck loading on the same place when using those parameters

[kust2708]

Mmmh, I removed launch options, and it does work now. I noticed that I had to switch off my controller before launch the game the first time. I need more investigation.

[kust2708]

steam-1145360.log
Here is my log if it can be usefull. I can get why I don't have the issue at launch and in the main menu after selecting save slot.

When i had the loading issue at launch, I switched off my controller and managed to see the main menu, but the game crashed right after selecting my save slot. I had to add PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to my launch option and the game worked. After that moment I don't need anymore to add any options.

However, the game crashes randomly. The more frequent crash is when the game change the map. Otherwise, it happens that the game freeze randomly (sound is still working).

EDIT: Switch off controller doesn't make differences, it was a wrong track.

[madewokherd]

* Assertion: should not be reached at /vagrant/mono/mono/utils/mono-threads.c:1066

I've seen this message before in a game that uses a managed wrapper library around dinput. Wine's mscoree tries to create two different appdomains using the mono embedding api, and mono doesn't like that.

[Cxpher]

* Assertion: should not be reached at /vagrant/mono/mono/utils/mono-threads.c:1066

I've seen this message before in a game that uses a managed wrapper library around dinput. Wine's mscoree tries to create two different appdomains using the mono embedding api, and mono doesn't like that.

Worked for a while with PROTON_FORCE_LARGE_ADDRESS_AWARE=1

Had a few game crashes but now consistently crashes when launching. Even with the controller disconnected.

Error is the same --> * Assertion: should not be reached at /vagrant/mono/mono/utils/mono-threads.c:1066

[TauAkiou]

This seems to be a problem more with the OSS driver stack, because it works perfectly on my desktop (running an nvidia card with driver) and my laptop (when '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' is set under launch options, offloading the game rendering to the dGPU).

It hangs on load when using any OSS driver for me. I have the same results when trying to run the game on another machine using Mesa (Vega 56) and when not offloaded to the dGPU on my laptop. (Intel integrated stack).

[kisak-valve]

Hello @TauAkiou, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[TauAkiou]

https://gist.github.com/TauAkiou/a1624d761ed55ab31a6acb9e9f7f6d07

This is for the laptop, which has an NVIDIA dGPU. I can reproduce the save crashing by simply not setting _NV_PRIME_RENDER_OFFLOAD=1, which tells the game to render on the dedicated NVIDIA hardware.

[gfbett]

not sure if relevant, but I enabled mesa logs and I see a lot of messages like this: Mesa: User error: GL_INVALID_ENUM in glMatrixMode

[googleson78]

Game won't start, screen just flashes black once after clicking play.

System info: https://gist.github.com/googleson78/21872d019056a7a863f04a474cf73025
Log: steam-1145360.log

[fmorency]

With Proton 5.0-2, game hangs on the first screen with the progress bar. Progress bar is around halfway and game just hangs there. Game will finally start correctly after killing and restarting it a couple of time. Game will always start correctly afterward until I reboot the computer. I have a feeling that this issue has something to do with the inputs handling (mouse/controller/...).

steam-1145360.log

[madewokherd]

Dunno if it's related but there is a .NET exception in there:

Hades.exe Error: 0 : Error/GameAnalytics: System.NullReferenceException: Object reference not set to an instance of an object
  at GameAnalyticsSDK.Net.Utilities.JSONNode.ParseElement (GameAnalyticsSDK.Net.Utilities.JSONNode ctx, System.String token, System.String tokenName, System.Boolean quoted) [0x00080] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.Utilities.JSONNode.Parse (System.String aJSON) [0x00243] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.Utilities.JSON.Parse (System.String aJSON) [0x00000] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.Http.GAHTTPApi.RequestInitReturningDict () [0x001cf] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.State.GAState.StartNewSession () [0x00014] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.State.GAState.InternalInitialize () [0x00027] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.GameAnalytics+<>c__DisplayClass10_0.<Initialize>b__0 () [0x0007b] in <881e220562404cc6a339d305d4bd0958>:0 
  at GameAnalyticsSDK.Net.Threading.GAThreading.Run () [0x00014] in <881e220562404cc6a339d305d4bd0958>:0 

[chelobaka]

Installing dotnet48 in the game Wine prefix fixes this problem but makes it barely playable due to heavy frame drop. Native Mono libraries provided very smooth experience.

[aeikum]

Hello. Proton 5.0-4 contains a fix for Hades when controllers are attached. I'm not sure how well the game is working, but it may be worth another try.

[chelobaka]

Hello. Proton 5.0-4 contains a fix for Hades when controllers are attached. I'm not sure how well the game is working, but it may be worth another try.

I tried it with Proton 5.0-4 today right after Hades received huge update itself and everything worked out of the box (fresh install, no extra dotnet). No more stuttering!

[fmorency]

Hello. Proton 5.0-4 contains a fix for Hades when controllers are attached. I'm not sure how well the game is working, but it may be worth another try.

I need to perform more testing but so far, so good. Game started with controlled attached. Thanks!

[VMReyes]

Hello, I am having the loading screen issue on Proton 5.0.4 and the latest Hades update. According ProtonDB, someone else also reported the issue. I am running on Fedora 31, i5 8300H, Intel UHD 630.

Let me know how I can help. Thanks.
steam-1145360.log

[dunestorm333]

Same loading problem using the latest proprietary Nvidia drivers!

[mohang13]

Fresh install, the game runs fine for the first time and when I died it force closes itself, then I start again and I'm facing the same loading problem thereafter. Tried every solution mentioned here nothing works.

[chelobaka]

An update

The game sometimes still freezes on loading screen but restarting usually solves this problem.

There is another problem though: the screen can freeze when a lot of stuff happening there (often last boss fight, but can happen anywhere), but you still can hear the sound of your character taking damage and eventually dying. During this glitch controls are irresponsive, you don't return to House of Hades after death and the whole run progress is lost.

My system has latest Proton Beta and Mesa 20.0.4

[kisak-valve]

Hades (1145360) missing mouse hover on Wayland

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4247.
@Mershl posted on 2020-10-08T20:38:26:

Compatibility Report

• Name of the game with compatibility issues: Hades
• Steam AppID of the game: 1145360

System Information

• GPU: RX 570
• Driver/LLVM version: Mesa 20.2
• Kernel version: 5.8.13
• Proton version: 5.0.9

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

Tooltips/effects in the game are not shown when hovering over any UI element.
The issue is not reproducable and the hover effects are working as intended with Proton-5.9-GE-7-ST.

Reproduction

Start Hades with Proton 5.0.9 on a Wayland desktop. Hover over the main menu selections - the selections are not changing. Clicking is possible, but the intended tooltips and/or effects while hovering are missing.

[werman]

Games runs fine but for the following issue:

System Information

• GPU: 5700 XT
• Driver/LLVM version: Mesa 20.3.0-devel (git-57fba85da4) LLVM 12.0.0
• Kernel version: 5.7.9
• Proton version: 5.0-9

Symptoms

Using i3wm, I cannot switch from the workspace the game is running to another workspace.
It looks like the game forces the focus back? I'm not sure.
This happens even in a windowed mode. I remember some games behave like this in a full-screen mode.
However, usually there are no issues in a windowed mode.

Reproduction

1) Have an i3wm
2) Run the game
3) Try to switch workspaces
4) Ones in a ten times workspace would be switched

Workaround

Enable virtual desktop in the wine prefix.

[Mershl]

Yesterdays update (Hades v1.36401) introduced a massive VRAM leak when playing in Windowed mode and taking focus from the game window.

System Information

• GPU: RX570
• Driver: 4.6 Mesa 20.2.0
• Kernel version: 5.8.14
• Proton version: 5.0-9

Symptoms

Using Gnome wayland or X, taking the focus of the game window in Windowed Mode will instantly rise the VRAM usage of the game exe to the GPUs limit resulting in a hang of the DE for a few seconds. The game is crashing afterwards and the VRAM is freed.

Reproduction

1. Start Hades in Windowed mode (VSync on/off both tested)
2. Choose start the game - ingame VRAM usage should be around 3GB at 1080p
3. Take focus of game using ALT+Tab or clicking other window
4. VRAM usage of Hades.exe should rise very fast until crash

Workaround

Playing in Fullscreen mode or never losing focus in Windowed mode did work for my last play session (~2 hours).

[Lightsockie]

Experiencing same issue as described by Mershl, Hades v1.36447. Except game doesn't always crash (or I'm too impatient to wait for it to?), leading to a system hang and forcing a reboot

• GPU: 5700 XT
• Driver: 4.6 Mesa 20.2.1
• Kernel version: 5.9.1-arch1-1
• Proton version: 5.0-9 & 5.13-1

[Askannz]

The October 27th patch added a Vulkan renderer that can be selected when launching the game. However it doesn't work: the game hangs on a black screen and pops a crash report window. The game still works in DirectX mode.

Text of the right box: https://paste.ubuntu.com/p/8HcjcxP2c5/

Proton log:
steam-1145360.log

GPU: GTX1060
Driver: 455.28
Kernel: 5.9.1-6-tkg-pds

[kisak-valve]

Hello @Askannz, fixme:vulkan:wine_vkCreateInstance Support for allocation callbacks not implemented yet fixme:vulkan:convert_VkInstanceCreateInfo_struct_chain Application requested a linked structure of type 1000247000. which is immediately followed by an access violation (c0000005) looks like a couple lines of interest from the log.