bug(debug-ui): frame-time and FPS graph use render-only total #1077
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital#1077
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
totalis measured fromt_realize_start, which happens after the update phase and after surface lock/acquire/view. The actual frame period is therefore approximately:But
TOTAL_STAGE_INDEXis documented as "the whole-frame duration", the debug graph labels it "frame time", andfps_values()computes1000.0 / total.Evidence
fpscolumn is correct; the graph is not.Fix direction
frame_total(update + surface_acq + totalplus event-loop overhead) and keeprender_totalif needed.totaland add separate update/render-only stages.Acceptance criteria
fpscolumn.update,surface_acq, andtotalare no longer double-counted or mislabeled.bug(debug-ui): frame-time and FPS graph exclude surface acquisitionto bug(debug-ui): frame-time and FPS graph use render-only total