Symmetrize Armature should symmetrize transform of custom bone shape #91871

Closed
opened 2021-10-01 12:55:14 +02:00 by Sybren A. Stüvel · 10 comments

Status: waiting for a developer to implement this.

Team
Commissioner: @Mets
Project leader: @dr.sybren

Description
Big picture: Symmetrize Armature (manual & python docs) does not yet take the new transform parameters of custom bone shapes (fc5bf09fd8) into account.

**Status:** waiting for a developer to implement this. **Team** **Commissioner:** @Mets **Project leader:** @dr.sybren **Description** **Big picture:** *Symmetrize Armature* ([manual](https:*docs.blender.org/manual/en/dev/animation/armatures/bones/editing/symmetrize.html) & [python docs](https:*docs.blender.org/api/master/bpy.ops.armature.html#bpy.ops.armature.symmetrize)) does not yet take the new transform parameters of custom bone shapes (fc5bf09fd8) into account.
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscribers: @Mets, @dr.sybren

Added subscribers: @Mets, @dr.sybren

Added subscriber: @AquaticNightmare

Added subscriber: @AquaticNightmare
Member

Added subscriber: @PaoloAcampora

Added subscriber: @PaoloAcampora
Member

the task is not too complicated per se, perhaps there are some implications that should be discussed.

The function updateDuplicateCustomBoneShapes() looks for existing symmetric shapes. If a bone has mirrored a custom shape named "MyShape.R", and "MyShape.L" is found, the latter will be used.

What is the operator supposed to do in that case? If there is a Symmetric shape in the scene, this will likely be symmetric already.

I propose that the transforms are left untouched if a shape for the mirrorred side is found.

Also, I wonder if we should have a boolean or even an enumerator property:

Boolean proposal:
- Symmetrize Custom Shape Transform:
- False: Old Behaviour
- True: Symmetrize (If no symmetric shape is found)

Enum proposal:
- No Shape Simmetry
- Symmetrize Same Shape
- Symmetrize Always

Would that be useful, or are we ok with silently symmetrizing same shapes?

the task is not too complicated per se, perhaps there are some implications that should be discussed. The function *updateDuplicateCustomBoneShapes()* looks for existing symmetric shapes. If a bone has mirrored a custom shape named "MyShape.R", and "MyShape.L" is found, the latter will be used. What is the operator supposed to do in that case? If there is a Symmetric shape in the scene, this will likely be symmetric already. I propose that the transforms are left untouched if a shape for the mirrorred side is found. Also, I wonder if we should have a boolean or even an enumerator property: Boolean proposal: - Symmetrize Custom Shape Transform: - False: Old Behaviour - True: Symmetrize (If no symmetric shape is found) Enum proposal: - No Shape Simmetry - Symmetrize Same Shape - Symmetrize Always Would that be useful, or are we ok with silently symmetrizing same shapes?
Member

Uploaded a diff [here (D13416)](https://developer.blender.org/D13416)

Uploaded a diff [here ([D13416](https://archive.blender.org/developer/D13416))](https://developer.blender.org/D13416)
Author
Member

@PaoloAcampora or @Mets do you have an example file with non-symmetrical custom shapes that gets symmetrized correctly with D13416?

@PaoloAcampora or @Mets do you have an example file with non-symmetrical custom shapes that gets symmetrized correctly with [D13416](https://archive.blender.org/developer/D13416)?
Member
Hi @dr.sybren, Demeter jas uploaded a .blend with four possible scenarios on diff page, is that good? https://dev-files.blender.org/file/download/5ctpllqpn232spfp3qsj/PHID-FILE-a5j6ybnjjaltnpitdxy5/symmetrize_custom_shape_transform_test3.blend

This issue was referenced by 452a7f6731

This issue was referenced by 452a7f673190e5161c96ec8a53631a1c89d127b9
Author
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sybren A. Stüvel self-assigned this 2022-02-08 18:12:10 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#91871
No description provided.