jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(simulation): fix stale 2048×1024 heightmap resolution in loader docstring (#963)

Browse Source 
The heightmap.rs module docstring still said 'canonically 2048×1024' (the
pre-decision figure); the canonical resolution is 1024×512 (D-202 amended).
Clerk caught the contradiction. Now consistent across D-200/201/202/208 + code.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-05-23 09:26:01 +02:00
co-authored by Claude Opus 4.7
parent 2c6621ac25
commit 6334b0ddbe
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/src/atlas/heightmap.rs
+6 -5
View File
@@ -4,11 +4,12 @@
//! **16-bit grayscale `heightmap.png`** stored next to the color `reliefmap.png`
//! in the body's wiki directory (path from `bodies.terrain_reference`). The
//! grayscale luminance is the normalized elevation; this is the single source
//! of truth — no `systems.db` BLOB. The file is high-resolution (canonically
//! 2048×1024) so the lower cascade layers (region/block/tile) have real local
//! detail; **Layer 1** (continental drainage/basins/mountain-ranges) calls
//! [`BodyHeightmap::downsample`] to `GRID_W × GRID_H` first, decoupling the
//! continental compute cost from the stored resolution.
//! of truth — no `systems.db` BLOB. The file is canonically 1024×512 (D-202
//! amended): native elevation detail for the lower cascade layers
//! (region/block/tile), while **Layer 1** (continental drainage/basins/
//! mountain-ranges) calls [`BodyHeightmap::downsample`] to the
//! `GRID_W × GRID_H = 512×256` working grid first, decoupling continental
//! compute cost from the stored resolution.
//!
//! Elevation values are normalized to [0.0, 1.0]. `sea_level` is body metadata
//! (carried alongside, not in the PNG) below which terrain is ocean.