Hades II
This is not really a fix but to anyone want to play the game while waiting for a fix here is my gamescope launch options to play the game normally:
gamescope -f -b -w 1920 -h 1080 -W 1920 -H 1080 -- env VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_wait DRI_PRIME=1 %command%
Stutter in Hades II
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8424.
@peniblec posted on 2025-01-27T22:11:46:
Compatibility Report
- Name of the game with compatibility issues: Hades II
- Steam AppID of the game: 1145350
System Information
- GPU:
AMD Radeon Graphics (RADV RENOIR)- (iGPU; CPU:
AMD Ryzen 5 PRO 4650G with Radeon Graphics)
- (iGPU; CPU:
- Video driver version:
4.6 (Compatibility Profile) Mesa 24.3.4 - Kernel version:
6.13.0 - Link to full system information report as Gist:
- https://gist.github.com/peniblec/4167783a31daca0a87517a39f99d8881
- gists do not seem to have TOCs, so direct links to specifc sub-sections for convenience:
- Proton version:
1737504144 experimental-9.0-20250121
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.
Attached PROTON_LOG=1: steam-1145350.log
Symptoms
Framerate oscillates at about 40±10 FPS in a sawtooth pattern; this correlates with game animation looking stuttery. When the framerate settles (either at 30 or 60 FPS), game animation looks smooth again.
Reproduction
In the game's hub rooms (Crossroads, Training Grounds), framerate stays at a smooth 60 while running around the edges of the rooms; moving toward the center of the rooms, the symptoms begin.
(Have not attempted a run since I have noticed this issue, so cannot say if this affects every area)
Closing notes
Regarding:
I confirm: - [x] that I haven't found an existing compatibility report for this game.
To be more precise:
- The game is ranked platinum on protondb.
- It seems well-earned: I personally sank 100h into the game, and never noticed any issue.
- Then I took a "forced break" from the game from November 19 to 28, due to a failing SSD bringing my system down.
- Symptoms began after system reinstallation.
- Since then, I have:
- tweaked in-game knobs ("low/medium/high" graphics, resolution, vsync, full/windowed)
- changed Proton versions
- switched from Wayland to X11
- enabled CPPC in UEFI settings, which let amd_pstate initialize and drive the CPU
- poked at sysfs tunables mentioned in fdo:drm/amd#1500
- checked whether VRR could be involved (
kscreen-doctorsays:Vrr: incapable) - started the game with
LD_PRELOAD= %command%, (as suggested in other ValveSoftware GH issues, to work around a recent regression from the game recording update IIUC) - changed the Plasma Renderer to Software to free up some VRAM
- None of the above (each tested on its own then reverted) had any effect on the symptoms.
- I have not:
- bisected any element of the distro stack (kernel, drivers, Mesa, Plasma): I would like to exhaust other "first principles"/"observation-based" methods before going down that road and introducing more bugs from incomplete (de|re)ⁿinstallations.
I worked up the nerve to file an issue here after trying a PROTON_LOG=1 %command% run: the 40s session generated 4MB's worth of trace:unwind:dump_unwind_info. I guess at this stage, I'm mostly after an informed opinion on these specifc logs: is the volume a red herring or a smoking gun?
Thoughts on the symptoms themselves also welcome, though apologies for vagueness in that regard. If that helps, I posted mangohud captures in fdo:mesa/mesa#11300.
I have Hades II (EGS version via Heroic) installed on my Steam Deck. The problem is: there is no rumble when launched from Game Mode, but rumble works when running from Desktop Mode (both from Steam or Heroic). Other games installed this way work just fine
UPD.: fixed by Hades 2 developers
When launching the game with Proton 10 beta or newer, I am getting an "Unrecognized Controller" error on my MSI Claw, which is presented as a Steam Controller via InputPlumber.
This error does not error on Proton 9.
@matte-schwartz Could you get a log with some additional logging channels? I don't have a MSI Claw to test directly, so I'm hoping we can figure out the problem remotely :) Also - very cool that you are running Proton/Linux on there :D
To start with, could you get a log with PROTON_LOG=+hid,+dinput,+xinput,+rawinput,+input,+wbemprox,+setupapi %command% ?
@alasky17 attaching a proton 9 log with no pop-up and proton 10 with the unknown controller pop-up
@matte-schwartz There doesn't seem to be anything specifically wrong in these logs, but we've changed the way the Steam Input controller is being exposed to applications in Proton 10, in order to improve compatibility with some Windows libraries, such as SDL, which have added specific support for Steam Input devices.
I'm not sure to understand what you mean by "presented as a Steam Controller via InputPlumber", if this is done at a lower level for Steam Input to take it over and handle the rest of the device virtualisation from there, or just presenting the device as a VID = 28de / PID = 11ff HID device to Proton.
In the latter case, as the game uses SDL, it's possible that it gets confused: when a Steam Input virtual controller is being detected, the library will try to lookup a separate file from a [SteamVirtualGamepadInfo](https://github.com/libsdl-org/SDL/blob/main/src/joystick/SDL_steam_virtual_gamepad.c) (and/or SteamVirtualGamepadInfo_Proton environment variable when running with Proton), to load the actual underlying device VID/PID and other properties from it, in order for instance to display the proper in-game glyphs.
This file is normally setup by Steam Input before launching the game, and maybe it's lacking for some reason in your case? You may check whether the file is present while the game is running, it's usually located at $HOME/.local/share/Steam/config/virtualgamepadinfo.txt, and you should see the environment variable with cat /proc/<pid>/environ |xargs -0 -n1|grep Gamepad with the PID of the game running. You will perhaps need to create this file, or it might be better to emulate an XBox controller VID/PID instead.
Sorry, saying it's presented as a Steam Controller was slightly inaccurate of me so I'll explain a bit further.
InputPlumber basically grabs source devices and then combines them into one target device which Steam Input can then grab and use. For handhelds on SteamOS, a Steam Deck target is used and then the Steam client recognizes that and shows a slightly different input scheme: https://github.com/ShadowBlip/InputPlumber/blob/bae539dc5fb6606b8e7324490d53e6c91391e6f0/src/input/target/steam_deck.rs#L52-L61
$HOME/.local/share/Steam/config/virtualgamepadinfo.txt does exist:
[Slot 0]
name=SteamOS Handheld Controller
VID=0x28de
PID=0x12f0
handle=0x000000000000000aa
type=unknown
emulating an Xbox controller does not show the error, but the problem with this approach is that we'd need to reevaluate both Steam client behavior and steamos-manager behavior, as steamos-manager is what sets the target device:
I don't have my Legion Go S with me at the moment, but I would not be surprised if that presents the same issue as it uses the same target that the MSI Claw is using.
I should also note the controller still seems to work fine in-game, it's just the pop-up warning that counts as the regression here.
Was able to confirm the same warning does appear on my Legion Go S running SteamOS now that I'm home
Same issue here, after 5 to 30 minutes, my game screen freezes and sound works fine.
Tested every Proton version and ChatGPT launch param brainstorm, but the issue persists.
My laptop is i5-13420H, RTX 3050, 16GB, Ubuntu 22.04.
I also noticed that after game freeze, my GPU goes to 0% usage, but VRAM locks in 3.36GB
Hey guys, I came with a solution to my freezing.
When the game freezes visually, the process is still running (audio works, VRAM stays allocated). Alt-tabbing sometimes makes the image update slightly, which pointed me to the compositor rather than the game.
Workaround (after your game freezes, and without closing the game):
- Press Ctrl + Alt + F3 to switch to a TTY. You should stop hearing the game.
- Press Ctrl + Alt + F4, login on your accout. You should hear Hades II application.
- Press Ctrl + Alt + F2 to return to your GNOME Desktop, the game should unfreeze.
Sometimes I had to repeat this process a few times (up to ~4), but it always worked in the end.
I can reproduce this every time, and this workaround consistently fixes the freeze. In my case, this strongly suggests an issue with GNOME + NVIDIA + Vulkan, not Proton itself.
Launch options
PROTON_LOG=+hid,+dinput,+xinput,+rawinput,+input,+wbemprox,+setupapix1 2025-10PROTON_LOG=1x1 2025-01PROTON_LOG=1`:x1 2025-01VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_waitx1 2024-06DXVK_FILTER_DEVICE_NAME="3050"x1 2024-06
Launch lines
Upstream links
- ValveSoftware/Proton/issues/8424x1 2025-01
Compatibility Report
System Information
I confirm:
Logs: steam-1145350.zip
Symptoms
Game freezes at the moment when I press alt tab and crashes after few seconds. Not in the game menu, only in actual gameplay.
Reproduction
0- Game needs to be run with this param to detect dgpu: DXVK_FILTER_DEVICE_NAME="3050"
1- Run game with Nvidia Gpu on Wayland.
2- Start game.
3- Press alt+tab.