Symmetrizing armature does not symmetrize constraints #88076

Open
opened 2021-05-06 14:37:43 +02:00 by MattCROK · 9 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27

Blender Version
Broken: - version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab
- version 2.93 Beta

Short description of error
I try to constrain bones from an armature to bones from a rigify rig. Both armatures are in the world origin.
I start by constraining the bones of the left arms and legs of the rig, then I symmetrize these and once it's symmetrized, I notice that the right arms and legs are constrained to the left arms and legs of the Rigify rig.

Exact steps for others to reproduce the error
Create a rigify rig, then another rig, make the constraints on the bones and symmetrize.

PS:

  • It's not just because of Rigify, I also tested with another Rig.
  • It's not because of add-ons: I also tried to do it after I reloaded the factory settings.
**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27 **Blender Version** Broken: - version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` - version 2.93 Beta **Short description of error** I try to constrain bones from an armature to bones from a rigify rig. Both armatures are in the world origin. I start by constraining the bones of the left arms and legs of the rig, then I symmetrize these and once it's symmetrized, I notice that the right arms and legs are constrained to the left arms and legs of the Rigify rig. **Exact steps for others to reproduce the error** Create a rigify rig, then another rig, make the constraints on the bones and symmetrize. PS: - It's not just because of Rigify, I also tested with another Rig. - It's not because of add-ons: I also tried to do it after I reloaded the factory settings.
Author

Added subscriber: @MattCROK

Added subscriber: @MattCROK
Member

Added subscribers: @ZedDB, @lichtwerk

Added subscribers: @ZedDB, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Afaics, this is working with bones in the same rig, see

#88076.blend

So the issue is that we might have the case where we are constrained to an existing bone in a separate armature (and the mirrored subtarget bone in that separate armature would actually already exist -- of course we would not want to create one in that separate armature).
This then does not work, true. subtarget stays "un-mirrored".

T88076_b.blend

This seems to be intended though, code in updateDuplicateSubtarget checks if this happens in the same armature.
Dont think this is a bug, quick confirmation from @ZedDB would help.

Afaics, this is working with bones in the same rig, see [#88076.blend](https://archive.blender.org/developer/F10056461/T88076.blend) So the issue is that we might have the case where we are constrained to an existing bone in a **separate** armature (and the mirrored subtarget bone in that separate armature would actually already exist -- of course we would not want to create one in that separate armature). This then does not work, true. subtarget stays "un-mirrored". [T88076_b.blend](https://archive.blender.org/developer/F10056485/T88076_b.blend) This seems to be intended though, code in `updateDuplicateSubtarget` checks if this happens in the **same** armature. Dont think this is a bug, quick confirmation from @ZedDB would help.

As Philipp pointed out, the operator is not programmed to handle this. So it is not a bug per se.

However it sound useful to be able to do something like this, so I'll mark this as a "Known Issue".
Also marking it as such as I don't think me or any of the other core devs will have time to work on this in the coming months.

If anyone else wants to work on this, feel free do to do so :)

As Philipp pointed out, the operator is not programmed to handle this. So it is not a bug per se. However it sound useful to be able to do something like this, so I'll mark this as a "Known Issue". Also marking it as such as I don't think me or any of the other core devs will have time to work on this in the coming months. If anyone else wants to work on this, feel free do to do so :)
Author

Indeed, you're right. It's an issue only for constraints from bones from an armature to bones of another armature. I tried and it works in the same armature.
I didn't know it wasn't a bug. ^^'

But indeed, I confirm you it would be really useful to be able to symmetrize the constraints as well in that condition.

Thank's.

Indeed, you're right. It's an issue only for constraints from bones from an armature to bones of another armature. I tried and it works in the same armature. I didn't know it wasn't a bug. ^^' But indeed, I confirm you it would be really useful to be able to symmetrize the constraints as well in that condition. Thank's.
Member

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Member

Since status has been clarified by @ZedDB we dont need any more information from developers, setting to "confirmed".

Since status has been clarified by @ZedDB we dont need any more information from developers, setting to "confirmed".

Added subscriber: @KevinCurry_Unity

Added subscriber: @KevinCurry_Unity
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:35:50 +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#88076
No description provided.