Minor: Floating trees in Kakariko Village #352

Closed
opened 2026-11-07 22:02:41 +00:00 by Gh0sTSaysHi · 9 comments
Gh0sTSaysHi commented 2026-11-07 22:02:41 +00:00 (Migrated from github.com)

Builder version

Foliage and lighting

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

Stepping back into Kakariko village after finishing Death Mountain for Great Fairy, I get flown down to the top of a roof. Looking out and around, there's about 50 trees just up in the air. I tried replicating on Lichii with my save and didn't have the same issue. Not game breaking. Just thought I'd mention it in case it causes something bigger down the line.

Visual Studio or Build Tools version, and Windows SDK version

No response

Operating system and free space on the output drive

Windows 11 25H2 / 338 GB Free on Output Drive

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 ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text Stepping back into Kakariko village after finishing Death Mountain for Great Fairy, I get flown down to the top of a roof. Looking out and around, there's about 50 trees just up in the air. I tried replicating on Lichii with my save and didn't have the same issue. Not game breaking. Just thought I'd mention it in case it causes something bigger down the line. ``` ### Visual Studio or Build Tools version, and Windows SDK version _No response_ ### Operating system and free space on the output drive Windows 11 25H2 / 338 GB Free on Output Drive ### 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.
Gh0sTSaysHi commented 2026-11-07 22:03:18 +00:00 (Migrated from github.com)
Image
<img width="1279" height="740" alt="Image" src="https://github.com/user-attachments/assets/a7bc9e1f-fe61-453a-9e6c-feeabc2dad53" />
NotRexed commented 2026-11-07 22:19:23 +00:00 (Migrated from github.com)

Thanks for the report and the screenshot! Could you attach hookshot_log.txt from a run where the trees float (next to hookshot.exe), and say which GPU and driver you have? It would also help to know whether they're still floating after you leave Kakariko and come back.

Thanks for the report and the screenshot! Could you attach `hookshot_log.txt` from a run where the trees float (next to `hookshot.exe`), and say which GPU and driver you have? It would also help to know whether they're still floating after you leave Kakariko and come back.
miniskulljob commented 2026-11-07 22:28:01 +00:00 (Migrated from github.com)

Same problem here, inside and outside of Kakariko. I also have a weird shadow flickering issue...

hookshot_log.txt

