It sampled the first five sweeps, which run while the mission is still
coming up and nothing has registered with the renderer yet. So it reported
"0 static, 0 moving" on a POD, whose map demonstrably works - and I took
that reading at face value and concluded the map was broken for everyone.
It was the instrument, not the game.
Now sampled on a clock like the ranking trace, every five seconds, and the
bounds line repeats too so the centre can be seen tracking. The real
baseline from a pod race:
CamLog: nav in bounds - 0 static, 0 moving (first sample, loading)
CamLog: nav in bounds - 44 static, 1 moving (running, and stays)
44 static is the track, 1 moving is the player, and the centre walks with
the vehicle. That is what a working nav display looks like, so a camera
station can now be compared against something real rather than against a
startup artefact.
Found by putting the pod's map on screen next to its own trace, which is
what should have happened before the first conclusion.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
2adbeba6c4