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.
Link to armory3d/armsdk#64.
Blender 3.6 LTS was released yesterday; luckily this time there were almost no breaking changes, so this PR is quite small:
Mix
node that replaces theMix RGB
node (closes Blender 3.4 Mix Color Node support #2821).In the 3.6 project, I also added some optional tasks that need some more research (the Blender release notes are rather sparse in those cases), but these aren't important at the moment.
Unfortunately, Blender now initializes the name of new custom node trees to the
bl_label
of the node tree/node editor (Blender commit). In our case this calls new node treesLogic Node Editor
, which is not only semantically wrong but also conflicts with Haxe naming and thus raises a warning a laIt might be possible to listen for tree creation events and then quickly rename them, I will try to find a workaround in the next days but it could be impossible...