Update for Blender 5.0 compatibility and minor fixes on default Actions#87
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes for Blender 5.0 Compatibility
API Compatibility (String Bridge): Updated property definitions to ensure compatibility with Blender 5.0's stricter requirements for StringProperty and other data types.
Auto Smooth Attribute Fix: Resolved AttributeError: 'Mesh' object has no attribute 'use_auto_smooth'. This was achieved by replacing the deprecated direct mesh attribute calls with the new bpy.ops.object.shade_smooth(use_auto_smooth=True) operator system.
Storage.json Refactoring: Updated the default actions in Storage.json to utilize the new non-destructive "Smooth by Angle" logic, ensuring "Subd Smooth" and similar actions work out of the box.
Stability: Cleaned up redundant macro steps to prevent errors when objects are missing or when the API structure expects a modifier-based workflow.