Fix for vr rendering not taking render target size into account. fixes #2420 #2424
Conversation
This file contains 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
FireFlyForLife
changed the title
raysan5
reviewed
Apr 23, 2022
|
@FireFlyForLife After further review I'm merging this fix for now. Current FBO data should be provided to RLGL in some way, I'll investigate it further... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I tried to find a way to fix the issue without breaking an existing API. I think the current solution fits that criteria.
I needed to comment in the
distortionScale, to keep the example's "vignette" effect. To my eyes the final image looks the same as the previous version.