Update material.py for blender 3.3.0 #155
Merged
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
The name of the "Separate RGB" input has changed from `Image` to `Color` in blender 3.3.0. Also support just using an image named "Glossmap" instead.
StjerneIdioten
approved these changes
Sep 19, 2022
|
🎉 This PR is included in version 4.1.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The name of the "Separate RGB" input has changed from
ImagetoColorin blender 3.3.0. Also support just using an image named "Glossmap" instead.This change is protected by a blender version check.
The "old way" that still works - using the newly renamed node "Separate Color", manually re-named to "Glossmap"
An optional "new way" - using just an Image Texture manually re-named to "Glossmap"
I've not delved deeply into 3.3 yet, but other than this, it all seems to be working correctly - only re-ran a couple quick exports to see if they appeared the same. Fwiw, been on 3.2 for a week or two prior to this, no issues found there.