MagicBeanDev/Hookshot

Archived

Watch

Fork 0

Crash on 3D load persists on RX 570 #355

Closed

opened 2026-11-07 22:03:55 +00:00 by ArcaPhria · 6 comments

ArcaPhria commented

2026-11-07 22:03:55 +00:00

(Migrated from github.com)

Builder version

Foliage and lighting, update offer, Linux AppImage, rumble

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

Hey everyone, 

Quick update regarding lower-end AMD hardware (Radeon RX 570 4GB / i5-8500 / 16GB RAM) after the latest update:

The good news is that the visual bugs in the menus are gone! The text now loads instantly and everything looks perfectly clear, so thanks a lot for fixing that part. 

The bad news is that the game still hits a hard crash and force closes the exact second it tries to transition into the 3D world map. I read in the latest notes that a new menu was added to modify the resolution scaling (which could definitely help with my 4GB VRAM limit), but I honestly cannot find it anywhere in the application or menus. 

Could anyone point out exactly how to access or configure this new scaling menu? Is it a keyboard shortcut or a hidden setting in a config file? Any help would be highly appreciated so I can test if lowering the scale bypasses the 3D map crash. Thanks!

Visual Studio or Build Tools version, and Windows SDK version

Last Version

Operating system and free space on the output drive

Window 10

Before you send it

I'm on the newest release, or it still fails on it.
I searched the open issues for this error.
I'm not attaching game files or anything built from them.

### Builder version Foliage and lighting, update offer, Linux AppImage, rumble ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text Hey everyone, Quick update regarding lower-end AMD hardware (Radeon RX 570 4GB / i5-8500 / 16GB RAM) after the latest update: The good news is that the visual bugs in the menus are gone! The text now loads instantly and everything looks perfectly clear, so thanks a lot for fixing that part. The bad news is that the game still hits a hard crash and force closes the exact second it tries to transition into the 3D world map. I read in the latest notes that a new menu was added to modify the resolution scaling (which could definitely help with my 4GB VRAM limit), but I honestly cannot find it anywhere in the application or menus. Could anyone point out exactly how to access or configure this new scaling menu? Is it a keyboard shortcut or a hidden setting in a config file? Any help would be highly appreciated so I can test if lowering the scale bypasses the 3D map crash. Thanks! ``` ### Visual Studio or Build Tools version, and Windows SDK version Last Version ### Operating system and free space on the output drive Window 10 ### Before you send it - [x] I'm on the newest release, or it still fails on it. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.

ArcaPhria commented

2026-11-07 22:04:07 +00:00

(Migrated from github.com)

hookshot_log.txt

