Repository navigation
feat(online): Show adaptive quality in the network overlay - #668
Open
tintinhamans wants to merge 18 commits into
Open
tintinhamans wants to merge 18 commits into
tintinhamans wants to merge 18 commits into
Conversation
tintinhamans
force-pushed
the
arctic/go/stack2/13-adaptive-overlay
branch
4 times, most recently
from
October 26, 2026 15:39
a02b42d to
5a9fadc
Compare
tintinhamans
force-pushed
the
arctic/go/stack2/13-adaptive-overlay
branch
from
October 28, 2026 01:47
5a9fadc to
5f2863c
Compare
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
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.
Merge after #667 and #649. The branch merges #649 into the netcode stack, so the diff against main shows both; the only new code is the last commit.
When a match stutters, the network overlay showed the connection side only, so it wasn't clear whether the network or this PC was the cause. The overlay now shows the adaptive quality state from #649 as well. The player view gets one line with the current quality level and the reason for the last step (late frames, slow frames or recovering). The developer view (Shift+F10) adds three lines: the level, fps and 1% low, this PC's own frame cost (median and p95, split into CPU and present) against the step limits and the frame deadline (vsync, fps cap or floor), how much each level saves on this machine (learned or the default), and how long until the next step down or up is allowed.
Read only, nothing about the quality decisions changes. Tested:
z_generalsbuilds.