fix(debug-ui): plot frame time and timer FPS #1106
No reviewers
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital!1106
Loading…
Reference in a new issue
No description provided.
Delete branch "sakulflee/fix-debug-ui-frame-time"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Fixes #1077.
cdt_ms) as frame time, instead of the renderer-onlyrender_total.totalCSV stage torender_total, and theFrameTimingshistory accessor fromframe_mstorender_ms, so their scope is explicit.render_totalis no longer treated as a whole-frame budget.Verification
cargo test -p orbital_ecs_bridge -p orbital_debug_ui -p orbital_appcargo clippy -p orbital_ecs_bridge -p orbital_debug_ui -p orbital_app --tests -- -D warningscargo fmt --all -- --checkSmart test results
Result: PASS
Scope: full workspace
Reason: unmapped change: Tools/performance/performance_report.ipynb
Elapsed: 14m 48s
Workflow run
Overall: 563 tests, 553 passed, 0 failed, 10 skipped
Nextest: 552 tests, 552 passed, 0 failed, 0 skipped
Doctests: 11 tests, 1 passed, 0 failed, 10 skipped
Outcome charts are split between nextest and doctests. The timing chart covers nextest only.