Crash after intro #2521
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2521
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hookshot version
v2.1.0
What kind of problem
Graphics (missing, black or wrong-coloured things, lighting, flicker)
What happened
On steamdeck as soon intro for game finishes game crashes
Where in the game
After intro
How often
Every time
Graphics card and driver version
AMD Custom GPU 0405
CPU, RAM and operating system
AMD Custom APU 0405
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log4.txt
Screenshots or video
No response
Before you send it
I think I managed to find a solution: enter the game menù and under "GPU Device" select your GPU, don't leave it in "Auto".
How would I access game menu on steamdeck?
Press Select and Start together (or whatever they are called on Steam Deck).
Made the change but issue still occurred unfortunately :(
Try to set "Compute" under the "Mesh shaders" option. It will trigger a shader recompilation, so it may take a while.
same symtom..here's my log
log.txt
Doing the compute now will let you know what happens!
Thanks for the report. Reports of the same kind are collected in #1000, which lists this one with your details and links back here, so one fix closes them together. Follow #1000 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.
Thanks for trying the GPU selection; I see it did not help. Did the Mesh shaders → Compute attempt you started finish, and what was the result? Please include that run's log and your SteamOS/distro and Mesa versions.
Main now includes #1965's RADV optimization change and #2362's Linux AMD Compute default, neither of which is in v2.1.0. Those are related fixes, not confirmation that your particular hang is resolved.
@thiDucTran, your separate 680M log explicitly records device loss, whereas the Deck log stops after capture timeouts without that report. Please add your RAM amount, graphics settings and any kernel
amdgputimeout/reset messages; the two cases remain separate within #1000.