rUv 6f5ac3aa5a fix(ui): clamp deltaTime to 1ms in pose-renderer FPS calc (#519 Bug 2) (#610) ...

When two render frames land in the same performance.now() tick,
`currentTime - lastFrameTime === 0`, so `fps = 1000 / 0 = Infinity`,
and `averageFps = averageFps * 0.9 + Infinity * 0.1 = Infinity` poisons
the EMA forever after a single zero-dt tick. The UI then displays
"Infinity FPS" until reload.

Floor deltaTime at 1 ms before the division. That caps displayed FPS at
1000 (far above any real render rate so the cap is never observed in
practice) but keeps the EMA finite.

Reported in #519 ("Bug 2 — FPS shows Infinity") by @kapilsoni2013 on a
3-node ESP32-S3-WROOM multi-node setup with edge-tier 1 + 2.

2026-05-17 19:16:00 -04:00

..

backend-detector.js

feat: Sensing-only UI mode with Gaussian splat visualization and Rust migration ADR

2026-02-28 14:37:29 -05:00

mock-server.js

I've successfully completed a full review of the WiFi-DensePose system, testing all functionality across every major

2025-06-09 17:13:35 +00:00

pose-renderer.js

fix(ui): clamp deltaTime to 1ms in pose-renderer FPS calc (#519 Bug 2) (#610)

2026-05-17 19:16:00 -04:00