Replace the inherited one-way timing behavior with a design the engine owns: an RTT estimator that stops counting retransmission waits, the mesh-wide MaxAhead separated from the per-link retry timer, every peer publishing its worst RTT symmetrically, and a responsiveness ladder that can step back down. The multiplayer FPS-table question resolves here.
Constraints:
- All timing values are validated on receipt; the launch file never supplies timing.
References: Vinifera (spawner branch, 2b809d61) src/spawner/net/protocolzero.* - cited as the adaptive design this issue deliberately does not adopt; useful as a map of the problem space.
Replace the inherited one-way timing behavior with a design the engine owns: an RTT estimator that stops counting retransmission waits, the mesh-wide MaxAhead separated from the per-link retry timer, every peer publishing its worst RTT symmetrically, and a responsiveness ladder that can step back down. The multiplayer FPS-table question resolves here.
Constraints:
References: Vinifera (
spawnerbranch,2b809d61)src/spawner/net/protocolzero.*- cited as the adaptive design this issue deliberately does not adopt; useful as a map of the problem space.