Dropcatching Owned Engine - One Time Bug New

Latency figure doesn't refresh between consecutive runs

sofia_r 19 Mar 2026, 18:23

Once the login screen computes latency it seems to cache it for the session, so on a later drop hours after connecting the number is stale and I'm judging timing on an old value. Would want it re-measured per run.

0 comments

Sign in with your TDesk account to comment.

← Back to all posts