Same problem here, inside and outside of Kakariko. I also have a weird shadow flickering issue... [hookshot_log.txt](https://github.com/user-attachments/files/34529844/hookshot_log.txt)
hallygtree commented 2026-11-08 04:37:28 +00:00 (Migrated from github.com)

Same here, floating trees in Kakariko Village (they look like the Death Mountain slope trees with the mountain itself not drawn, as in #422).

  • Release: device-lost-fix (source caaaf2b7), built with Hookshot Builder from a .nup (build e0f3ccfa, v131072)
  • GPU: NVIDIA GeForce RTX 3050 Laptop GPU, 4 GB, driver 617.42 (Windows 11)
  • Settings: Quality preset Minimum (4GB), Handheld profile On, Resolution 50%, Lanczos, frame generation 2x
  • Mods: one RomFS mod loaded (DualSense button icons: font, UI textures and ResourceSizeTable)
  • Save: copied over from an emulator

Log from the run where the trees floated (I went from Kakariko into the Royal Family's Tomb afterwards in the same run): https://gist.github.com/hallygtree/1d14e332852279a847947fa4ad6264c4

Same here, floating trees in Kakariko Village (they look like the Death Mountain slope trees with the mountain itself not drawn, as in #422). - **Release:** device-lost-fix (source caaaf2b7), built with Hookshot Builder from a .nup (build e0f3ccfa, v131072) - **GPU:** NVIDIA GeForce RTX 3050 Laptop GPU, 4 GB, driver 617.42 (Windows 11) - **Settings:** Quality preset Minimum (4GB), Handheld profile On, Resolution 50%, Lanczos, frame generation 2x - **Mods:** one RomFS mod loaded (DualSense button icons: font, UI textures and ResourceSizeTable) - **Save:** copied over from an emulator Log from the run where the trees floated (I went from Kakariko into the Royal Family's Tomb afterwards in the same run): https://gist.github.com/hallygtree/1d14e332852279a847947fa4ad6264c4
alberthorta commented 2026-11-08 12:43:49 +00:00 (Migrated from github.com)

Still happening on the latest release, low-vram (source 618e37c6), and not only in Kakariko: I see floating trees when entering the Hyrule Castle area.

  • GPU: RTX 2080 Super (8 GB), NVIDIA driver 621.14, Windows 11
  • Built with: Hookshot Builder (update offer) from a .nup (build e0f3ccfa)
  • Settings: Quality preset Low (6GB), Handheld profile On, Resolution 75%, Lanczos, frame generation 2x; RX_VK_WAIT_GPU=0 in hookshot_env.txt
  • Log: no shader translation failures (0 failed), no device loss or crash during the session

This fits the reading above (Death Mountain slope trees drawn without the mountain, as in #422), since Death Mountain is visible in the distance from the castle area too. I can attach hookshot_log.txt if it helps.

Still happening on the latest release, **`low-vram`** (source `618e37c6`), and not only in Kakariko: I see floating trees **when entering the Hyrule Castle area**. - **GPU:** RTX 2080 Super (8 GB), NVIDIA driver 621.14, Windows 11 - **Built with:** Hookshot Builder (update offer) from a .nup (build e0f3ccfa) - **Settings:** Quality preset Low (6GB), Handheld profile On, Resolution 75%, Lanczos, frame generation 2x; `RX_VK_WAIT_GPU=0` in `hookshot_env.txt` - **Log:** no shader translation failures (`0 failed`), no device loss or crash during the session This fits the reading above (Death Mountain slope trees drawn without the mountain, as in #422), since Death Mountain is visible in the distance from the castle area too. I can attach `hookshot_log.txt` if it helps.
mshooba commented 2026-11-08 17:19:45 +00:00 (Migrated from github.com)

Still happening on v2.0.2 (latest), so not tied to low settings or VRAM:

  • GPU: RTX 4070 Ti Super 16 GB, Ryzen 7 5700X3D, Windows 11
  • Settings: Ultra (16GB+), Resolution 100%, Lanczos, 4K fullscreen
  • Built via Hookshot Builder from a .nup, updated through the launcher

Same pattern — trees climbing into the sky in the shape of a slope, which matches
the Death Mountain trees-without-the-mountain reading (#422). Screenshot attached.

Image
Still happening on v2.0.2 (latest), so not tied to low settings or VRAM: - GPU: RTX 4070 Ti Super 16 GB, Ryzen 7 5700X3D, Windows 11 - Settings: Ultra (16GB+), Resolution 100%, Lanczos, 4K fullscreen - Built via Hookshot Builder from a .nup, updated through the launcher Same pattern — trees climbing into the sky in the shape of a slope, which matches the Death Mountain trees-without-the-mountain reading (#422). Screenshot attached. <img width="3587" height="2020" alt="Image" src="https://github.com/user-attachments/assets/5c76d1e1-0778-4a8d-bff4-c0a1b164dac6" />
HabibiSteve commented 2026-11-09 04:41:05 +00:00 (Migrated from github.com)

Same here on v2.0.5 (Windows, NVIDIA). Floating trees in many places around Hyrule, not just Kakariko. In Hyrule Field, for example, trees stand where the hillside under them should be, matching the "mountain not drawn" explanation in #422.

Setup

  • Hookshot v2.0.5, built with the Windows Hookshot Builder from a .nup (program 0400486024DEC000, v131072, build e0f3ccfa)
  • GPU: NVIDIA GeForce RTX 4070 (12 GB), driver 32.0.16.2114, Vulkan 1.4
  • CPU: AMD Ryzen 9 9950X3D, 32 GB RAM, Windows 11 Pro
  • Settings: High (12GB) preset, resolution 100%, frame generation 2x (game at 60 fps)
Same here on v2.0.5 (Windows, NVIDIA). Floating trees in many places around Hyrule, not just Kakariko. In Hyrule Field, for example, trees stand where the hillside under them should be, matching the "mountain not drawn" explanation in #422. **Setup** - Hookshot v2.0.5, built with the Windows Hookshot Builder from a .nup (program 0400486024DEC000, v131072, build e0f3ccfa) - GPU: NVIDIA GeForce RTX 4070 (12 GB), driver 32.0.16.2114, Vulkan 1.4 - CPU: AMD Ryzen 9 9950X3D, 32 GB RAM, Windows 11 Pro - Settings: High (12GB) preset, resolution 100%, frame generation 2x (game at 60 fps)
NotRexed commented 2026-11-09 05:47:06 +00:00 (Migrated from github.com)

Tracked in #994, follow there. That issue collects every report of floating trees and missing or vanishing vegetation, and this one is linked from it with its GPU, version and log details. It is a known issue in v2.0.6 and not fixed yet. This was the main floating-trees report; its details and the #422 trace are summarised there. 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 #994, follow there. That issue collects every report of floating trees and missing or vanishing vegetation, and this one is linked from it with its GPU, version and log details. It is a known issue in v2.0.6 and not fixed yet. This was the main floating-trees report; its details and the #422 trace are summarised there. 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`.
BernabeCR93 commented 2026-11-09 07:59:41 +00:00 (Migrated from github.com)

Found which program draws the floating trees, in case it helps (v2.0.6 + local changes, RTX 3060 Ti, Windows).

I hid mesh programs one at a time while looking at the floating trees over Kakariko (RX_VK_SKIP_FILE, bisection with screenshots). They are all drawn by one mesh program: 3cb7682790143836. With only that program left out:

  • the floating trees are gone, all around Kakariko (360°);
  • the near mountain and its own trees are still drawn correctly;
  • the distant Death Mountain is still drawn (that one is c36a4f3f667c886a / 9d8403e2e566c773, so the "mountain not drawn" reading from #422 doesn't seem to be the cause here: the mountain is there, these trees are extra).

As a stopgap I skip it by default in vk_draw.cpp (added to the RX_VK_SKIP_PROG default list, with a switch to draw it again). It looks like a far-LOD forest whose own culling/placement goes wrong rather than missing terrain under it. I haven't checked yet whether skipping it removes legitimate distant trees elsewhere (Hyrule Field from a distance looked fine).

Found which program draws the floating trees, in case it helps (v2.0.6 + local changes, RTX 3060 Ti, Windows). I hid mesh programs one at a time while looking at the floating trees over Kakariko (`RX_VK_SKIP_FILE`, bisection with screenshots). They are all drawn by **one mesh program: `3cb7682790143836`**. With only that program left out: - the floating trees are gone, all around Kakariko (360°); - the near mountain and its own trees are still drawn correctly; - the distant Death Mountain is still drawn (that one is `c36a4f3f667c886a` / `9d8403e2e566c773`, so the "mountain not drawn" reading from #422 doesn't seem to be the cause here: the mountain is there, these trees are extra). As a stopgap I skip it by default in `vk_draw.cpp` (added to the `RX_VK_SKIP_PROG` default list, with a switch to draw it again). It looks like a far-LOD forest whose own culling/placement goes wrong rather than missing terrain under it. I haven't checked yet whether skipping it removes legitimate distant trees elsewhere (Hyrule Field from a distance looked fine).
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#352
No description provided.