-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix wayland capture on nvidia #649
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
Conversation
Your PR was set to |
Thanks for the PR! There seems to be an issue with your commits. It looks like they were not made by an actual github user. You might have a problem with your git configuration? Also, you probably want to cleanup the git history if you know how. Otherwise, it's best to start with a clean copy of our |
5dcf17f
to
9e4f288
Compare
Rebased on nightly and signed the cla. I still don't know exactly why this fixes the error, but hopefully it's useful. |
Thank you! The Windows error is not related to this change. All our builds are failing right now with that. |
afe27cc
to
cc481c0
Compare
cc481c0
to
70e8be9
Compare
…y_ram_t" This reverts commit ebe01ce. Looks like this commit undos the fix for LizardByte#649, in PR LizardByte#884.
…y_ram_t" This reverts commit ebe01ce. Looks like this commit undos the fix for LizardByte#453, see also PRs LizardByte#649 and LizardByte#884. This also adds a comment so hopefully it doesn't get removed again in the future (or a proper fix is found).
…y_ram_t" This reverts commit ebe01ce. Looks like this commit undos the fix for LizardByte#453, see also PRs LizardByte#649 and LizardByte#884. This also adds a comment so hopefully it doesn't get removed again in the future (or a proper fix is found).
…y_ram_t" This reverts commit ebe01ce. Looks like this commit undos the fix for LizardByte#453, see also PRs LizardByte#649 and LizardByte#884. This also adds a comment so hopefully it doesn't get removed again in the future (or a proper fix is found).
…y_ram_t" This reverts commit ebe01ce. Looks like this commit undos the fix for LizardByte#453, see also PRs LizardByte#649 and LizardByte#884. This also adds a comment so hopefully it doesn't get removed again in the future (or a proper fix is found).
Description
When using Sway on a Nvidia device, the following error occurs: https://discord.com/channels/804382334370578482/1053022079039058001
To summarize, moonlight displays a black screen after connecting and an opengl error is printed to the sunshine logs. The logs are here: https://gist.github.com/jhgarner/5627b7e48aae7f8b1d9744e3f9011f11
I can consistently reproduce and fix the issue by compiling with and without the code in this branch, but I can't explain why this code fixes it. As far as I can tell, this is just debug logging. My guess is that it's forcing the driver to actually flush parts of the command buffer? Swapping the code out with a glFinish call doesn't fix it though. Maybe Nvidia is just broken?
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.