Shaders: use matrices where possible - #2946
Merged
Merged
Conversation
lenemter
force-pushed
the
lenemter/rework-colorblindness-correction-shader
branch
from
October 3, 2026 21:33
4631c86 to
7eccb37
Compare
leolost2605
approved these changes
Oct 3, 2026
leolost2605
left a comment
leolost2605
left a comment
Member
There was a problem hiding this comment.
Don't know a lot about this but it works like before :)
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
2 participants
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'm currently looking into using lcms2 for our grayscale / colorblindness-correction shaders. ICC profiles use matrices for transformations, so while I'm here, let's just use matrices as it's cleaner than whatever we have now.