Files
gods-eye-view/changelog.d/1555-navara-globe-engine.md
T
German Khokhlov 371d848eec Delete dead render code and consolidate QA helpers
Remove code that nothing in the app, the runners or CI uses:
- the one-off migration compare, look and bench scripts and the vector
  ground prototype they measured, with the bench tables in the docs;
- the unused Navara-named shared render modules (polygons, ground picks,
  mover bank, ground ring);
- the Cesium-shaped aircraft and vessel test renderers, and the trail,
  engineFromViewer and horizon-occluder helpers only they kept alive.
  Their tests now run on the production displays over the fake engine;
- Navara's unread diagnostics, fallback ports, dead exports and
  parameters, stale effect-chain anchors and the unread capability flags.

The QA scripts share one keyless guard and readiness wait, the session
harness reuses the strict harness's browser flags and block list, and the
harness honours QA_ANGLE and QA_RESERVED_PORTS. The bikeshare fixture
keeps only what its scenario reads. The docs name the engine picker where
it is (VISUAL PRESETS) and drop dated run results.

No behaviour changes on either engine. Navara layer renderer lines fall
from 189 to 0 and viewer lines from 891 to 849.
2026-11-08 17:05:38 +04:00

691 B

  • Add Navara, an experimental three.js/WASM globe, as a second engine next to Cesium, switchable live under VISUAL PRESETS → Globe Engine or with ?engine=navara. Navara draws at CSS pixels like Cesium; Navara HD (?engine=navara-hd) draws at the screen's full resolution and needs about 1 GiB more on a Retina screen. Layers keep their data across a switch and draw on both engines; Cesium loads only when a Cesium globe or a Cesium-only feature needs it (German, @gekh, #1555).
  • Keep the cockpit camera steady near the ground: it no longer jumps up and down when an aircraft's reported altitude sits below the globe's terrain, on either engine (German, @gekh, #1555).