memory: placement check results + north-buildings camera bug

This commit is contained in:
zwitschi committed 2026-11-08 14:39:18 +01:00
1 parent 15c91c344e
commit 20ff30bf77
1 file changed
+16
+16
View File
@@ -288,3 +288,19 @@ Scope: facts and traps that cost time to establish. Planned work lives in [TODO.
(2) ODbL review — recorded. The [D] Blosm-import (blockout cleaning) item stays (2) ODbL review — recorded. The [D] Blosm-import (blockout cleaning) item stays
deferred (tracked separately). deferred (tracked separately).
- Branch: odbl-review-0.1.0 (docs + TODO closure only). - Branch: odbl-review-0.1.0 (docs + TODO closure only).
## 2026-11-08 — placement release check; north-buildings camera was 9.5 km off
- Release check 2 (placement vs references): rendered demo, probed DemoMap world
positions, compared to Geo references. Matches: road 24.3 m (ref crossings
20.9-25.9), sidewalk centreline offsets 12.5/13.2 m (ref 12.6/13.6), hero
frontage 26.0 m / setback ~13 m (ref 25.75/14.5), six south-frontage buildings
+ TCL/Tussaud's in verified OSM positions.
- **Bug found:** the `demo-north-buildings` camera sat at X -22800 (the buildings'
own X), aiming at its own position -> 85%-sky screenshot. Probed real geometry:
TCL bbox X -22889..-18442, Y -9431..-1802; Tussaud's X -27071..-22799,
Y -7586..-1888; hero at X -13336, Y +1307 (frontage 26 m). Camera now at
(X -22750, Y +1600) looking north; sky fraction 85% -> 41%.
- Getting actor world bounds: spawn at loc(0,0,0) means static mesh bbox IS the
world footprint (FBX carries the geo offset). Probe by loading the level
explicitly (load_level) — a fresh commandlet starts on Untitled otherwise.