Once triggered, the viewer must gather geometric and texture data.
Date: October 26, 2023 Subject: Real-Time Rendering Pipelines / Computer Vision Infrastructure Type: Technical White Paper viewerframe mode refresh work
When switching from manual to continuous mode while paused on a non-first frame, the viewer does not automatically refresh that current frame before starting the loop. The result is a brief stale display (1–2 frames into playback).
Severity: Medium Once triggered, the viewer must gather geometric and
Modern ViewerFrame implementations often utilize a hybrid. The viewer sits in a low-power "Refresh" state. When an input event occurs (camera pan, object transform), it temporarily enters "Motion" mode for a few frames to smooth the transition, before returning to an idle state. When switching from manual to continuous mode while
Refresh is the act of updating the ViewerFrame’s contents. A refresh can be:
In continuous mode, the refresh loop runs as fast as the event queue allows, often exceeding the display’s vertical sync. This causes tearing and unnecessary CPU/GPU load.
Severity: Low (performance, not correctness)