Allow usage of discard inside custom shader functions
#93590
+14
−2
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
Chaosus
force-pushed
the
shader_custom_func_discard
branch
3 times, most recently
from
702020a
to
3b168fb
Compare
|
Is it possible to allow access to UV / SCREEN_UV and sdf functions as well? Just ran into this. |
Chaosus
force-pushed
the
shader_custom_func_discard
branch
from
3b168fb
to
f81a720
Compare
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.
Since #93358 got merged (which introduced call hierarchy checking), it's now easily possible to allow a user to use a
discardkeyword in custom user function inspatial/canvas_itemshader types: