AMD feedback (RX 6750 XT) and a couple of suggestions

NicoCancedda commented

2026-11-07 20:03:35 +00:00

(Migrated from github.com)

The idea

Hi, and thanks a lot for Hookshot, it's great to see how fast it's improving!

I've been testing it on an AMD card (RX 6750 XT, 12 GB, Windows 11) and framerates are very good, around 50 FPS while walking. Since AMD is listed as untested, here's what I saw on the build I used, in case it helps:

Build: https://github.com/NotRexed/Hookshot/releases#release-small-vram (small-vram)

Dialogue text boxes were not shown.
Some textures were missing.
The image was too bright and not very sharp.

I'm now rebuilding with the latest release and will report back on whether these are still present.

And two small ideas, in case they fit your plans (no pressure at all, I know how much is on your plate):

Internal resolution above 100%
The Insert menu offers Auto / 100 / 75 / 67 / 50%. Something like 125% or 150% (or a plain supersampling toggle for people with GPU headroom) would help image clarity on 1440p and higher displays.
An anti-aliasing option
I couldn't find any AA in the options, so edges look a bit jagged, especially at lower resolution scales. A cheap post-process pass like SMAA or FXAA would already help. FSR-style sharpening would be a nice bonus, although the existing Catmull-Rom / Lanczos sharpness already covers part of it.

I'm happy to test builds on AMD and report back if that helps.

Thanks again for all the work!

Anything else

No response

### The idea Hi, and thanks a lot for Hookshot, it's great to see how fast it's improving! I've been testing it on an AMD card (RX 6750 XT, 12 GB, Windows 11) and framerates are very good, around 50 FPS while walking. Since AMD is listed as untested, here's what I saw on the build I used, in case it helps: Build: https://github.com/NotRexed/Hookshot/releases#release-small-vram (small-vram) - Dialogue text boxes were not shown. - Some textures were missing. - The image was too bright and not very sharp. I'm now rebuilding with the latest release and will report back on whether these are still present. And two small ideas, in case they fit your plans (no pressure at all, I know how much is on your plate): 1. Internal resolution above 100% The Insert menu offers Auto / 100 / 75 / 67 / 50%. Something like 125% or 150% (or a plain supersampling toggle for people with GPU headroom) would help image clarity on 1440p and higher displays. 2. An anti-aliasing option I couldn't find any AA in the options, so edges look a bit jagged, especially at lower resolution scales. A cheap post-process pass like SMAA or FXAA would already help. FSR-style sharpening would be a nice bonus, although the existing Catmull-Rom / Lanczos sharpness already covers part of it. I'm happy to test builds on AMD and report back if that helps. Thanks again for all the work! ### Anything else _No response_

👍 1

NicoCancedda commented

2026-11-07 20:54:04 +00:00

(Migrated from github.com)

Update after testing the latest release.

Build: https://github.com/NotRexed/Hookshot/releases/tag/foliage-linux-updater

GPU: AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11. Settings: Resolution 100%, Upscaling Off, Frame pacing On, Frame generation Off.

What is fixed compared to the previous build (small-vram):

Dialogue text boxes and menu text are now shown.

What is still wrong on AMD:

Some surfaces and objects are too bright.
While moving, the image shimmers, as if some textures were overlapping and flickering on top of each other (it looks like z-fighting or layered surfaces fighting for the same pixels).

Performance is around 40-45 FPS while walking, which is playable, so the main remaining problems are the rendering issues above.

Short video (1080p, 60 FPS, about 40 seconds, Kokiri Forest) where both effects can be seen: https://streamable.com/d2syum

I'm happy to test any build or switch aimed at AMD, and to send logs if useful.

Thanks again!

Update after testing the latest release. Build: https://github.com/NotRexed/Hookshot/releases/tag/foliage-linux-updater GPU: AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11. Settings: Resolution 100%, Upscaling Off, Frame pacing On, Frame generation Off. What is fixed compared to the previous build (small-vram): - Dialogue text boxes and menu text are now shown. What is still wrong on AMD: - Some surfaces and objects are too bright. - While moving, the image shimmers, as if some textures were overlapping and flickering on top of each other (it looks like z-fighting or layered surfaces fighting for the same pixels). Performance is around 40-45 FPS while walking, which is playable, so the main remaining problems are the rendering issues above. Short video (1080p, 60 FPS, about 40 seconds, Kokiri Forest) where both effects can be seen: https://streamable.com/d2syum I'm happy to test any build or switch aimed at AMD, and to send logs if useful. Thanks again!

lcaiado commented

2026-11-07 21:32:55 +00:00

(Migrated from github.com)

Same here on an RX 6750 XT 12 GB (Windows 11, AMD driver 32.0.21045.16010), build foliage-linux-updater.

Shimmering / layered surfaces flickering while moving, short black flashes, and occasional hitches.
RX_VK_FOLLOW_GRAPHICS=0 in hookshot_env.txt helped a bit (~20% less flicker), but doesn't fix it.
In-game: Frame generation Off, Frame pacing Off, Resolution 100%, Game speed Real time.
~43 fps walking, no device lost. VRAM 9.9 of 10.4 GB allowed, 115 programs failed.

Log: https://gist.github.com/lcaiado/661090a11fa3178a372ec6518013572c

Happy to test any AMD build or switch. Thanks for the work!

Same here on an RX 6750 XT 12 GB (Windows 11, AMD driver 32.0.21045.16010), build foliage-linux-updater. - Shimmering / layered surfaces flickering while moving, short black flashes, and occasional hitches. - `RX_VK_FOLLOW_GRAPHICS=0` in hookshot_env.txt helped a bit (~20% less flicker), but doesn't fix it. - In-game: Frame generation Off, Frame pacing Off, Resolution 100%, Game speed Real time. - ~43 fps walking, no device lost. VRAM 9.9 of 10.4 GB allowed, 115 programs failed. Log: https://gist.github.com/lcaiado/661090a11fa3178a372ec6518013572c Happy to test any AMD build or switch. Thanks for the work!

y0riich10 commented

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

(Migrated from github.com)

Yep, I have the same issues also with my AMD RX 6750XT 12GB (Windows 11, AMD driver 32.0.21045.16010), build foliage-linux-updater, Ryzen 5 7600X, 32GB DDR5 RAM.

Apart from the issues mentioned, the game does show a decent FPS range, however, the FPS counter is bugged as it's barely visible/not visible. Secondly, sometimes the game does not load the first time, when it loads and compiles its shaders, it doesn't load into OOT but when I close the game and then re-open it, it loads fine.

I have attached 2 videos of the game not loading and also gameplay footage of what I've experienced, pretty much the exact same as @NicoCancedda and @Icaiado.

https://streamable.com/pmr3k0
https://streamable.com/9r0lre

Appreciate the work.

Yep, I have the same issues also with my AMD RX 6750XT 12GB (Windows 11, AMD driver 32.0.21045.16010), build foliage-linux-updater, Ryzen 5 7600X, 32GB DDR5 RAM. Apart from the issues mentioned, the game does show a decent FPS range, however, the FPS counter is bugged as it's barely visible/not visible. Secondly, sometimes the game does not load the first time, when it loads and compiles its shaders, it doesn't load into OOT but when I close the game and then re-open it, it loads fine. I have attached 2 videos of the game not loading and also gameplay footage of what I've experienced, pretty much the exact same as @NicoCancedda and @Icaiado. https://streamable.com/pmr3k0 https://streamable.com/9r0lre Appreciate the work.

NotRexed commented

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

(Migrated from github.com)

Thanks for the videos. A first start that stops after compiling and then works on reopening is very likely the first-time shader compiling; if it happens again, please attach that run's hookshot_log.txt (next to hookshot.exe). The black flashes and flicker are tracked in #145, and EvilBoyce's fix for them is in the next release, coming soon.

