-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: drop advertised resolutions and fps #2924
feat!: drop advertised resolutions and fps #2924
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2924 +/- ##
=========================================
+ Coverage 9.65% 9.67% +0.01%
=========================================
Files 97 97
Lines 17557 17526 -31
Branches 8230 8199 -31
=========================================
Hits 1696 1696
+ Misses 12998 12993 -5
+ Partials 2863 2837 -26
Flags with carried forward coverage won't be shown. Click here to find out more.
|
I tried to ignore display modes and didn't see any problem. |
Switch client still rely on it, will try to add required changes in near future |
Wii U uses @mariotaku's modified libgamestream, which still parses the supported modes. I'm not sure if this will fail, if the server doesn't respond with them. I'll have to test this later. |
Moonlight UWP does work as expected with this version of Sunshine. My libgamestream is derived from the moonlight-embedded one btw, but the app never checked the supported resolutions. |
I've made all necessary modifications, Moonlight-Switch v1.2.0 release should works fine without screen modes list |
b4e43b8
to
efd6071
Compare
efd6071
to
d9a3c22
Compare
This reverts commit 04df80f.
Description
Drop support for advertised resolutions and fps. Any clients still using this?
Moonlight maintainers, please verify this doesn't break any of your clients.
Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.