Game crash after first cutscene #2612

Closed

opened 2026-11-12 02:08:45 +00:00 by hudsonrockes · 4 comments

hudsonrockes commented

2026-11-12 02:08:45 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

immediate crash after first cutscene ends other wise the cutscene is fine

Where in the game

After First cutscene

How often

Every time

Graphics card and driver version

Intel B580 32.0.101.9175

CPU, RAM and operating system

Ryzen 5 7600x, Windows 11

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.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 Crash, freeze or black screen ### What happened immediate crash after first cutscene ends other wise the cutscene is fine ### Where in the game After First cutscene ### How often Every time ### Graphics card and driver version Intel B580 32.0.101.9175 ### CPU, RAM and operating system Ryzen 5 7600x, Windows 11 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34723205/hookshot_log.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.

Oliverwwemi commented

2026-11-12 02:17:08 +00:00

(Migrated from github.com)

i'm experiencing the exact same error in Hookshot v2.1.0: the game crashes after the first cutscene. In the previous version, it would get about halfway through the second cutscene before crashing.

Codeguy21345 commented

2026-11-12 02:42:11 +00:00

(Migrated from github.com)

i shall note this is for general gameplay as well

NotRexed commented

2026-11-12 03:08:37 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same kind are collected in #999, which lists this one with your details and links back here, so one fix closes them together. Follow #999 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.

github-sync commented

2026-11-12 13:40:06 +00:00

Owner

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

Thanks for the log. Its device-loss checkpoints name 435a0138b9013040 and 592079442d7129da, the pair already recorded on B580 in #999; checkpoints identify work in flight, not necessarily the guilty shader. #2306 touches those passes, but its Intel native-add path remains untested and off by default, so it is not a confirmed fix here.

Could you add your RAM amount, graphics settings, whether loading an existing save also fails, and any Windows GPU-reset event from the same time? Your driver version and failed-run log are already supplied. @Oliverwwemi @Codeguy21345, please include your own GPU/driver, OS, build and failed-run log rather than assuming the same symptom has the same cause.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:46 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2612#issuecomment-6823988397) Thanks for the log. Its device-loss checkpoints name `435a0138b9013040` and `592079442d7129da`, the pair already recorded on B580 in #999; checkpoints identify work in flight, not necessarily the guilty shader. #2306 touches those passes, but its Intel native-add path remains untested and off by default, so it is not a confirmed fix here. Could you add your RAM amount, graphics settings, whether loading an existing save also fails, and any Windows GPU-reset event from the same time? Your driver version and failed-run log are already supplied. @Oliverwwemi @Codeguy21345, please include your own GPU/driver, OS, build and failed-run log rather than assuming the same symptom has the same cause.

Commenting is not possible because the repository is archived.