Thanks for the videos. A first start that stops after compiling and then works on reopening is very likely the first-time shader compiling; if it happens again, please attach that run's `hookshot_log.txt` (next to `hookshot.exe`). The black flashes and flicker are tracked in #145, and EvilBoyce's fix for them is in the next release, coming soon.

NicoCancedda commented

2026-11-08 02:42:27 +00:00

(Migrated from github.com)

Thanks for the reply @NotRexed , i'm encountering a strange bug in the new release i attach a screenshot so you can see it

this never happened with the previous builds Edit : I've downloaded the latest build and this error vanished

Thanks for the reply @NotRexed , i'm encountering a strange bug in the new release i attach a screenshot so you can see it <img width="354" height="47" alt="Image" src="https://github.com/user-attachments/assets/5281f6b6-b1ed-4af4-b694-6f8e2af4f544" /> this never happened with the previous builds Edit : I've downloaded the latest build and this error vanished

NicoCancedda commented

2026-11-08 03:43:22 +00:00

(Migrated from github.com)

Update after testing the new release.

Build: https://github.com/NotRexed/Hookshot/releases/tag/device-lost-fix

GPU: AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11, Intel i7-11700F, 32 GB RAM.

What I see on AMD with this build (screenshots attached, video here: https://streamable.com/x5ll3e):

Performance and stutter
Frame rate is around 24 FPS while walking (26 FPS in the attached screenshot), with very heavy stutter. On the previous build (foliage-linux-updater) I was getting about 40-45 FPS, but I suspect that was because some shaders or effects were not being drawn yet, so the drop may simply be the cost of rendering more of the scene correctly. It is still better than what I get from the Switch 2 emulators on this card. I'm not sure whether the stutter is shader compilation on first visit or something else, so I'm happy to test with any switch or log you suggest.
White glowing textures
Some textures appear very bright white and seem to glow, for example the trim at the edges of the Kokiri tunics.
Terrain looks wrong
The ground shows streaky, smeared patterns, as if textures were overlapping or sampled wrongly. It is visible in the second screenshot, on the grass and dirt near the steps.
No anti-aliasing
Edges are very jagged (fences, logs, steps) and it is quite noticeable. If it fits your plans, a simple post-process AA such as SMAA or FXAA, plus an internal resolution above 100% or supersampling, would make a big difference.

I can send logs, test builds or try specific settings on AMD, just let me know what is useful.

Thanks again for all the work, it's impressive how fast this is moving!

<img width="2559" height="1439" alt="Image" src="https://github.com/user-attachments/assets/15434d2e-4cdb-4c16-8476-5bb72f378386" /> <img width="1266" height="982" alt="Image" src="https://github.com/user-attachments/assets/0595bad9-eb0d-46e3-9d34-a58c527c1059" /> Update after testing the new release. Build: https://github.com/NotRexed/Hookshot/releases/tag/device-lost-fix GPU: AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11, Intel i7-11700F, 32 GB RAM. What I see on AMD with this build (screenshots attached, video here: https://streamable.com/x5ll3e): 1. Performance and stutter Frame rate is around 24 FPS while walking (26 FPS in the attached screenshot), with very heavy stutter. On the previous build (foliage-linux-updater) I was getting about 40-45 FPS, but I suspect that was because some shaders or effects were not being drawn yet, so the drop may simply be the cost of rendering more of the scene correctly. It is still better than what I get from the Switch 2 emulators on this card. I'm not sure whether the stutter is shader compilation on first visit or something else, so I'm happy to test with any switch or log you suggest. 2. White glowing textures Some textures appear very bright white and seem to glow, for example the trim at the edges of the Kokiri tunics. 3. Terrain looks wrong The ground shows streaky, smeared patterns, as if textures were overlapping or sampled wrongly. It is visible in the second screenshot, on the grass and dirt near the steps. 4. No anti-aliasing Edges are very jagged (fences, logs, steps) and it is quite noticeable. If it fits your plans, a simple post-process AA such as SMAA or FXAA, plus an internal resolution above 100% or supersampling, would make a big difference. I can send logs, test builds or try specific settings on AMD, just let me know what is useful. Thanks again for all the work, it's impressive how fast this is moving!

NicoCancedda commented

2026-11-08 05:35:59 +00:00

(Migrated from github.com)

Additional information after playing for about 40 minutes with the same build (device-lost-fix). Performance was very bad this time, and I took screenshots of Task Manager and AMD Adrenalin while it was running:

GPU is almost idle in the screenshots: 3% 3D utilization in Task Manager, 8% in Adrenalin, about 40 W power draw and 47 C. That was captured during a shader compilation moment, while during normal gameplay it goes up to around 20-25% with about 80 W power draw. Still, the card is clearly waiting on something.
GPU memory is full: 11.8 / 12.0 GB dedicated (12,051 MB in Adrenalin), and 4.8 GB already used as shared memory. I suspect resources are being pushed to system memory, which could explain the heavy stutter.
System RAM is high: 28.1 / 31.9 GB (88%) in total. I have not checked how much of it belongs to the game process, I will report back. The README mentions about 10 GB for a run, so I'm not sure if this is expected.
CPU: Adrenalin shows 100% while Task Manager shows 57% total. Looking at per-core usage on my i7-11700F, a few threads are completely pegged at 100% while the remaining ones sit around 30-40%, so it definitely looks thread-bound.

AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11, 32 GB RAM.

If it helps, I can run a profiler, send logs or test any option you think is useful on AMD. Thanks again!

Additional information after playing for about 40 minutes with the same build (device-lost-fix). Performance was very bad this time, and I took screenshots of Task Manager and AMD Adrenalin while it was running: - GPU is almost idle in the screenshots: 3% 3D utilization in Task Manager, 8% in Adrenalin, about 40 W power draw and 47 C. That was captured during a shader compilation moment, while during normal gameplay it goes up to around 20-25% with about 80 W power draw. Still, the card is clearly waiting on something. - GPU memory is full: 11.8 / 12.0 GB dedicated (12,051 MB in Adrenalin), and 4.8 GB already used as shared memory. I suspect resources are being pushed to system memory, which could explain the heavy stutter. - System RAM is high: 28.1 / 31.9 GB (88%) in total. I have not checked how much of it belongs to the game process, I will report back. The README mentions about 10 GB for a run, so I'm not sure if this is expected. - CPU: Adrenalin shows 100% while Task Manager shows 57% total. Looking at per-core usage on my i7-11700F, a few threads are completely pegged at 100% while the remaining ones sit around 30-40%, so it definitely looks thread-bound. AMD RX 6750 XT 12 GB (driver 32.0.21045.16010), Windows 11, 32 GB RAM. If it helps, I can run a profiler, send logs or test any option you think is useful on AMD. Thanks again! <img width="1276" height="1030" alt="Image" src="https://github.com/user-attachments/assets/b3b15740-f9d4-4c46-8aee-5df5581d8b33" /> <img width="2556" height="1389" alt="Image" src="https://github.com/user-attachments/assets/0b67c449-8d53-4815-8acc-398ba45b140e" />

y0riich10 commented

2026-11-08 13:22:09 +00:00

(Migrated from github.com)

I've gone through the latest build #fast-updates, overall, it is playable in terms of the FPS only however, some bits of the gameplay is still an issue which did not occur in a previous build I had played, forgotten which one.

1.) Screen flickering: You probably already know but there is constant screen flickering when playing.
2.) Bright Objects: As mentioned above, some textures such as the tunics, light sources shine very bright.

