Fix glslscale bug when binding a framebuffer before gl_swap_buffers. #425
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.
Using the Intel HD Graphics 2500 driver for Windows 10 and possibly some other old graphics drivers (the SDL documentation cites macOS), swapping to a framebuffer other than 0 prior to calling SDL_GL_SwapWindow can cause the screen to flicker or not display at all. This was occurring in the GLSL renderer, though for some reason only with
glslscale
(and notglsl
).