After placing the layers at the seek's moment, the hold settles them
without the seek, so the reveal continues from where the seek put it and
a clip the moment falls in starts again from its beginning (a clip
cannot be joined partway); one the moment is past stays finished.
GEV stories never explore, carry no world time and are never live:
drop the resume play state, Jump to live, the exploring branches and
world-time arguments, the overridden play button rules, and the hidden
rail and fill. The legend reads a plain field instead of a mock one.
directorSettled now tells a timeout from settlement, and on a timeout
revokes the scene's layer cleanup still in flight before Close puts the
view back.
Restores the scene picker and its selection on load, after a delete and
after an import, so PLAY and NEXT work after a reload. Open in GEV
selecting a shot and NEW SCENE stay as they are.
Pressing Live while a timed snapshot load was in flight left the live poll
waiting on that load. The live poll returned early, so the map showed no
vessels until the next refresh. The live poll now drops a timed load still
in flight, and loadAt shares the same dropLoad helper.
startScene takes fromProgress and starts partway into a shot: the camera
goes on along the rest of the flight, the hold waits only what is left
and the scene clock carries on from the same point.
- On GEV's phone layout, where neither the style readout nor the account
avatar shows, the Stories button goes icon-only under the corner-actions
column instead of covering the top row of icon buttons.
- Explore frames its start view and a picked story in the middle of the
map it leaves visible (beside the feed, above the phone sheet), with one
short correction if that area moved during the flight.
- The share icon stays visible in icon-only header buttons.
- A world clock nothing moved while Stories was open (no jump, same mode
and rate) is left alone on Close.
- Card images use the globe's own Esri tile URL; the credit list keeps the
application's full-screen placement on phones.
- Tests cover the live and playing clock restores, the clock coming back
after the share state, the tile-settling hold being released (settled,
10 s, Close), the visible-map aim, and the near-end Play fix in the
director's real order. One changelog fragment covers the PR.
Focused follow-up to manjunath22466's Stories contribution.
A paused share link in the final 250 ms is not a completed scene.
Add node:test coverage for near-end Play and true-end replay; update
current-state documentation and the #1724 changelog fragment.
Main now keeps Cesium behind the renderer contract, so Stories stops
reaching Cesium and the viewer directly.
- Camera: flights, the -60 degree story framing, cancel, the pose saved
on open and put back on Close go through the camera port; a follow is
released with stopFollowing.
- Pins: placed in the frame port's postRender from the query port's
projection and horizon test, still written straight to each pin's
transform on every drawn frame.
- Tile settling: a continuous-render hold until the globe port reports
the base settled, for at most 10 s.
- Clock: Close and Back to Explore put back the page's world clock (live,
or the time it showed, playing on), and leave a clock that is still
where it should be alone.
- Card images: drawn from Esri World Imagery's own Web Mercator tiles
while the Esri map stack is active, read as images; no Cesium imagery
provider is touched.
- THUMBNAIL: the director hands captureStoryThumb the frame port and the
renderer's canvas, so the scene document's module stays renderer-free.
- Credits: Stories places and keeps visible the application's credit
line (#gev-credits) and its list as well as the renderer's own display.
- Tests fake the ports instead of a Cesium viewer, and cover pins per
frame, the flights, the settling bound and the clock restore; the
share link tests Stories added build their manager over a camera port.
A Stories button (top right) opens Explore: a feed of GEV scenes over
GEV's own Cesium globe, with a pin per story. Explore opens at country
level over the first story and, while idle, flies on from story to story
for a minute. A picked story is framed in the middle of the view; a pin
plays its story on a second click. The Story page plays the scene through
SceneDirector with a timeline, chapters, key moments, sources and
background, then Close (or Back) puts the person's camera, clock, layers,
style and AUTHORING selection back. Open in GEV hands the scene to the
Scenes panel at its current shot.
Stories lists the scenes GEV ships with a camera path (while they are in
the project), the scenes saved with SAVE TO STORIES in AUTHORING, and the
person's other scenes as drafts. The person's own stories live in the
project on this device, so they have no Share; a link to a story that is
not here opens Explore and says so. Each shipped story's
context comes from what GEV knows: what it shows, the place each shot goes,
and each layer's data sources as DATA_SOURCES.md lists them; the Nepal
story carries the event pack's facts and CC BY-NC sources. Card images are
a captured THUMBNAIL or drawn from the keyless Esri World Imagery.
AUTHORING has no scene picker: it starts with no scene, NEW SCENE (or
CAPTURE SHOT) makes one, and Stories' Open in GEV selects one. Before SAVE
TO STORIES it offers topic tags and THUMBNAIL. A scene's stories flag,
storyThumb and storyTags are saved with the project and kept through
export and import.
Only the closed state loads with the page; the screens, styles, story data
and controller load on first open. Stories keeps its place in the query
(one history entry per screen) and holds the share link's hash writes
while open. Keyboard input and voice tools stay with Stories while it is
open. Explore's pins move on every drawn frame without asking for frames;
the idle tour and tile settling are bounded.
All strings are translated in the 13 locales.
While the timeline plays or is scrubbed, each vessel icon is handed to the
renderer as a motion segment along its track (a straight piece of at most
10 km between two fixes, on the scene clock), as aircraft already are. The
layer writes an icon again only when its segment runs out or the time
moves back before it, instead of moving every icon on the CPU every frame.
Behaviour is kept:
- Icons follow the same great-circle track between fixes (a 10 km chord
stays within 2 m of it) with the same course.
- A vessel still appears TIMELINE_UNSEEN_MS before its first fix and
hides again when the time moves back before that.
- Cards, the selected vessel, ship models and the vessel the bridge camera
rides are read where they are every frame; the rest within
HIDDEN_FOLLOW_MS, as before.
- Position reads (getAllPositions, getNearby, the focus pass, the
detection overlay, single-vessel lookups) return where the icon is drawn
at the world time.
- Going live, each icon holds where its segment last drew it, unless a
live update has drawn it since.
- Trails are unchanged: they are built from the feed's fixes, not from the
per-frame position.
- Live mode and renderers without the motionSegments capability take the
previous path unchanged.
On Node 26 the engine inlined the projection pass's helpers in another order and left distanceScale out, so every label's paint scale allocated a number: 158 B per candidate per frame against the 154 B budget, where main measures 136 B. The curve now sits beside the altitude curve in snapshotAndProject, with the same arithmetic.
Grounded aircraft turn 3D on the first settled frame: streaming tiles are not a miss. groundSnap's tests keep main's cases against the branch's query port; trackedModelForm.test.mjs (the branch's form of trackedModelRegime.test.mjs) takes main's edits.
Turning CONTACTS on with a vessel selected made the nearest flight to the view the subject and followed it. The selected vessel is now adopted as if it had been selected while CONTACTS was on; a followed flight still comes first, and with nothing selected the nearest flight is still focused.
- Scratch and marker positions are a Cesium-free Vec3 (src/geo/vector.js), so writing a coordinate does not allocate.
- The dirty set and the upsert lists are kept between frames instead of rebuilt; patchDrawnIcons reuses its lookup arrays.
- measureFrames and stopFrameProbe live in src/layers/transit/testing.js again.
- Tests: 3000 moving vehicles stay under 8 KiB per frame of layer allocation; moving 500 icons allocates under 256 B per upsert.
Tiles still streaming no longer count as a failed ground sample: they leave
the retry backoff alone and return the last measured ground, if any, so the
first tick after the tiles settle samples and hands the icon to the model.
- Clicks: when two tools want the globe's clicks, the newest takes them and the older is told and turns itself off; a click is decided when it arrives, and ambient selection fires only when no tool holds the pointer. The "map is busy" paths and their strings are removed.
- Recession: the limb fade is shared (src/render/recession.js) and reaches icon and model sets through SetSpec.recede; tuning applies on the next frame.
- Display panel groups are published through src/ui/displayGroups.js; the Weather group and src/viewWeather.js are removed.
- Draw port: a set whose icons only move is moved in place, and models that did not change are not restyled each frame, so moving fleets cost what they did when drawn directly; an untinted, fully opaque model is drawn without a colour.
- Conformance: input.lease.lost checks the new lease inside onLost and reports a throwing onLost; draw.sets.recede covers model sets.
- QA scripts read the renderer host instead of internals the seam replaced.
mergeTimelineRuns read an entry's time again on every comparison, and the
vessel layer passed a new arrow for every vessel. Times are now read once
into arrays, the leading older entries the loop would keep one by one are
sliced in one step, and the layer passes one function. The result is the
same entries in the same order; a test checks 3,000 random merges against
the previous algorithm.
Measured in the browser, one implementation per page, 9,000 vessels with
240 kept fixes each, 5 alternating pairs: 65-87 ms -> 57-61 ms per snapshot.
The label pass projects every vessel in view each time it runs. It asked
Cesium for each one, which reads the camera and allocates for every point.
createWindowProjector reads the camera's matrices and the canvas size once
and runs the same arithmetic in the same order, so the window positions are
the same numbers (a test compares them bit for bit with Cesium); outside a
3D perspective view it asks Cesium as before.
Grid cells are keyed by number, a cell's candidate is made only for its
first vessel and updated in place, and whether a name is worth a card is
kept per vessel until its name, MMSI or id changes.
Measured in the browser (perf harness, 9,000 vessels, 1 min/s): the label
pass 33 ms -> 11 ms, the forced visibility pass 42 ms -> 27 ms.
A profile of about 9,000 vessels following a playing world clock spent
~13 ms of every frame in the clock pass, moving every drawn vessel a
fraction of a pixel, and ~4 ms more re-uploading their billboards.
- Drawn vessels move again once the fastest would have moved half a pixel
on screen at the speed each last moved (measured from the world time it
was drawn at), at least once a second, and at once when the camera moves
or changes height by a tenth of its height or the view zooms. A pass that
holds them back asks for a frame, so a paused clock settles on the time.
- Hidden vessels move a share of them each pass, each within 250 ms, rather
than all of them in one frame; the visibility pass moves one coming into
view to the time first.
- A vessel's three positions are written from one surface point and normal
(Cesium's own formula) instead of three fromDegrees calls; the unused
normal is dropped. The great-circle step builds no arrays.
The pass falls from 4.6 ms to 0.37 ms a frame on average in a benchmark of
9,000 vessels (3,000 drawn) at 240 frames a second.