Repository navigation
Render only the latest pending tracking frame per scene - #45
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
WebSocket data currently mutates Three.js objects immediately for every received tracking frame, even when several network frames arrive between display refreshes. Those intermediate state frames can never be presented and only add CPU/GC work.
Changes
Result
Application-side buffering is bounded to one pending frame per scene, and visual state naturally follows the freshest available tracking frame without building a FIFO backlog.
Scope
This intentionally stays in the ThreeJS example/viewer rather than changing the transport-independent JS SDK. Setup/control messages remain immediate. No protocol, polling or compression behavior is changed.