Wire M10.7b interpolation and the stale loss view into the client
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m27s
Foundation / checks (network) (push) Successful in 12m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 25m13s
Foundation / checks (postgres) (push) Canceled after 12m48s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m27s
Foundation / checks (network) (push) Successful in 12m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 25m13s
Foundation / checks (postgres) (push) Canceled after 12m48s
ADR-0095. The engineering client times presentation with the tick clock: its own marker between ticks, other markers interpolated a few ticks behind (grey when stale). Silence beyond 3 ticks and long-gap holds are stale. A lost session leaves its last view frozen and labelled stale until the reconnect's fresh baseline; nothing is predicted or sent meanwhile. evo-motion-trace --remote measures remote-marker error between two clients through the relay, with a 1.5 s outage (motion-trace-remote-smoke CTest). Prediction errors are recorded only for ticks inputs are scheduled for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -35,7 +35,10 @@ evo-client --connect void.aeternalisgames.com:7400 --server-name NAME --ca dev-c
|
||||
are blue), an engineering experiment, not an organism (ADR-0094). It is predicted
|
||||
locally and corrected by the server; the camera follows it until you pan or zoom.
|
||||
The Session panel lists each intention as sent, admitted, rejected, simulated (final;
|
||||
intentions are never durable) or unknown, plus the prediction figures.
|
||||
intentions are never durable) or unknown, plus the prediction figures. Other players'
|
||||
markers are shown a few ticks in the past, interpolated (ADR-0095); grey means stale.
|
||||
- If the connection is lost, the last view stays on screen, frozen and labelled STALE,
|
||||
until the reconnect brings a fresh view. Nothing you press is sent meanwhile.
|
||||
- Each reconnect uses the next grant. A second client with a bundle for the same account
|
||||
takes the session over; the first stops (do not share bundles).
|
||||
- A server on an older session protocol (v1, v2) refuses the client
|
||||
|
||||
@@ -62,3 +62,45 @@ row: 95.9-98.3 % exact, resync 2,241-2,248 ms.
|
||||
- Many clients at once (10.8).
|
||||
- Real links (dev route); deferred until a v3 server is deployed.
|
||||
- Sub-tick presentation: the marker steps at 20 Hz.
|
||||
|
||||
## M10.7b remote interpolation (2026-10-06, ADR-0095)
|
||||
`evo-motion-trace --remote`. Two clients, each behind its own relay with the profile's
|
||||
impairment. A moves with the script; B shows A's marker interpolated. Every 10 ms B's
|
||||
presented position is compared with A's authoritative path, interpolated linearly at B's
|
||||
render tick (clock minus delay). Midway through the 20 s, B's link is cut for 1.5 s
|
||||
(outage). "Current" excludes markers shown as stale.
|
||||
|
||||
| Profile | Samples | p99 mm (all) | max mm (all) | Current p99 mm | Current max mm | Extrapolated | Stale | Mean delay (ticks) | Outage shown stale | Recovered ms |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| clean | 1705 | 0 | 2,514.0 | 0 | 0 | 0 % | 0.8 % | 2.00 | 89.9 % | 156 |
|
||||
| lan | 1706 | 0 | 2,518.7 | 0 | 0 | 0 % | 0.8 % | 2.00 | 89.3 % | 160 |
|
||||
| rtt60-loss2 | 1704 | 0 | 2,598.8 | 0 | 0 | 0 % | 0.8 % | 2.00 | 89.9 % | 154 |
|
||||
| rtt120-loss2 | 1700 | 87.6 | 2,977.8 | 60.7 | 100.0 | 0 % | 2.8 % | 2.98 | 86.3 % | 510 |
|
||||
| rtt200-loss5 | 1696 | 2,811.5 | 2,862.4 | 22.0 | 83.0 | 2.5 % | 5.3 % | 2.11 | 84.2 % | 950 |
|
||||
|
||||
- Markers shown as current are within about 0.1 m of the true path at their render tick.
|
||||
Linear motion between snapshots is exact; errors come from direction changes within a
|
||||
gap.
|
||||
- The large all-sample maxima come from the long-gap rule after the outage: the
|
||||
pre-outage position is held until the first post-outage snapshot's tick. Those frames
|
||||
are flagged stale and drawn grey, never presented as current.
|
||||
- During the outage the marker is shown stale after the 150 ms grace (the clock freezes
|
||||
one tick past the last observation; silence beyond 3 ticks is stale). The ~10 % of
|
||||
outage samples that are not yet stale are that grace.
|
||||
- Recovery (the first non-stale frame after the link returns) takes 150-950 ms. It grows
|
||||
with RTT and loss: the next snapshot must arrive, and the delay must cover it.
|
||||
- Variance: in one of three smoke runs (rtt60-loss2, 8 s), 32 % of samples were
|
||||
extrapolated and 36 % stale, while current errors stayed at 0 mm. That is consistent
|
||||
with snapshot datagrams being dropped under congestion while watermarks still arrived;
|
||||
the adaptive delay rose only to 2.23 ticks on average. The other two runs matched the
|
||||
table.
|
||||
|
||||
Prediction rerun after the M10.7 changes (own marker presented between ticks; errors
|
||||
recorded only for ticks inputs are scheduled for):
|
||||
- clean: 100 % exact.
|
||||
- lan: 99.8 %.
|
||||
- rtt60-loss2: 99.5 %.
|
||||
- rtt120-loss2: 97.1 %; resync 2,500 ms.
|
||||
- rtt200-loss5: 94.2 %; max 1,293.3 mm.
|
||||
|
||||
All profiles converged.
|
||||
|
||||
Reference in New Issue
Block a user