Bone's Transformation constraint numbers won't be symmetrized correctly. #109275

Open
opened 2023-06-23 09:34:54 +02:00 by Yutaka Fukumoto · 5 comments

System Information
Operating system:Windows 10
Graphics card:RTX 2070

Blender Version
Broken: 3.3.1

Use this file

This will break:

  • open the blend file
  • delete the selected Left bone
  • select Right bone and symmetrize it
  • check both Right and Left bones' Transformation constraint setting. Numbers on the Left one will be messed up.

But this works:

  • delete the selected Left bone
  • go to pose mode
  • select the Right bone
  • go to edit mode again and symmetrize it
  • Transformation numbers are both fine.

Original description:

When Bones have Transformation constraint and are symmetrized in edit mode, its numbers are symmetrized correctly too.(Map from numbers like Location X min , Location X max and Map to numbers like Location min max etc) but if Transformation constraint's Target and Owner space are set as not Local those numbers are totally messed up and broken.

**System Information** Operating system:Windows 10 Graphics card:RTX 2070 **Blender Version** Broken: 3.3.1 [Use this file](https://projects.blender.org/attachments/89fa04b0-1941-4c49-bb2f-483fa5fb402d) This will break: - open the blend file - delete the selected Left bone - select Right bone and symmetrize it - check both Right and Left bones' Transformation constraint setting. Numbers on the Left one will be messed up. But this works: - delete the selected Left bone - go to pose mode - select the Right bone - go to edit mode again and symmetrize it - Transformation numbers are both fine. ------ Original description: When Bones have Transformation constraint and are symmetrized in edit mode, its numbers are symmetrized correctly too.(Map from numbers like Location X min , Location X max and Map to numbers like Location min max etc) but if Transformation constraint's Target and Owner space are set as not Local those numbers are totally messed up and broken.
Yutaka Fukumoto added the
Status
Needs Triage
Type
Report
Priority
Normal
labels 2023-06-23 09:34:55 +02:00
Member

Will take a look. Meanwhile it's best if you can give us a example file that replicates the issue. The constraint might not be that "intelligent" in my understanding.

Update: Unable to break the value, if you set the value to local space it still works as usual. See attached file.

Will take a look. Meanwhile it's best if you can give us a example file that replicates the issue. The constraint might not be that "intelligent" in my understanding. Update: Unable to break the value, if you set the value to local space it still works as usual. See attached file.
YimingWu added the
Interest
Modeling
label 2023-06-23 10:20:30 +02:00
YimingWu added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-06-23 10:57:09 +02:00

ok I will upload blend file and check how this glitch happens. wait a moment.

ok I will upload blend file and check how this glitch happens. wait a moment.

This will break:

  • open the blend file
  • delete the selected Left bone
  • select Right bone and symmetrize it and check both Right and Left bones' Transformation constraint setting. Numbers will be messed up.

But this works:

  • delete the selected Left bone
  • go to pose mode
  • select the Right bone
  • go to edit mode again and symmetrize it, Transformation numbers are fine.
This will break: - open the blend file - delete the selected Left bone - select Right bone and symmetrize it and check both Right and Left bones' Transformation constraint setting. Numbers will be messed up. But this works: - delete the selected Left bone - go to pose mode - select the Right bone - go to edit mode again and symmetrize it, Transformation numbers are fine.
YimingWu changed title from Bone's Transformation constraint numbers won't be symmetrized correctly when its Target and Owner space is not Local. to Bone's Transformation constraint numbers won't be symmetrized correctly. 2023-06-23 17:42:38 +02:00
YimingWu added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Information from User
labels 2023-06-23 17:44:01 +02:00
Member

Can confirm the issue. Looks could be a dirty matrix since once it came back from pose mode it worked as it should.

Can confirm the issue. Looks could be a dirty matrix since once it came back from pose mode it worked as it should.

And I found out Limit location constraint isn't symmetrized correctly.

see this picture. Above constraint setting is , if owner space is set as world, resulted numbers are incorrect.
I need to set it as local to avoid this.

And below is I set owner space as local to avoid above glitch but still result is incorrect. Values are fine but use_min_x and use_max_x state are wrong. I tried other limit constraints and limit rotation and limit scale work fine. only limit location symmetrizing is wrong.

https://i.imgur.com/sWJ2jyn.jpg

Please fix this. why don't you set owner space as local before symmetrizing?

And I found out Limit location constraint isn't symmetrized correctly. see this picture. Above constraint setting is , if owner space is set as world, resulted numbers are incorrect. I need to set it as local to avoid this. And below is I set owner space as local to avoid above glitch but still result is incorrect. Values are fine but use_min_x and use_max_x state are wrong. I tried other limit constraints and limit rotation and limit scale work fine. only limit location symmetrizing is wrong. https://i.imgur.com/sWJ2jyn.jpg Please fix this. why don't you set owner space as local before symmetrizing?
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
2 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#109275
No description provided.