CRASH-rx 6600 kokori village & zora river #2611

Closed

opened 2026-11-12 01:57:02 +00:00 by vault-dweller111 · 3 comments

vault-dweller111 commented

2026-11-12 01:57:02 +00:00

(Migrated from github.com)

Hookshot version

2.1.0

What kind of problem

Crash, freeze or black screen

What happened

When I get near Zora's River and Kokiri Village in Hyrule Field, the game crashes; sometimes I can enter the area, but as soon as I attack an enemy, the game crashes.

Where in the game

hyrule fields close to zara river and kokori forest

How often

Every time

Graphics card and driver version

rx 6600 26.10.1 WHQL

CPU, RAM and operating system

ryzen 5500 16gb ram 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 2.1.0 ### What kind of problem Crash, freeze or black screen ### What happened When I get near Zora's River and Kokiri Village in Hyrule Field, the game crashes; sometimes I can enter the area, but as soon as I attack an enemy, the game crashes. ### Where in the game hyrule fields close to zara river and kokori forest ### How often Every time ### Graphics card and driver version rx 6600 26.10.1 WHQL ### CPU, RAM and operating system ryzen 5500 16gb ram 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/34722986/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.

felipemeamaral commented

2026-11-12 02:31:35 +00:00

(Migrated from github.com)

@vault-dweller111 I was having the same issues and after changing my settings onto hookshot_options.ini to this is fixed the crashes, frame pacing and the game is running flawlessly on my RX 6600:

quality_preset=0
fullscreen=1
gpu_device=0
frame_generation=2
frame_pacing=0
frame_rate_cap=0
amd_anti-lag_2=1
output_res=1920x1080
resolution=1
upscaling=0
sharpness=30
anisotropic_filtering=0
handheld_profile=0
robust_buffers=0
mesh_shaders=2
debug_tools=1
descriptor_reuse=1
sampler_cache=1
options_version=4

@vault-dweller111 I was having the same issues and after changing my settings onto `hookshot_options.ini` to this is fixed the crashes, frame pacing and the game is running flawlessly on my RX 6600: ``` quality_preset=0 fullscreen=1 gpu_device=0 frame_generation=2 frame_pacing=0 frame_rate_cap=0 amd_anti-lag_2=1 output_res=1920x1080 resolution=1 upscaling=0 sharpness=30 anisotropic_filtering=0 handheld_profile=0 robust_buffers=0 mesh_shaders=2 debug_tools=1 descriptor_reuse=1 sampler_cache=1 options_version=4 ```

NotRexed commented

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

(Migrated from github.com)

Thanks for the report. Reports of the same kind are collected in #996, which lists this one with your details and links back here, so one fix closes them together. Follow #996 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. Your log records GPU device loss on the native mesh path, but no GPU checkpoints that identify the stalled work. The settings suggested above change several things together, so they do not yet identify which change helped.

If you try the same entrance again, please change only Mesh shaders → Compute, restart when prompted, and keep the other settings unchanged. Please post the result and settings; if it still fails and you are comfortable capturing it, RX_VK_CHECKPOINTS=1 would add useful markers. This is a diagnostic comparison, not a confirmed RX 6600 fix.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:46 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2611#issuecomment-6823987838) Thanks. Your log records GPU device loss on the native mesh path, but no GPU checkpoints that identify the stalled work. The settings suggested above change several things together, so they do not yet identify which change helped. If you try the same entrance again, please change only **Mesh shaders → Compute**, restart when prompted, and keep the other settings unchanged. Please post the result and settings; if it still fails and you are comfortable capturing it, `RX_VK_CHECKPOINTS=1` would add useful markers. This is a diagnostic comparison, not a confirmed RX 6600 fix.

Commenting is not possible because the repository is archived.