On this page
timer
Interaction Lag
Tracking is correct but the response feels late. The sensor is rarely the cause.
Measure before changing anything
Touch a known point and record the interval between the physical event and the visual response. Eyeballing “feels slow” leads to tuning the wrong stage.
| Stage | Typical contribution |
|---|---|
| Sensor scan and packet emission | Tens of milliseconds at 100 Hz+ |
| Network transport | 1–5 ms on a quiet segment |
| Host application processing | Varies wildly — usually the culprit |
| Rendering / display pipeline | 1–3 frames, i.e. 16–50 ms |
Where the time actually goes
| Symptom | Likely stage |
|---|---|
| Delay grows over hours | Host application leaking frames or buffering |
| Delay constant but high | Display pipeline, or vsync on a slow refresh |
| Delay only with many targets | Host-side tracking complexity, not the sensor |
| Delay only on one machine | Network adapter offload, or an antivirus inspecting UDP |
Cheap wins
| Change | Effect |
|---|---|
| Disable frame buffering in the renderer | Removes 1–3 frames |
| Process packets on arrival, not on a timer | Removes up to one polling interval |
| Isolate the sensor VLAN | Removes retransmission delays from congestion |
| Lower the sensor frame rate | Sometimes reduces perceived lag if the host was dropping packets |
When it really is the sensor
Only if the emitted packet rate is below the configured frame rate. Check that on the wire before blaming the hardware:
tcpdump -i en0 -n udp port 10940 -c 200
Next
Acceptance criteria for latency: Interaction test.