David Gwilliam 73ca72d920 fix(display): correct FPS calculation in all display backends ...

BUG: FPS display showed incorrect values (e.g., >1000 when actual FPS was ~60)

ROOT CAUSE: Display backends were looking for avg_ms at the wrong level
in the stats dictionary. The PerformanceMonitor.get_stats() returns:
  {
    'frame_count': N,
    'pipeline': {'avg_ms': X, ...},
    'effects': {...}
  }

But the display backends were using:
  avg_ms = stats.get('avg_ms', 0)  # ❌ Returns 0 (not found at top level)

FIXED: All display backends now use:
  avg_ms = stats.get('pipeline', {}).get('avg_ms', 0)  # ✅ Correct path

Updated backends:
- engine/display/backends/terminal.py
- engine/display/backends/websocket.py
- engine/display/backends/sixel.py
- engine/display/backends/pygame.py
- engine/display/backends/kitty.py

Now FPS displays correctly (e.g., 60 FPS for 16.67ms avg frame time).

2026-03-16 20:03:53 -07:00

6.4 KiB

Raw Blame History

View Raw