Game Crashing my GPU on the same spot - .Appimage (Linux) RX 6700 XT #2408

Closed

opened 2026-11-11 17:48:54 +00:00 by mjnko1988 · 2 comments

mjnko1988 commented

2026-11-11 17:48:54 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

Tried it three times - game kept crashing on the same spot after the pre-rendered cutscene - Great Deku Tree orders Navi to fetch Link, Navi flies away towards Link's House - as soon as it pans on Saria while holding Link's Ocarina - instant crash of my GPU.

I've seen this issue on early builds of Lichii/Eglantine but now its been alright for me.

Where in the game

After First Pre-rendered Cutscene - Navi flies towards Link's house, camera shows Saria

How often

Every time

Graphics card and driver version

RX 6700 XT, MESA 26.2.6-arch3.1

CPU, RAM and operating system

Ryzen 5 5600, 16GB, CachyOS

Changes from the defaults

quality_preset=0
fullscreen=1
gpu_device=1
frame_generation=1
frame_pacing=0
hdr=0
hdr_paper_white=200
hdr_peak_brightness=1000
frame_rate_cap=0
nvidia_reflex=0
amd_anti-lag_2=0
output_res=1920x1080
dlss=0
dlss_model=0
resolution=0
upscaling=0
sharpness=20
anisotropic_filtering=4
handheld_profile=0
ultrawide=0
ultrawide_menus=1
robust_buffers=0
mesh_shaders=0
volume=100
mute_in_background=0
audio_output=0
fps_counter=1
menu_size=2
game_speed=1
text_speed=0
text_size=0
microphone=1
discord_status=1
controller_in_background=0
mouse_camera=0
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_camera_x=0
invert_camera_y=0
stick_dead_zone=0
rumble_strength=100
motion_controls=1
motion_sensitivity_x=100
motion_sensitivity_y=100
invert_motion_x=0
invert_motion_y=0
motion_deadzone=1
layout_preset=0
button_prompts=0
menu_shortcut=0
debug_tools=0
descriptor_reuse=1
sampler_cache=0
options_version=4
pad_a=1
key_a=69,0
pad_b=0
key_b=16,0
pad_x=3
key_x=32,0
pad_y=2
key_y=1,0
pad_ls=7
key_ls=17,0
pad_rs=8
key_rs=67,0
pad_l=9
key_l=81,0
pad_r=10
key_r=82,0
pad_zl=15
key_zl=90,2
pad_zr=16
key_zr=88,70
pad_plus=6
key_plus=9,13
pad_minus=4
key_minus=77,0
pad_left=13
key_left=49,0
pad_up=11
key_up=50,0
pad_right=14
key_right=51,0
pad_down=12
key_down=52,0
key_move_up=87,0
key_move_down=83,0
key_move_left=65,0
key_move_right=68,0
key_cam_up=38,73
key_cam_down=40,75
key_cam_left=37,74
key_cam_right=39,76

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log.1.txt

hookshot_log.2.txt

hookshot_log.3.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 Tried it three times - game kept crashing on the same spot after the pre-rendered cutscene - Great Deku Tree orders Navi to fetch Link, Navi flies away towards Link's House - as soon as it pans on Saria while holding Link's Ocarina - instant crash of my GPU. I've seen this issue on early builds of Lichii/Eglantine but now its been alright for me. ### Where in the game After First Pre-rendered Cutscene - Navi flies towards Link's house, camera shows Saria ### How often Every time ### Graphics card and driver version RX 6700 XT, MESA 26.2.6-arch3.1 ### CPU, RAM and operating system Ryzen 5 5600, 16GB, CachyOS ### Changes from the defaults quality_preset=0 fullscreen=1 gpu_device=1 frame_generation=1 frame_pacing=0 hdr=0 hdr_paper_white=200 hdr_peak_brightness=1000 frame_rate_cap=0 nvidia_reflex=0 amd_anti-lag_2=0 output_res=1920x1080 dlss=0 dlss_model=0 resolution=0 upscaling=0 sharpness=20 anisotropic_filtering=4 handheld_profile=0 ultrawide=0 ultrawide_menus=1 robust_buffers=0 mesh_shaders=0 volume=100 mute_in_background=0 audio_output=0 fps_counter=1 menu_size=2 game_speed=1 text_speed=0 text_size=0 microphone=1 discord_status=1 controller_in_background=0 mouse_camera=0 disable_camera_centering=0 mouse_sensitivity=100 invert_mouse_vertical=0 invert_camera_x=0 invert_camera_y=0 stick_dead_zone=0 rumble_strength=100 motion_controls=1 motion_sensitivity_x=100 motion_sensitivity_y=100 invert_motion_x=0 invert_motion_y=0 motion_deadzone=1 layout_preset=0 button_prompts=0 menu_shortcut=0 debug_tools=0 descriptor_reuse=1 sampler_cache=0 options_version=4 pad_a=1 key_a=69,0 pad_b=0 key_b=16,0 pad_x=3 key_x=32,0 pad_y=2 key_y=1,0 pad_ls=7 key_ls=17,0 pad_rs=8 key_rs=67,0 pad_l=9 key_l=81,0 pad_r=10 key_r=82,0 pad_zl=15 key_zl=90,2 pad_zr=16 key_zr=88,70 pad_plus=6 key_plus=9,13 pad_minus=4 key_minus=77,0 pad_left=13 key_left=49,0 pad_up=11 key_up=50,0 pad_right=14 key_right=51,0 pad_down=12 key_down=52,0 key_move_up=87,0 key_move_down=83,0 key_move_left=65,0 key_move_right=68,0 key_cam_up=38,73 key_cam_down=40,75 key_cam_left=37,74 key_cam_right=39,76 ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34699374/hookshot_log.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34699380/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34699591/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34699382/hookshot_log.3.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.

source-gitfox commented

2026-11-11 18:38:23 +00:00

(Migrated from github.com)

I'm on Steamdeck, game crashes when it pans out from Links house after he woke up. V2.1.0 still

NotRexed commented

2026-11-11 21:30:07 +00:00

(Migrated from github.com)

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

Commenting is not possible because the repository is archived.