fix(gl_bridge): restore old Zink vsync behavior for Kopper path#1667
Open
fis4med2 wants to merge 2 commits into
Open
fix(gl_bridge): restore old Zink vsync behavior for Kopper path#1667fis4med2 wants to merge 2 commits into
fis4med2 wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Commit 18f18fe changed the Zink renderer from OSMesa bridge to GL bridge
for Kopper support. The OSMesa bridge ignored swap intervals unless
POJAV_VSYNC_IN_ZINK was set, while the GL bridge calls eglSwapInterval
unconditionally. This causes FPS to be locked to the display refresh rate
for Zink/MobileGlues users when the game requests v