revert(cockpit): no water read timeout, and loaded reads not raise-only

Both reviews of the timeout found that Cesium cannot cancel a full-detail
read: each one given up kept its nine picks traversing every frame, so
stalled tiles piled up a new set every 30 s, while slow but valid answers
were dropped. Raise-only loaded reads then locked in a wrong-high height.
Back to one full-detail read at a time whose answer always applies, and
loaded reads that may adjust a river height but never take it to the sea;
a coarse probe can again lower it partway until the full read lands.

Keeps the test for another ship selected inside the double-click memory,
and corrects CURRENT-STATE: a failed read keeps the height it had.
This commit is contained in:
Sameh Khamis committed 2026-11-08 14:09:18 -08:00
1 parent 1bc4f980e0
commit 1b9bb844e6
4 files changed
+18 -96

No files matched your search

-7
View File
@@ -38,13 +38,6 @@ export const VESSEL_WATERLINE_PROBE_COUNT = 8;
/** How often the bridge reads the water under its ship again, ms. */
export const VESSEL_WATERLINE_REFRESH_MS = 5000;
/**
* A full-detail water read still running after this long is given up and
* a fresh one started, ms: tile requests can stall, and one read that never
* lands would otherwise hold the height for the rest of the bridge.
*/
export const VESSEL_WATERLINE_READ_TIMEOUT_MS = 30000;
/** A surface less than this above sea level is the sea itself, metres. */
export const VESSEL_WATERLINE_MIN_RISE_M = 2;