A personal suggestion, as mentioned above, would be to add some form of anti-aliasing (SMAA, FXAA), anisotropic filtering and a better windows adapting filter/upscaling such as AMD FSR to give a better overall experience of the gameplay. The difference I see in quality with the Lichii emulator and this recomp is very clear so having these features would be greatly appreciated.

Specs: Ryzen 5 7600X, RX 6750 XT 12GB (driver 32.0.21045.16010), Windows 11, 32GB DRR5 RAM.

This is still all within Kokiri Forest, I haven't explored any other parts yet, not willing to until the gameplay does become a lot more better and playable.

I've attached a log and a video of what I've been experiencing.

hookshot_log.txt
https://drive.google.com/file/d/1qsLudVgHIqq48XvtwWtlIxahz5p-bpUV/view
https://drive.google.com/file/d/1rMpzzqRHWsj1gsGOLsreZWYF4Etb2-n9/view?usp=drive_link (metrics)

Appreciate it.

I've gone through the latest build #fast-updates, overall, it is playable in terms of the FPS only however, some bits of the gameplay is still an issue which did not occur in a previous build I had played, forgotten which one. 1.) Screen flickering: You probably already know but there is constant screen flickering when playing. 2.) Bright Objects: As mentioned above, some textures such as the tunics, light sources shine very bright. A personal suggestion, as mentioned above, would be to add some form of anti-aliasing (SMAA, FXAA), anisotropic filtering and a better windows adapting filter/upscaling such as AMD FSR to give a better overall experience of the gameplay. The difference I see in quality with the Lichii emulator and this recomp is very clear so having these features would be greatly appreciated. Specs: Ryzen 5 7600X, RX 6750 XT 12GB (driver 32.0.21045.16010), Windows 11, 32GB DRR5 RAM. This is still all within Kokiri Forest, I haven't explored any other parts yet, not willing to until the gameplay does become a lot more better and playable. I've attached a log and a video of what I've been experiencing. [hookshot_log.txt](https://github.com/user-attachments/files/34543733/hookshot_log.txt) https://drive.google.com/file/d/1qsLudVgHIqq48XvtwWtlIxahz5p-bpUV/view https://drive.google.com/file/d/1rMpzzqRHWsj1gsGOLsreZWYF4Etb2-n9/view?usp=drive_link (metrics) Appreciate it.

tdsantos commented

2026-11-08 17:00:09 +00:00

(Migrated from github.com)

Update on v2.0.1, RX 6750 XT

GPU: AMD RX 6750 XT 12 GB (Adrenalin 26.10.1, Vulkan 1.4), Windows 11, Ryzen 7 5700X, 64 GB RAM.

Before v2.0.0 (build low-vram-14): Kokiri Forest had a brief full-screen brightness flash ("lightning"). Quality preset, frame generation, resolution and upscaling made no difference.

With RX_VK_NOOPT=1 in hookshot_env.txt the flash was gone, but the game dropped from ~55 to ~30 real fps.
Removing RX_VK_NOOPT=1 afterwards made "Preparing shaders" hang at 99%, with graphics pipeline for 6eaa646d07ea4e43 not made (-13) (and another) in the log. This is the AMD compiler failure described in vk_draw.cpp.

After updating to v2.0.1 (Update button, same folder), with RX_VK_NOOPT=1 still on and the High (12GB) preset: no flash, no hang. Shader preparation (95955 shaders) completed on the first run. Walking in Kokiri it shows ~73 fps with 2x frame generation (game ~38).

Not tested yet: v2.0.1 without RX_VK_NOOPT=1. Since #574 was fixed by waiting for the GPU every frame, I suspect NOOPT only hid that bug by slowing the GPU, so the flash may already be gone without it. I'll report back once I test it (and whether the -13 compile error still happens).

Happy to test any AMD switch and send logs.

**Update on v2.0.1, RX 6750 XT** GPU: AMD RX 6750 XT 12 GB (Adrenalin 26.10.1, Vulkan 1.4), Windows 11, Ryzen 7 5700X, 64 GB RAM. **Before v2.0.0 (build `low-vram-14`):** Kokiri Forest had a brief full-screen brightness flash ("lightning"). Quality preset, frame generation, resolution and upscaling made no difference. - With `RX_VK_NOOPT=1` in `hookshot_env.txt` the flash was gone, but the game dropped from ~55 to ~30 real fps. - Removing `RX_VK_NOOPT=1` afterwards made "Preparing shaders" hang at 99%, with `graphics pipeline for 6eaa646d07ea4e43 not made (-13)` (and another) in the log. This is the AMD compiler failure described in `vk_draw.cpp`. **After updating to v2.0.1** (Update button, same folder), with `RX_VK_NOOPT=1` still on and the High (12GB) preset: no flash, no hang. Shader preparation (95955 shaders) completed on the first run. Walking in Kokiri it shows ~73 fps with 2x frame generation (game ~38). **Not tested yet:** v2.0.1 without `RX_VK_NOOPT=1`. Since #574 was fixed by waiting for the GPU every frame, I suspect NOOPT only hid that bug by slowing the GPU, so the flash may already be gone without it. I'll report back once I test it (and whether the -13 compile error still happens). Happy to test any AMD switch and send logs.

tdsantos commented

2026-11-08 19:30:31 +00:00

(Migrated from github.com)

Follow-up: v2.0.2, RX 6750 XT works without NOOPT

Update on my previous comment. On v2.0.2 (same hardware, Adrenalin 26.10.1):

Without RX_VK_NOOPT=1, the precompile step ("Preparing shaders") hung at 99% on start, with graphics pipeline for 5fa56485a6b07619 not made (-13) in the log (v2.0.1 also showed 6eaa646d07ea4e43). After two failed starts, the "notes are dropped" recovery kicked in and the game ran fine, but the next start hung again, since the notes are rebuilt while playing.
RX_VK_PRECOMPILE=0 in hookshot_env.txt avoids the hang: it starts normally every time.
Result: no RX_VK_NOOPT, no flash, game at ~45+ fps real (90+ with 2x frame generation) in Kokiri, versus ~30-38 with NOOPT.

So the AMD compiler error is in the precompile of pipeline 5fa56485a6b07619 specifically; the rest compile fine in play. Happy to test anything on this.

**Follow-up: v2.0.2, RX 6750 XT works without NOOPT** Update on my previous comment. On v2.0.2 (same hardware, Adrenalin 26.10.1): - Without `RX_VK_NOOPT=1`, the precompile step ("Preparing shaders") hung at 99% on start, with `graphics pipeline for 5fa56485a6b07619 not made (-13)` in the log (v2.0.1 also showed `6eaa646d07ea4e43`). After two failed starts, the "notes are dropped" recovery kicked in and the game ran fine, but the next start hung again, since the notes are rebuilt while playing. - **`RX_VK_PRECOMPILE=0` in `hookshot_env.txt`** avoids the hang: it starts normally every time. - Result: no `RX_VK_NOOPT`, no flash, game at ~45+ fps real (90+ with 2x frame generation) in Kokiri, versus ~30-38 with NOOPT. So the AMD compiler error is in the precompile of pipeline `5fa56485a6b07619` specifically; the rest compile fine in play. Happy to test anything on this.

Lukoak commented

2026-11-09 01:29:05 +00:00

(Migrated from github.com)

HOW DO U GOT 50 FPS?

NotRexed commented

2026-11-09 05:46:13 +00:00

(Migrated from github.com)

Tracked in #1006, follow there. That issue collects every report of AMD-specific rendering problems, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your hookshot_log.txt.

Tracked in #1006, follow there. That issue collects every report of AMD-specific rendering problems, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your `hookshot_log.txt`.

Rows
Columns

AMD feedback (RX 6750 XT) and a couple of suggestions #305

The idea

Anything else