WorldScape3D terrain saved with region size 256 no longer loads correctly
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Read WorldScape3D::set_region_size(), load_directory(), and the existing change_region_size() implementation. Open the linked MRP and reproduce the out-of-bounds errors with one 256 region, then check loading with multiple 256 regions. Done means existing 256 region terrain loads fully at 512 without map access errors; the author says a fix is ready and plans to open a PR.
Written by the indexing model from the issue text.
Description
Tested versions
- Reproducible in:
master(2f04816ffd), local Linux editor build.
System information
CachyOS (Linux 7.2), x86_64.
Issue description
WorldScape3D terrain saved with region size 256 no longer loads correctly. #1450 removed region size 256 without migrating existing data. WorldScape3D::set_region_size() now rejects anything below 512, but load_directory() still loads the old files:
- One 256 region: the terrain stays at 512 while the region's maps are 256. Every frame logs thousands of errors like
Index p_y = 272 is out of bounds (height = 256), because collision reads past the maps, and the shader samples past them too. - Two or more 256 regions: the second file hits the size check in
load_directory(), which returns early, so the directory is only half loaded and nothing renders.
The terrain data from #1374's MRP uses 256 regions, so it hits the first case.
Steps to reproduce
- Open #1374's MRP (world_scape_mrp.zip) in current
master. - Open
world_scape_3d.tscn. The output fills withget_pixelout-of-bounds errors. - With terrain data that has two or more 256 regions (saved before #1450), no terrain renders.
Minimal reproduction project (MRP)
#1374's MRP.
I have a fix ready: regions saved at 256 are upsized to 512 on load, using the existing change_region_size(). I'll open a PR.
AI disclosure: I used Claude Code to find the cause and draft this report.
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 337
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from Redot-Engine/redot-engine
-
Broken links in the docsPossibly taken @DaveTheEggman claimed this today. Openbug documentation
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Redot-Engine/redot-engine#1542 ·
Maintainers usually reply within 1 day
-
bug topic:gdextension usability
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Redot-Engine/redot-engine#1544 ·
Maintainers usually reply within 1 day
-
WorldScape3D has no collision near the world origin with vertex_spacing > 1Possibly taken @KazW claimed this 1 day ago. Openbug topic:worldscape usability
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Redot-Engine/redot-engine#1537 ·
Maintainers usually reply within 1 day
-
bug topic:3d topic:rendering
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Redot-Engine/redot-engine#1533 ·
Maintainers usually reply within 1 day
-
bug usability
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Redot-Engine/redot-engine#1525 · 2 reactions ·
Maintainers usually reply within 1 day
All issues in Redot-Engine/redot-engine
Similar issues
-
P2: A timed rotation maneuver does nothing on a ship that had an earlier timed lateral maneuverOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
scp-fs2open/fs2open.github.com#7914 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-score/inc_someip_gateway#356 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/rocksdb-js#945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day