Endless loading when entering the Great Deku Tree (RTX 3080 Ti, v2.0.13 and v2.0.14) #1807

Closed

opened 2026-11-10 17:16:30 +00:00 by NotRexed · 3 comments

NotRexed commented

2026-11-10 17:16:30 +00:00

(Migrated from github.com)

Reported on Discord (RTX 3080 Ti; happens on v2.0.13 and v2.0.14).

What happens: entering the Great Deku Tree, the loading screen never ends.

What would help: the log attached on Discord was from an earlier run, so please attach the hookshot_log.txt from a run where the loading hangs (it's beside hookshot.exe and is rewritten on each start; earlier runs are kept as hookshot_log.1.txt to .4.txt). Also: does it happen from a fresh save or only one save, and with frame generation and the Frame rate cap at their defaults?

Reported on Discord (RTX 3080 Ti; happens on v2.0.13 and v2.0.14). **What happens:** entering the Great Deku Tree, the loading screen never ends. **What would help:** the log attached on Discord was from an earlier run, so please attach the hookshot_log.txt from a run where the loading hangs (it's beside hookshot.exe and is rewritten on each start; earlier runs are kept as hookshot_log.1.txt to .4.txt). Also: does it happen from a fresh save or only one save, and with frame generation and the Frame rate cap at their defaults?

NotRexed commented

2026-11-10 20:45:37 +00:00

(Migrated from github.com)

Update from the reporter on Discord: the endless load entering the Deku Tree also happens on another emulator, so it's most likely the game dump or the save rather than Hookshot. Worth checking the .nup's size (a complete dump is about 23.8 GB) and trying a different save or a new game.

FancyCK commented

2026-11-10 21:44:51 +00:00

(Migrated from github.com)

hookshot_log.txt
hookshot_log.1.txt

Here are recent logs after checking the dump

[hookshot_log.txt](https://github.com/user-attachments/files/34652555/hookshot_log.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34652554/hookshot_log.1.txt) Here are recent logs after checking the dump

NotRexed commented

2026-11-11 21:23:58 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2506, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2506 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.