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.

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

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.

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.

* 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.

* 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

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).

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.

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

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

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

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

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 

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.

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.

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!

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!

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

Same loading problem using the latest proprietary Nvidia drivers!

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.

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

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

A new update to Hades has been published yesterday which hopefully fixes the issues with memory leaks on DX11 for Proton 5.0-10 and 5.13.

The Vulkan build still doesn't initialize the device on Proton but should work through Proton-GE

The game launches and works fine with DX11 on 5.13-4 for me, but I need to disable the controller API, otherwise the input is doubled and movement is almost impossible. Without Controller API it works fine (XBOX One S Controller).

Vulkan build starts for me, but hangs on alt + tab and needs to be killed, also Steam overlay doesn't start. Haven't tested the game too much with Vulkan yet.

Sysinfo: https://gist.github.com/NoXPhasma/1cebc751ddab3708d4492b95982896ed
Proton log (Vulkan): steam-1145360.log

Just bought this, it seems to boot with Vulkan on Proton Experimental, but I'm getting the same two issues @NoXPhasma lists above. Namely the Steam Overlay doesn't work and alt-tab or loss of focus makes the window go black, however music continues and I'm unable to continue without forcably killing the game.

Worth noting also is that the loss of focus issue is identical to Doom Eternal on my Nvidia system, so it seems this may just be an issue with modern Vulkan games in Proton on Nvidia and not game-specific.

While game runs great with Proton 5.13-4 , Steam Overlay doesn't work properly with Vulkan renderer of the game (renderer itself works fine ) , Steam Overlay works properly with D3D renderer (DXVK) which is the default renderer option.

Nvidia GTX 1050 , 455.45.01 driver.

The game launches and works fine with DX11 on 5.13-4 for me, but I need to disable the controller API, otherwise the input is doubled and movement is almost impossible. Without Controller API it works fine (XBOX One S Controller).

The game has updated to SDL 2.0.14 which started using RawInput for handling xinput devices which in turn hit a bug in Wine and caused the behavior you have described. There's a fix for that in the newest experimental (https://github.com/ValveSoftware/wine/commit/3f5e9b902a37728c19a1336530349b312acbee24). There are still some rough corners around hotplug, namely switching from a xinput to a non-xinput (e.g. DualShock) device but I am working on getting that sorted out too.

That bug can be worked around using SDL_JOYSTICK_RAWINPUT=0

What is Hades doing to detect controllers? I can't do anything at all to get controllers to work in the Flatpak version of Steam, even with the big ugly /run/udev hole poked into it, which fixes most native games with broken controller input in Flatpak. Even on the distro package for Steam, controllers don't work unless I use a Proton version before 5.13 and set the launch options to SDL_JOYSTICK_RAWINPUT=0 %command%. Should I be posting this on the issue tracker for the Flatpak version instead?

