【BUG】Voxy 26.2: circular area fails to render after first import, fixed by re-importing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
- Windows 11 Home 25H2
- Minecraft: 26.2
- Voxy: [0.2.18]
- Sodium: [0.9.1]
- Fabric: [0.19.3]
- Chunky: [1.5.3]
- Shaders: IterationRP / Sundial / Helian-MMCO / Eclipse
- Singleplayer
Description
After pre-generating a large area with Chunky and importing the world with Voxy, a circular area around the world spawn fails to render correctly.
The important part is that the area inside and outside the circle renders normally, while a ring-shaped area in between does not.
If I physically move around the affected area, the missing terrain gradually gets loaded and the problem disappears.
Initially I suspected a shader compatibility issue, because several different shaderpacks showed the same problem. However, running "/voxy import" again, the problem disappeared.
After the problem was fixed, I could enable all of the previously affected shaderpacks without the issue returning.
I also reproduced the same problem in a second Minecraft 26.2 singleplayer world, which makes me suspect Voxy rather than a corrupted world.
The same general Chunky + Voxy workflow does not produce this issue for me on Minecraft 1.21.11.
Steps to reproduce
- Create/load a singleplayer world on Minecraft 26.2.
- Use Chunky to pre-generate a large circular area (in my case, radius 512 chunks).
- Import the world with Voxy.
- Observe that a circular/ring-shaped area around the world spawn does not render correctly.
- Moving around the affected area causes the missing terrain to gradually appear.
- Running "/voxy import" again fixes the issue.
Expected behavior
The entire pre-generated area should be available in Voxy's LODs after the initial import.
Actual behavior
A ring-shaped area is missing after the initial import, but becomes available after moving through the area or re-importing the world.
Additional information
This happened in two different 26.2 singleplayer worlds. It also occurs with multiple shaderpacks, but after re-importing with Voxy, all of those shaderpacks work normally.
This makes me suspect that the initial Voxy import/LOD ingestion is sometimes incomplete or fails to update some LOD regions correctly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Chunky pre-generation and initial /voxy import workflow in Minecraft 26.2, comparing the missing ring with the result after moving through it or importing again. Trace the initial import and LOD ingestion path; done means the entire pre-generated area is available in Voxy's LODs after the first import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100