Reorder properties in NoiseTexture2D/3D #103631
Merged
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
01d53da to
8922a2f
Compare
|
Imo noise ( definitely ) and colour ramp ( potentially) get more use than mipmap toggling . In 2d atleast |
|
Oh cool, it's doing the thing again where it won't recognize that it's been merged I'll leave it be for a bit to see if it eventually gets the hint |
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.
Closes godotengine/godot-proposals#9432
This PR reorders the properties of NoiseTexture2D and NoiseTexture3D to overall make more sense (see godotengine/godot-proposals#9432 for reasoning)
Not sure what labels this would belong to. It's a bit iffy.