Open gfbett opened 4 years ago
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.
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.
Launch the game
Hello @SanderJSA, err:steamclient:create_win_interface Don't recognize interface name: SteamController008
looks like a line of interest from your log. This looks like its part of Steamworks 1.51, which is provided by Proton 6.3-1 and newer. Proton 5.13 is now too old to use with the game.
Please share a log of the crash you're seeing with Proton 6.3.
That's good to know, here's the log for proton 6.3-8 Vulkan: steam-1145360.log Directx: steam-1145360.log
Thanks !
From those logs, err:module:process_init failed to load L"C:\\windows\\system32\\explorer.exe", error 4000000e
looks like the game's wineprefix or Proton 6.3 install is damaged or incomplete. Please verify the integrity of Proton's files in Steam.
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 !
Tracking note: Dropping the AMD RADV label because it needs a stronger hint that there's a driver-specific issue to investigate this game, possibly a general game issue.
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
Problem mods in hades
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7258. @SecondMaker posted on 2023-11-14T03:41:15:
Hades crash when i load it with the OlympusExtra Mod i have the complete log of the game here:
date time [thread name/id ] file:line v | 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:436 INFO| Start reading manifest OEHera 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:489 INFO| Done reading manifest OEHera 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:436 INFO| Start reading manifest OEHestia 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:489 INFO| Done reading manifest OEHestia 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:515 INFO| Loading package: OEHera.pkg 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:545 INFO| Package Loaded: OEHera 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:515 INFO| Loading package: OEHestia.pkg 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:545 INFO| Package Loaded: OEHestia 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:436 INFO| Start reading manifest OEApollo 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:489 INFO| Done reading manifest OEApollo 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:515 INFO| Loading package: OEApollo.pkg 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:545 INFO| Package Loaded: OEApollo 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:436 INFO| Start reading manifest OEMinor 2023-11-13 22:36:35 [NoName ] gameassetmanager.cpp:489 INFO| Done reading manifest OEMinor 2023-11-13 22:36:35 [GameAssetManagerLoadThread] gameassetmanager.cpp:515 INFO| Loading package: OEMinor.pkg 2023-11-13 22:36:35 [NoName ] world.cpp:1433 DBG| Finished PostLaod 2023-11-13 22:36:35 [RenderThread ] vulkan.cpp:1052 ERR| [../src/intel/vulkan_hasvk/anv_device.c:3253] : VK_ERROR_OUT_OF_DEVICE_MEMORY (0) 2023-11-13 22:36:35 [RenderThread ] vulkan.cpp:1052 ERR| [../src/intel/vulkan_hasvk/anv_device.c:3253] : VK_ERROR_OUT_OF_DEVICE_MEMORY (0) 2023-11-13 22:36:35 [RenderThread ] vulkan.cpp:3613 ERR| vmaCreateBuffer(pRenderer->pVmaAllocator, &add_info, &vma_mem_reqs, &pBuffer->pVkBuffer, &pBuffer->pVkAllocation, &alloc_info): FAILED with VkResult: -2 2023-11-13 22:36:35 [RenderThread ] program.cpp:659 INFO| Error {0} Success 2023-11-13 22:36:35 [RenderThread ] program.cpp:678 INFO| Total RAM on host machine: 15661 MB 2023-11-13 22:36:35 [RenderThread ] program.cpp:679 INFO| Total RAM in use on host machine: 68 percent 2023-11-13 22:36:35 [RenderThread ] program.cpp:683 INFO| Total RAM in use by this application: 1741 MB 2023-11-13 22:36:35 [RenderThread ] program.cpp:687 INFO| Total TextureMemory in use by this application: 1238 MB 2023-11-13 22:36:36 [MainThread ] program.cpp:369 INFO| Window Inactive 2023-11-13 22:36:38 [MainThread ] program.cpp:352 INFO| Window Active 2023-11-13 22:36:38 [MainThread ] program.cpp:352 INFO| Window Active Stack Trace: at 0x000000007b066869 at 0x00000001700427a6 at 0x0000000170042538 at 0x000000017000ef74 at 0x000000017004212c at 0x0000000170044959 at 0x000000017000efce at 0x000000018000c387 2023-11-13 22:36:40 [MainThread ] program.cpp:369 INFO| Window Inactive 2023-11-13 22:36:42 [MainThread ] program.cpp:352 INFO| Window Active 2023-11-13 22:36:42 [MainThread ] program.cpp:352 INFO| Window Active 2023-11-13 22:36:43 [MainThread ] program.cpp:369 INFO| Window Inactive 2023-11-13 22:36:44 [MainThread ] program.cpp:352 INFO| Window Active 2023-11-13 22:36:44 [MainThread ] program.cpp:352 INFO| Window Active 2023-11-13 22:36:45 [MainThread ] program.cpp:369 INFO| Window Inactive
I have 15gb ram but for some reason proton only uses 2 for the game, resulting in a frezze and crash, is there a way to manually allocate more memory for the game so it can load the extra features of the mod. I must clarify that it only happens when the run start. I can be on the house of hades normally without problem but at the moment of startun the run it breaks.
Cloud saves don't work for Hades
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/10910. @ASHGOLDOFFICIAL posted on 2024-05-19T14:33:40:
Cloud saves for Hades do not work. It always says "Up to date" but storage is empty. I discovered it after reinstall.
Compatibility Report
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:
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