[hookshot_log.txt](https://github.com/user-attachments/files/34529533/hookshot_log.txt)

NotRexed commented

2026-11-07 22:19:21 +00:00

(Migrated from github.com)

Thanks for the update, and glad the menu text is fixed now.

The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the Resolution line (Auto / 100 / 75 / 67 / 50%).

The hookshot_log.txt you attached ends very early (right after the renderer starts, before the precompile line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, hookshot.exe), the exception code and offset from it would help too. The earlier RX 570 crash report is #192.

Thanks for the update, and glad the menu text is fixed now. The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the **Resolution** line (Auto / 100 / 75 / 67 / 50%). The `hookshot_log.txt` you attached ends very early (right after the renderer starts, before the `precompile` line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, `hookshot.exe`), the exception code and offset from it would help too. The earlier RX 570 crash report is #192.

ArcaPhria commented

2026-11-07 23:57:42 +00:00

(Migrated from github.com)

Thanks for the update, and glad the menu text is fixed now.

The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the Resolution line (Auto / 100 / 75 / 67 / 50%).

The hookshot_log.txt you attached ends very early (right after the renderer starts, before the precompile line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, hookshot.exe), the exception code and offset from it would help too. The earlier RX 570 crash report is #192.

Thank you very much.
I lowered the resolution to 50% in the settings and started the game. After a few seconds, the FPS dropped to 0, the screen went black, and then the game crashed again.
I’ve attached the file once more. I believe it captured the error information this time.

hookshot_log.txt

> Thanks for the update, and glad the menu text is fixed now. > > The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the **Resolution** line (Auto / 100 / 75 / 67 / 50%). > > The `hookshot_log.txt` you attached ends very early (right after the renderer starts, before the `precompile` line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, `hookshot.exe`), the exception code and offset from it would help too. The earlier RX 570 crash report is [#192](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/192). Thank you very much. I lowered the resolution to 50% in the settings and started the game. After a few seconds, the FPS dropped to 0, the screen went black, and then the game crashed again. I’ve attached the file once more. I believe it captured the error information this time. [hookshot_log.txt](https://github.com/user-attachments/files/34530882/hookshot_log.txt)

ArcaPhria commented

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

(Migrated from github.com)

Thanks for the update, and glad the menu text is fixed now.

The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the Resolution line (Auto / 100 / 75 / 67 / 50%).

The hookshot_log.txt you attached ends very early (right after the renderer starts, before the precompile line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, hookshot.exe), the exception code and offset from it would help too. The earlier RX 570 crash report is #192.

hookshot_log.txt

> Thanks for the update, and glad the menu text is fixed now. > > The resolution option is in the in-game menu: press Insert (or F1) while the game runs and use the **Resolution** line (Auto / 100 / 75 / 67 / 50%). > > The `hookshot_log.txt` you attached ends very early (right after the renderer starts, before the `precompile` line), so it doesn't reach the crash. Could you attach the log straight after a crash, and say which Radeon driver version you have? If Windows shows an error dialog, or an entry in Event Viewer (Windows Logs > Application, `hookshot.exe`), the exception code and offset from it would help too. The earlier RX 570 crash report is [#192](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/192). <img width="1920" height="1022" alt="Image" src="https://github.com/user-attachments/assets/d1467347-d214-4718-8cc3-a278b6d82eb0" /> [hookshot_log.txt](https://github.com/user-attachments/files/34531151/hookshot_log.txt)

NotRexed commented

2026-11-08 00:40:30 +00:00

(Migrated from github.com)

Thanks for the report! This is the same problem as #192, so I'm folding it into that issue to keep everything in one place. Please follow #192, and add your log there if it shows something new.

ArcaPhria commented

2026-11-08 03:40:52 +00:00

(Migrated from github.com)

Thanks for the report! This is the same problem as #192, so I'm folding it into that issue to keep everything in one place. Please follow #192, and add your log there if it shows something new.

Quick update after testing the latest release and tweaking the config file:

Good news is that the game now actually boots into the 3D world! I can see Link inside his house, and it runs surprisingly smooth for about 10 seconds. However, it still suffers from some visual bugs before it hits a wall.

After those 10 seconds, the VRAM fills up completely, and the game hits a hard crash with the Windows application error: "The memory could not be read" (hookshot.exe).

Specs: Radeon RX 570 4GB / i5-8500 / 16GB RAM.

It is definitely a huge step forward compared to when it wouldn't even open! It seems the port just needs better memory management or an aggressive VRAM garbage collector for 4GB cards so it doesn't overflow during gameplay. Attaching the crash screenshot.

hookshot_log.txt

> Thanks for the report! This is the same problem as [#192](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/192), so I'm folding it into that issue to keep everything in one place. Please follow [#192](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/192), and add your log there if it shows something new. Quick update after testing the latest release and tweaking the config file: Good news is that the game now actually boots into the 3D world! I can see Link inside his house, and it runs surprisingly smooth for about 10 seconds. However, it still suffers from some visual bugs before it hits a wall. After those 10 seconds, the VRAM fills up completely, and the game hits a hard crash with the Windows application error: "The memory could not be read" (hookshot.exe). Specs: Radeon RX 570 4GB / i5-8500 / 16GB RAM. It is definitely a huge step forward compared to when it wouldn't even open! It seems the port just needs better memory management or an aggressive VRAM garbage collector for 4GB cards so it doesn't overflow during gameplay. Attaching the crash screenshot. <img width="1600" height="867" alt="Image" src="https://github.com/user-attachments/assets/e9a45873-67b3-4556-a69d-4a9a3009f97f" /> [hookshot_log.txt](https://github.com/user-attachments/files/34536862/hookshot_log.txt)

Commenting is not possible because the repository is archived.