Crash after intro #2521

Closed
opened 2026-11-11 21:48:10 +00:00 by Elroy1995 · 9 comments
Elroy1995 commented 2026-11-11 21:48:10 +00:00 (Migrated from github.com)

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'm on the newest release, or the problem is still there on it.
  • I searched the open issues for this problem.
  • I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
### 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](https://github.com/user-attachments/files/34712332/hookshot_log4.txt) ### Screenshots or video _No response_ ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
AMonreale commented 2026-11-11 21:55:34 +00:00 (Migrated from github.com)

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

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".
Elroy1995 commented 2026-11-11 21:58:20 +00:00 (Migrated from github.com)

How would I access game menu on steamdeck?

How would I access game menu on steamdeck?
AMonreale commented 2026-11-11 22:03:01 +00:00 (Migrated from github.com)

How would I access game menu on steamdeck?

Press Select and Start together (or whatever they are called on Steam Deck).

> How would I access game menu on steamdeck? Press Select and Start together (or whatever they are called on Steam Deck).
Elroy1995 commented 2026-11-11 22:10:37 +00:00 (Migrated from github.com)

Made the change but issue still occurred unfortunately :(

Made the change but issue still occurred unfortunately :(
AMonreale commented 2026-11-11 22:28:34 +00:00 (Migrated from github.com)

Try to set "Compute" under the "Mesh shaders" option. It will trigger a shader recompilation, so it may take a while.

Try to set "Compute" under the "Mesh shaders" option. It will trigger a shader recompilation, so it may take a while.
thiDucTran commented 2026-11-11 22:29:16 +00:00 (Migrated from github.com)

same symtom..here's my log

           .;looooooooc  .oooooooooo'          OS: Ubuntu 26.04.1 LTS (Resolute Raccoon) x86_64
        .;looooool:,''.  :ooooooooooc          Host: A6
       ;looool;.         'oooooooooo,          Kernel: Linux 7.3.3-1-liquorix-amd64
      ;clool'             .cooooooc.  ,,       Uptime: 23 hours, 31 mins
         ...                ......  .:oo,      Packages: 1965 (dpkg), 19 (flatpak-system), 1 (flatpak-user), 24 (snap)
  .;clol:,.                        .loooo'     Shell: bash 5.3.9
 :ooooooooo,                        'ooool     Display (LG Electronics 22"): 1920x1080 in 22", 60 Hz [External]
'ooooooooooo.                        loooo.    DE: GNOME 50.1
'ooooooooool                         coooo.    WM: Mutter (Wayland)
 ,loooooooc.                        .loooo.    WM Theme: Yaru-dark
   .,;;;'.                          ;ooooc     Theme: Yaru-dark [GTK2/3/4]
       ...                         ,ooool.     Icons: Yaru-dark [GTK2/3/4]
    .cooooc.              ..',,'.  .cooo.      Font: Ubuntu Sans (11pt) [GTK2/3/4]
      ;ooooo:.           ;oooooooc.  :l.       Cursor: Yaru (24px)
       .coooooc,..      coooooooooo.           Terminal: GNOME Terminal 3.58.0
         .:ooooooolc:. .ooooooooooo'           Terminal Font: Ubuntu Sans Mono (11pt)
           .':loooooo;  ,oooooooooc            CPU: AMD Ryzen 7 6800H (16) @ 4.79 GHz
               ..';::c'  .;loooo:'             GPU: AMD Radeon 680M [Integrated]

log.txt

same symtom..here's my log ``` .;looooooooc .oooooooooo' OS: Ubuntu 26.04.1 LTS (Resolute Raccoon) x86_64 .;looooool:,''. :ooooooooooc Host: A6 ;looool;. 'oooooooooo, Kernel: Linux 7.3.3-1-liquorix-amd64 ;clool' .cooooooc. ,, Uptime: 23 hours, 31 mins ... ...... .:oo, Packages: 1965 (dpkg), 19 (flatpak-system), 1 (flatpak-user), 24 (snap) .;clol:,. .loooo' Shell: bash 5.3.9 :ooooooooo, 'ooool Display (LG Electronics 22"): 1920x1080 in 22", 60 Hz [External] 'ooooooooooo. loooo. DE: GNOME 50.1 'ooooooooool coooo. WM: Mutter (Wayland) ,loooooooc. .loooo. WM Theme: Yaru-dark .,;;;'. ;ooooc Theme: Yaru-dark [GTK2/3/4] ... ,ooool. Icons: Yaru-dark [GTK2/3/4] .cooooc. ..',,'. .cooo. Font: Ubuntu Sans (11pt) [GTK2/3/4] ;ooooo:. ;oooooooc. :l. Cursor: Yaru (24px) .coooooc,.. coooooooooo. Terminal: GNOME Terminal 3.58.0 .:ooooooolc:. .ooooooooooo' Terminal Font: Ubuntu Sans Mono (11pt) .':loooooo; ,oooooooooc CPU: AMD Ryzen 7 6800H (16) @ 4.79 GHz ..';::c' .;loooo:' GPU: AMD Radeon 680M [Integrated] ``` [log.txt](https://github.com/user-attachments/files/34718628/log.txt)
Elroy1995 commented 2026-11-11 22:36:45 +00:00 (Migrated from github.com)

Doing the compute now will let you know what happens!

Doing the compute now will let you know what happens!
NotRexed commented 2026-11-12 03:07:33 +00:00 (Migrated from github.com)

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

@mooki000 commented on GitHub · 2026-11-12 12:45 UTC · original

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 amdgpu timeout/reset messages; the two cases remain separate within #1000.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:45 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2521#issuecomment-6823984560) 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 `amdgpu` timeout/reset messages; the two cases remain separate within #1000. <!-- github-sync:c:6823984560 -->
Commenting is not possible because the repository is archived.
No milestone
No assignees
2 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2521
No description provided.