A Live Cam's map was blank and its score frozen at 1000 while the gauge
canvas underneath was being drawn perfectly - 50 static entities and one
mover, every sample, centre tracking the camera. The trace that settled it
found zero "map copy running" lines against that: the canvas was alive and
simply never reached the pane.
SVGA16::Update services one display per call and steps mDisplayToUpdate at
the END of the function. Both of its early bails returned before ever
getting there. A camera's cameraInit page configures the secondary port
and nothing else - no auxUL2, auxC, auxUR2, auxLL or auxLR - so the MFD
branch could never be serviced, and the first time the counter landed on
an MFD slot it stopped dead. Display 0's copy is the map, so it ran once,
early, and never again. The pane kept that one frame for the whole race: a
blank map, because nothing had registered with the renderer that early,
and a score showing its opening value. "It had name and score at the start
of the mission" was the tell, and it was accurate.
Both bails now step the rotation on the way out, so the sweep moves past a
display it cannot service instead of parking on it. A station with no MFDs
therefore copies its secondary every third call, which is the same cadence
a pod gets.
Pod regression: the map copy still runs every pass at the same ~9900 lit
pixels as before. A pod has all five MFD ports and never takes either
bail, so that path is untouched.
Three wrong diagnoses preceded this one - the gauge page, the renderer
link, and a snapshot theory - and each died to a measurement rather than
an argument. The trace that found it was worth more than any of them.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
7a3b117f61