Bone Override Transform affects bone local axis display. #102948

Open
opened 2022-12-05 14:04:28 +01:00 by Konstantins Visnevskis · 8 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce

Short description of error
When a bone gets assigned a display transform override, it's viewport display axis gets transformed, which probably shouldn't happen as its purpose is to display the Bone's not it's Shape's local axes.

Exact steps for others to reproduce the error
override-transform.blend

  • Remove Override Transform from Bone's Viewport Display's Custom Shape -> Displayed Bone's axes change location.
**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` **Short description of error** When a bone gets assigned a display transform override, it's viewport display axis gets transformed, which probably shouldn't happen as its purpose is to display the Bone's not it's Shape's local axes. **Exact steps for others to reproduce the error** [override-transform.blend](https://archive.blender.org/developer/F13996673/override-transform.blend) - Remove Override Transform from Bone's Viewport Display's Custom Shape -> Displayed Bone's axes change location.

Added subscriber: @KonstantinsVisnevskis

Added subscriber: @KonstantinsVisnevskis

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I'm having trouble understanding the problem.
What should the expected result be?

I tested it on 2.79 and the behavior is the same, so it works like this for a long time:
override-transform_279.blend

I'm having trouble understanding the problem. What should the expected result be? I tested it on 2.79 and the behavior is the same, so it works like this for a long time: [override-transform_279.blend](https://archive.blender.org/developer/F13998636/override-transform_279.blend)

The point of having axes displayed is to see the origins and (most often) see the Roll of the Bones. Having Bone axes indicator transformed by Custom Shape nullifies that while serving no other purpose (afaik) as there is no need to know where the origin of a visibility shape is located. Furthermore it may lead to mistakes on actual roll, if the behavior is not known to the user. I suspect this wasn't reported because Roll is usually aligned earlier than assigning Bone Shapes, as well as Bone Shape Transform Override being mostly used in rather specific cases, like hierarchy problems or script generated rigs.
The expected behavior is for the Bone axes indicator to remain where it is when there is no Custom Shape Transform.

The point of having axes displayed is to see the origins and (most often) see the Roll of the Bones. Having Bone axes indicator transformed by Custom Shape nullifies that while serving no other purpose (afaik) as there is no need to know where the origin of a visibility shape is located. Furthermore it may lead to mistakes on actual roll, if the behavior is not known to the user. I suspect this wasn't reported because Roll is usually aligned earlier than assigning Bone Shapes, as well as Bone Shape Transform Override being mostly used in rather specific cases, like hierarchy problems or script generated rigs. The expected behavior is for the Bone axes indicator to remain where it is when there is no Custom Shape Transform.

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

So you're saying that the axis should be in the region indicated in red in the image bellow?
image.png

I'm not sure if this is really the case and really a bug.

So you're saying that the axis should be in the region indicated in red in the image bellow? ![image.png](https://archive.blender.org/developer/F14001017/image.png) I'm not sure if this is really the case and really a bug.

Well, the logic of me thinking it is a bug is in assumption, that the primary goal of the indicator is to display Bone Roll. Which in turn is based on:

  • seeing Bone Roll being a basic, core functionality for rigging, and no other practical way of seeing Roll being there.
  • not knowing any other purpose of the indicator.
    I hope it's just that my knowledge is incomplete, but I do have considerable experience in rigging :)
Well, the logic of me thinking it is a bug is in assumption, that the primary goal of the indicator is to display Bone Roll. Which in turn is based on: - seeing Bone Roll being a basic, core functionality for rigging, and no other practical way of seeing Roll being there. - not knowing any other purpose of the indicator. I hope it's just that my knowledge is incomplete, but I do have considerable experience in rigging :)
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:34:42 +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
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#102948
No description provided.