Repository navigation
Gamescope payload 20261026.3: FPS cap at acquire, present wait served by the shim, custom resolutions on Turnip - #2257
Conversation
…rved by the shim, and the gamenative-drm daemon that goes with it gamescope 92e30f5 and gamenative-drm master a11b500 (#19, #20, #21, #22, #23, #24). The frame cap moves from a slot's release to the swapchain acquire, so a capped game no longer throws rendered frames away; Blazing Chrome at a 60 cap went from about 85 % CPU to about 10 % on the Odin 3. The shim now advertises and serves VK_KHR_present_id / VK_KHR_present_wait on every route, so DXVK 2.x and vkd3d-proton pace to the display again under gamescope, and custom resolutions on Turnip render at the pool's row pitch instead of shearing. The daemon is rebuilt from the same tree (frame-cap note, latch reports). The payload is the 20261024.4 base with the gamescope, shim, ICD, LSFG engine and probe binaries rebuilt; no member links libandroid.so and it carries no AppleDouble entries. The archive is on the CDN.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update payload version app/src/main/java/app/gamenative/display/GamescopePayload.kt |
GamescopePayload.VERSION changes to 20261026.3. The derived archive name and readiness stamp comparison use this version. |
Priority:
Estimated code review effort: 1 (Trivial) | ~2 minutes
Change: Bug fix
Possibly related PRs
- utkarshdalal/GameNative#2247: Advances the Gamescope payload to the previous version,
20261024.4. - utkarshdalal/GameNative#2226: Defines the versioned payload archive and readiness flow.
Suggested reviewers: joshuatam
Merge Risk: 
Minimal · up to 0b889
-
No actionable merge-blocking risk is identified in this version-only update.
Pre-merge checks: 
5
-
Full details: Description check
-
Explanation
The description follows the required template and provides detailed change context, test results, caveats, change type, and checklist status. The recording is not attached, but this is a non-critical omission because the description states that it is available on request.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
|
Device results for this build (modernDebug of this branch, payload re-extracted to 20261026.3 on first launch, ICD md5 4630ea1d): Odin 3 (Adreno, wrapper/System route for Blazing Chrome, Turnip for Hades II)
Earlier passes with the same ICD on this device also covered DXVK 2.4.1, 2.6.1 and 1.10.3 (control) on the wrapper route, 2.7.1 on Turnip at 1280x720 and 1024x576, and Hades II with LSFG off at cap 30; all within 1 % of cap, no timeouts. Poco F6 (Snapdragon 8s Gen 3, Turnip, DXVK 2.4.1)
No hangs, no crashes, no one-second waits on either device. Containers restored after each run. |
Description
Gamescope payload 20261026.3 and the matching gamenative-drm daemon: gamescope 92e30f5 + gamenative-drm master a11b500 (#19 to #24).
Caveat for the
-r/present-wait design: with no cap set, FIFO does not hold the guest to the display rate under the shim, so DXVK's own limiter engages at 60.00 Hz; unchanged by this PR.Recording
Screenshots and logs from the Odin 3 and Poco F6 runs are kept locally (gn-testlogs); a recording of the 30 vs 60 cap on Blazing Chrome is available on request.
Type of Change
Checklist
#code-changes, I have discussed this change there and it has been green-lighted. If I do not have access, I have still provided clear context in this PR. If I skip both, I accept that this change may face delays in review, may not be reviewed at all, or may be closed.CONTRIBUTING.md.Summary by CodeRabbit
20261026.3. The app now uses this version when identifying the payload archive and checking whether the payload is ready. This update does not add or remove any user-facing features.