* Lines can fade with the age of their points, drawn by the renderer on the GPU
A LineItem's ageFade gives each position a time, a window and floors; the
renderer fades the line's alpha (and optionally its width) by each point's
recency on the scene clock, so a moving trail is not re-sent each frame.
Capability lineAgeFade; the Cesium port draws it in its line materials from a
small float texture of the points' times and a per-frame uniform, and the
conformance check draw.lines.ageFade pins it.
* Changelog for line age fade (#1892)
* fix(voice): a selection steps a docked assistant panel down so Context shows; the panel keeps the last reply
A voice or chat action that selects an entity (select_nearest_aircraft,
track_entity) now minimizes a voice or chat panel docked in the right rail's
lane, so the rail and its Context panel show as after a click. The voice
card inside the panel no longer hides 14 s after its last update: the reply
stays until the next turn, Stop or a dismissal. The floating card keeps its
idle deadline.
* fix(voice): a voice or chat selection opens its card in the Context panel
A successful select_nearest_aircraft or track_entity now selects the entity
in the Context panel's entity card store the same way a click does, so the
panel opens on its details; the docked assistant panel then steps down so it
shows. track_entity reports the id it tracked. Nothing opens in Cockpit,
where Context is hidden.
* fix(voice): a slow selection never replaces a card picked since; Cockpit is read from its own state
The entity card store counts selections and clears. A voice or chat
selection notes that count when it is asked and opens its card only if no
other card was picked or cleared before it finished. Whether Cockpit is
running is read from the style manager's Cockpit state when it has one.
* Add the changelog entry
* fix(voice): the app hands voice its Context card opener
The voice package no longer imports the entity card store. The app builds
the opener (createContextCardOpener) and passes it to the voice commands as
contextCard, which keeps the voice package inside its own boundary.
* fix(voice): voice Cockpit entry no longer turns Contacts on
Voice entry now changes no Context mode or detection setting, as the COCKPIT
button does not. An entry that names a layer or class searches that layer's
own aircraft, nearest first from the followed aircraft or the ground under
the camera, and follows the nearest match before entering; the followed
aircraft counts when it matches. A military request while Military Flights
is off switches that layer on as a plain layer. The class filter is shared
with Contacts navigation.
* fix(voice): a military Cockpit entry waits for the layer's first data and leaves no layer behind
A military entry that switched Military Flights on waits for that layer to
report its first data before searching it, bounded by that update, the
layer failing or going off, and the request's cancellation. If entry then
fails, the layer is switched off again; a layer that was already on stays
on. The search covers only the aircraft the person's filters show.
* Add the changelog entry
* Show JTWC warnings in Cyclone advisories
Cyclone advisories now also read the Joint Typhoon Warning Center (keyless,
public domain) for the western North Pacific, North Indian Ocean and Southern
Hemisphere, beside NHC and CPHC.
- server/providers/jtwc.js reads JTWC's warnings feed, each storm's JMV 3.0
warning (.tcw) and its overlay (.kmz). /api/cyclones merges them with NHC's:
one storm per id, NHC's advisory where NHC lists the storm. A failed JTWC
read keeps its last storms, marked stale, and never hides NHC's.
- Storms carry an agency. A JTWC warning has no cone; its 34-knot wind danger
area is drawn as its own dashed area and named for the selected storm.
- A JTWC storm's card notes that the regional centre's warning is official
and that JTWC winds are 1-minute averages. Source and coverage wording names
both agencies.
- Each storm is served while its own advisory is usable (12 hours for NHC,
13 for JTWC).
* Keep one JTWC failure from affecting other storms or NHC
- A storm whose JTWC warning cannot be read or parsed is left out and the
others are shown; the read fails only when every listed storm's does.
- JTWC is read under its own 8-second deadline. A failed or slow JTWC read
keeps JTWC's last good storms and never delays, fails or stales the NHC
answer.
- Danger-swath longitudes past ±180 (a ring crossing the antimeridian) are
wrapped into -180..180 instead of dropping the ring.
* Add the changelog entry for JTWC cyclones
Main's Street View budget tests in the media feed-type file now mount the
provider through the shared CCTV test harness, which also resets the Google
rate-limit setting.
An interactive overlay entry is a card that takes every click from what is
drawn under it, so a base's label kept an aircraft or vessel under it from
being selected. The labels are no longer interactive entries. The layer
claims a click on a label box through the pick registry's click claim, as
CCTV counts do, only where nothing another layer draws is under it; over
the map or the layer's own dots and fills the label takes it, and another
layer's card painted over the label keeps its click. The label box is read
from the box the overlay painted for it (overlayHost.paintRect).
Conflicts: the locale catalogs and package boundaries are three-way merges
(no message changed differently on both sides); zh-Hant is regenerated
from zh-CN. bhoteKoshiEmbeddedMedia.js keeps main's card counter and the
branch's shared YouTube loader (youtubeApi.js), so the media file builds
one script element fewer. The Cockpit briefing's LIVE tab and the orbital
NADIR/RESET button are main's UiButton.
The picker no longer keeps a hidden, disabled copy of the opening camera.
That copy could be re-picked with ArrowDown on a closed list, could show
twice in the iOS picker, and left Firefox without an accessible value.
The list now selects the camera's own option, as before. A native list
sends no change for the option it already shows, so FOCUS (or NEAREST,
when that camera is the nearest) keeps the shown camera. Closing the list
without a choice keeps automatic selection.
/frame now keeps a pullable HLS camera's shared health, so a viewer
refused for capacity saw its placeholder or Street View frame under the
live row's LIVE · OK badge and "Live HLS connected". When a video camera
is shown on its frame fallback while the row says live, the panel badge
now reads FALLBACK · DEGRADED and the meta line drops the live message;
the shared row stays as it is for the other viewers.
A viewer refused for capacity falls back to /frame after hls.js gives up.
For a pullable HLS camera without a snapshot, /frame only has a
placeholder or a Street View frame, which says nothing about the stream,
yet it wrote degraded over the health that /media owns. /frame now
leaves that health as it is; a dead upstream is still reported through
/media.
Tests: the middleware suite covers both fallbacks, a real upstream
failure that still degrades, and cross-site segment and release refusals
on a live HLS lease; capacity checks use HLS_LIMITS and HlsCapacityError;
the three CCTV suites share one provider harness in src/testSupport.
CURRENT-STATE and the changelog fragment describe the refusal.
The centred Display/Radio row now applies only inside the phone shell
(720 px and below) on flight and bridge views; satellite and provider
cockpits, narrow short windows (under 390x450) and very short windows
(under 240 px) keep main's right-anchored place, so the row no longer
lands on the desktop rail, orbital zoom, LOOK AHEAD, Reset or the Stories
button. The row sizes to its launchers instead of spanning the width.
The first-visit Stories announcement stays hidden and unread while
Cockpit is open: a Stories tap that Cockpit refuses no longer marks it
seen, so it shows again after Exit.
The unit tests and the Cockpit QA cover the phone boundary, glyph and
side taps, the destination cue, short and narrow windows and the
announcement's return.
- The /frame handler reads the client's network key (IPv6 /64) before it
awaits the camera, so a client that drops the connection is still
charged to its own window instead of the shared fallback key.
- The budget is charged only after the Google key and finite catalog
coordinates are confirmed, and the key is read once.
- Places and the CCTV window share one default (GOOGLE_DEFAULT_PER_MIN).
- Tests: the catalog-only test checks heading/fov/pitch from the query at
the catalog location; the budget test covers unknown ids, forwarded
requests and /64 grouping; a real-socket test covers a dropped
connection. The duplicate pose test is removed.
- .env.example, SECURITY.md, CURRENT-STATE and the changelog fragment
describe the separate per-IP window, the catalog position and the
placeholder for seed cameras.