Draw transit vehicles through the renderer ports, off the Cesium list

Transit drew its vehicles into two Cesium billboard collections and culled,
turned and floored them through the Cesium scene. It now draws them as two
draw-port icon sets, still and moving, registered with the sprite order by
set id in the same places. Each marker is a plain record; a frame writes the
changed ones in one upsert per set, and markers taken out in one task go in
one removal. Clicks read the draw-port hit.

Visibility uses the query port's horizon test and the frustum planes of the
camera port's pose. Icons stay turned in screen space by an exact projection
through the query port, the same answer the Cesium helper gave. The flat
globe is told from terrain by asking the height service once per surface
change; floors are read again when the answer flips. The mesh floor sampler
sees through the layer's sets by id. The camera pose and surface version are
read once per task.

The Cesium draw port now moves and turns an icon without restyling it. The
GL upload probe moves to src/render/cesium/uploadProbe.js, which the QA
scripts hand to the frame probe; the QA scripts read the billboards drawn for
each set.
This commit is contained in:
Sameh Khamis committed 2026-11-08 21:44:22 -08:00
1 parent 00ae80908c
commit 347427f83d
24 files changed
+1618 -452

No files matched your search

+23 -7
View File
@@ -4632,12 +4632,27 @@ synchronizes visible playback before its next frame.
Playback reserves numeric scratch before the first sample, including unknown
heights, and reuses caller-owned sample and segment storage.
**Scene work.** Stationary and animated billboards use separate, adjacent
collections above CCTV and Bikeshare. Transit listens to the camera port at its
own `changed` threshold (0.05); the port measures each listener separately, so no
layer changes another's camera trigger.
Visibility checks combine the camera frustum and ellipsoid occlusion at no more
than 4 Hz; missing map bounds do not admit the globe's far side. Camera arrivals
**Scene work.** Stationary and animated vehicles are two draw-port icon sets
(`transit:<n>:still` and `transit:<n>:moving`), registered by set id with the
sprite order in their old adjacent places above CCTV and Bikeshare. Each marker
is a plain record (position, show, image, size, colour, rotation); a frame
writes the changed ones to their set in one batched upsert, markers taken out
in one task go in one removal, and a marker that starts or stops moving moves
between the sets. The renderer moves and turns an icon without restyling it.
Rotation is computed in screen space through the query port's projection
(`perspectiveCourseRotation`), as before. Clicks read the draw-port hit. The
layer no longer reaches Cesium, so a caller handing it a Cesium viewer,
their own, with no renderer bound, loads the `./render/cesium/unbound` export
once first. Transit listens to the camera port at its own `changed` threshold
(0.05); the port measures each listener separately, so no layer changes
another's camera trigger.
Visibility checks combine the camera port's frustum and the query port's
ellipsoid occlusion at no more than 4 Hz; missing map bounds do not admit the
globe's far side. Whether the globe is the bare ellipsoid is asked of the
height service at the camera's subpoint each time the globe's surface
changes; the answer comes asynchronously, the last one holds until then, and
floors are read again when it flips.
Camera arrivals
rebuild an unprepared or cold marker corridor during that visibility sweep,
adopt a loaded surface, and update both heightPending and surfaceReady diagnostics.
A resolved display sample clears its pending-height gate without waiting for a poll. Frame work
@@ -4668,7 +4683,8 @@ it does not establish Google 3D acceptance.
The full run samples completed frames at 1920×1080 CSS pixels, records DPR, and
measures moving fleets of 800 and 3,000 vehicles with 128 fixes each and DETECT
on. Street/metro targets are respectively: transit frame CPU p95 ≤1/4 ms, frame
interval p95 ≤20/25 ms, billboard uploads ≤256 KiB/1 MiB per frame, and retained
interval p95 ≤20/25 ms, billboard uploads ≤256 KiB/1 MiB per frame (counted by
`src/render/cesium/uploadProbe.js` for the two marker sets), and retained
heap growth ≤24/48 MiB. The 3,000-vehicle CPU budget is 4 ms (recorded browser
measurement 3.4 ms); the 800-vehicle budget stays at 1 ms (measured 0.9 ms).
Transit-authored frame allocation is ≤8 KiB/frame at both fleets, attributed