Hi all,
I have been noticing what looks like a timer sync issue in Zwift for quite a while and wanted to see if others can reproduce it.
Steps to reproduce:
- Start a ride.
- Trigger a Coffee Stop (3 minute timer starts).
- After the Coffee Stop has already started, trigger a Split Lap timer.
- Watch both timers.
Expected behaviour:
Since the Split Lap timer was started after the Coffee Stop, it should always remain behind the Coffee Stop countdown.
Actual behaviour:
The Split Lap timer reaches the 3 minute mark before the Coffee Stop timer finishes, even though it started later.
In other words, the Coffee Stop countdown appears to be running slightly slower than elapsed ride timers. It is subtle, but over a 3-minute Coffee Stop it becomes obvious enough that a timer started afterwards overtakes it.
I have noticed this consistently over time rather than as a one-off occurrence.
Questions:
- Has anyone else seen this?
- Is Coffee Stop intentionally using a different timing mechanism/server sync?
- Could it be related to frame rate, game speed, or pause logic?
I am happy to try and capture a video if needed, but it seems reproducible.