I experience a crash of the game while having the nintendo switch pro controller plugged in. The crash looks similar to the one of a previous commentor (https://github.com/ValveSoftware/Proton/issues/3312#issuecomment-717800602).

System Information

• GPU: RTX 3070 Ti
• Driver version: nvidia 470.63.01
• Kernel version: 5.13.16-200.fc34.x86_64
• Proton version: Experimental (2021-09-19)

I confirm:

• [x] that I have checked whether there are updates for my system available.

Symptoms

Game crashes immediately after starting and the hades bug reporter is shown:

Proton log: steam-1145360.log

Reproduction

1. nintendo pro controller is plugged in
2. "Switch Pro Configuration Support" is enabled in the steam controller settings
3. Start the game
4. Choose Direct X

Someone on protondb.com has already pointed out this issue (username Cook Cannibal): https://www.protondb.com/app/1145360#FbEylO57_k
I first experienced the issue around the same time as he did.

Some more information on when exactly the problem is / is not occurring:

• Un-checking "Switch Pro Configuration Support" seems to fix the problem.
• The issue only occurs with the switch pro controller. Using keyboard/mouse or another cheap USB controller that I had laying around does not cause the crash.
• I also reproduced the issue when choosing Vulkan on startup. In this case I had to launch the game through big picture mode to get the game to recognize the controller - after that the result was again the hades bug reporter.

Crashing with the Vulkan renderer option, but Dx11 seems to work fine. I don't have a controller installed, nor connected. Game window is black, the sounds play, but get presented with the Hades - Bug Reporter.

Tried Experimental, 6.3-7, and 6.8-GE-2.

Steam Runtime, Arch Linux, AMD 5700XT, mesa-git.

steam-1145360.log

sys-info

but get presented with the Hades - Bug Reporter.

@HanFox Could you paste the contents of the Bug Reporter here?

@HanFox Could you paste the contents of the Bug Reporter here?

@sobajic Sure:

By clicking Submit, you agree to send Supergiant Games this information, your current save data, and the screenshot above.This information will only be used for investigating the reported bug.

Version: Release 38239
Renderer: Vk AMD RADV NAVI10 (vendor id: 0x1002   model id: 0x731f   rev: 0x00)
OS: Microsoft Windows NT 10.0.17763.0
RAM: 32045
Cores: 16
64-bit: True
Region: en-GB


FATAL EXCEPTION at 0x0000000000D4F378
Violation when reading address 0x3
Code: 0xc0000005

ExceptionStack Trace:
 at EntryPoint (0x000000007b039800)
 at EntryPoint (0x000000007bc68380)
 at EntryPoint (0x000000007bc68380)
 at EntryPoint (0x000000007bc68380)
 at EntryPoint (0x000000007bc68380)
 at EntryPoint (0x000000007bc68380)
 at sgg::ForgeRenderer::CmdRecord_BeginFrame (0x0000000000d4ec90)
 at sgg::renderThread (0x0000000000eb8440)
 at sgg::WorkerManager::ExecuteCmd (0x0000000000d23150)
 at taskThreadFunc (0x0000000000e3b930)
 at ThreadFunctionStatic (0x0000000000e45790)
 at EntryPoint (0x000000007b632160)
 at EntryPoint (0x000000007bc68380)
 at 0x0000000000000000
 at ThreadFunctionStatic (0x0000000000e45790)
 at 0x0000000000432860
 at 0x0000000000000000
RAM usage: 32% (~21 GB available or 22730010624 bytes)

Crashing with the Vulkan renderer option, but Dx11 seems to work fine. I don't have a controller installed, nor connected. Game window is black, the sounds play, but get presented with the Hades - Bug Reporter.

Tried Experimental, 6.3-7, and 6.8-GE-2.

Steam Runtime, Arch Linux, AMD 5700XT, mesa-git.

steam-1145360.log

sys-info

Very interesting that you're seeing this on AMD. I've had it intermittently since their Vulkan renderer launched on Nvidia, thought it was only an Nvidia issue. Are you using Gnome/Mutter also?

Also: The Vulkan renderer was confirmed to have some serious bugs by an Nvidia engineer over in the Gnome Mutter gitlab when I reported it there, there's a lot of problems on SuperGiant's side that might never be fixed, so probably best to just use DX11 w/ DXVK.

Edit: Oh, didn't notice @sobajic here was from SuperGiant - here's a link to the Nvidia Engineer's comments on what was causing some of the black screen issues with the Vk renderer: https://gitlab.gnome.org/GNOME/mutter/-/issues/1522#note_1196102

@Vash63 I'm on KDE / Wayland. I didn't used to crash on KDE / X11. I could flip back, but as sobajic didn't ask about that particular thing I'm not sure that's the issue. I'll try if requested.

I also tried in gamescope, as I'm under the impression that dodges(?) the native compositor (I could be wrong, the things Valve are doing are beyond me, lol). Vulkan crashes there, too.

@Vash63 haha, thanks, just wanted to ask for the thread so we can look into it 😀

@HanFox I've never used Wayland unfortunately, so I'm not familiar with what could be causing issues

Thanks for migrating the issue for me! I want to emphasize that a game not
working in proton is a bummer but not a huge deal for me. What makes this
issue so bad is that it fails such that the steam interface becomes locked
up.

On Sun, Oct 31, 2021, 5:37 AM kisak-valve @.***> wrote:

Starting a specific game seems to break overlay / all UI

Issue transferred from ValveSoftware/steam-for-linux#8197
https://github.com/ValveSoftware/steam-for-linux/issues/8197.
@frioux https://github.com/frioux posted on 2021-10-31T06:01:27:
Your system information

• Steam client version (build number or date): Oct 13 2021, at 19:47:28
• Distribution (e.g. Ubuntu): Ubuntu 20.04
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Tried to start Hades with many different SteamPlay versions (Experimental,
6.3-7, a couple glorious eggroll versions) and many different launch modes
(Vulkan, DX, 32 bit) and I always get either what seems like a total
interface lockup or (preferably!) a game crash.

I even upgraded from 460 nvidia drivers to 495, and still see the same
issue.

Once this occurs the big picture button on the controller no longer seems
to do anything and it's as if the screen is off. I end up ssh'ing into it
to reboot it.
Steps for reproducing this issue:

1. Try to start Hades?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3312#issuecomment-955692610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB7Y5MCWX4DZT73VLWBZDUJU2A3ANCNFSM4JZMZUAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

After a game update that's happened in the recent days, now Hades with Proton 6.3-7 and also Experimental shows Xbox button prompts when using the DualSense controller.

BTW I was able to resolve my issue by starting the game from a real window manager instead of full-on steamos style big picture mode. Normally I use steamcompmgr, which is somehow incompatible for this game for me 🤷🏻

@NyaomiDEV said:

After a game update that's happened in the recent days, now Hades with Proton 6.3-7 and also Experimental shows Xbox button prompts when using the DualSense controller.

Hi. I've looked into it as I've fixed the prompts for the DS4 controllers in Hades some time ago. This is no a Proton bug, the game also displays xbox prompts on Windows.

System Information

• GPU: GTX 1060
• Driver/LLVM version: nvidia 495.44
• Kernel version: 5.15.6-arch2-1
• Link to full system information report as Gist:
• Proton version: 5.13.6

I confirm:

• [x] that I have checked whether there are updates for my system available.

Symptoms

Launching the game using any option causes a black screen alongside this report

Launching with proton 6.3.8 causes it to crash without ever showing anything.
The game works perfectly when launched with Wine with base configuration.
I don't have any controllers plugged in and don't have a compositor either.

steam-1145360.log

Reproduction

Launch the game

That's good to know,
here's the log for proton 6.3-8
Vulkan: steam-1145360.log
Directx: steam-1145360.log

Thanks !

I uninstalled and reinstalled Proton 6.3, it works now !
Weirdly enough room transition are up to 5x slower than with Wine, even though Proton and Wine are installed in the same partition. Apart from that everything works flawlessly.

Thank you so much !

Replying to https://github.com/ValveSoftware/Proton/issues/3312#issuecomment-937612420

Vulkan works fine with in-game Vsync on, but if it's off the game crashes both on AMD RX580 and Intel A770. I tried to lock my FPS with mangohud, but that didn't help.

Since this game is steam deck verified I thought the game could be played from start to finish however there is a game breaking bug that causes a freeze at almost the end of the game that's stopping me from making any further progress

log:
steam-1145360.log

system info:
Computer Information.txt

the video of it happening:
https://user-images.githubusercontent.com/37030489/229025699-57aca41b-5f1e-42d3-af78-f87583b293aa.mp4

my save file to reproduce this bug
(the "Hades" folder should be placed in this directory $SteamLibrary/steamapps/compatdata/1145360/pfx/drive_c/users/steamuser/My Documents/Saved Games/):
Hades.zip

Replying to https://github.com/ValveSoftware/Proton/issues/3312#issuecomment-1491295501

and i found a workaround
PROTON_NO_FSYNC=1