Blender 4.0 support #347
Draft
Blender 4.0 support #347
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
|
Thanks a lot for your work already. |
|
The author already stated that some of the nodes have changed between Blender 3 and Blender 4. So if the node names or API have change, you should not expect it to be backward compatible. Unless I am misunderstanding something, Blender 4 changes are not backwards compatible. |
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.
Description
Rename some nodes looked at to support Blender 4.0. This is marked as a draft PR because I just went to the effort to make it work with Blender 4.0, not make it backwards compatible.
How Has This Been Tested?
A model has been created and successfully exported to URDF in Blender 4.0.
Types of changes