fix(win): Windows.Graphics.Capture API frame rate capped at 60fps #4424
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
StringWeaver
changed the title
Bundle ReportBundle size has no change ✅ |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4424 +/- ##
==========================================
- Coverage 14.23% 14.22% -0.02%
==========================================
Files 89 89
Lines 18936 18942 +6
Branches 8677 8682 +5
==========================================
- Hits 2696 2694 -2
- Misses 12963 15237 +2274
+ Partials 3277 1011 -2266
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Typically Windows Gaphics Capture API has a lower latency and better compatibility with DLSS-FG than Desktop Duplication API, but capped at 60 fps due to some internal limitation.
I fixed it by calling MinUpdateInterval(), like many other GitHub projects. I tested it on my computer and comfirm it can let frame capture running at 120Hz(which is my client setting)
Test environment: Windows 11 Version 26200.6584
Screenshot
Before:
After:
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage