Remove clamping from LinearToSRGB visual shader node. #113956
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
This was referenced Dec 12, 2025
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.
I've also updated related docs and moved clamping outside of other
linear_to_srgbfunctions to stop the spread of unnecessary clamping to other parts of the code and prevent this sort of issue from happening again in the future.This PR may affect existing projects that depend on this clamping. To achieve the existing behaviour after this PR is merged, simply use the existing
Clampvisual shader node to clamp to the range of [0, 1].Note: the HDR output PR will remove clamping from the SMAA shader, but since this change is only needed by the HDR output PR, I'm leaving the behaviour as-is in this PR.