Gimbal Transfor Orientation scaled if parent bone scaled on one axis #71514

Open
opened 2019-11-12 14:20:00 +01:00 by Danila · 7 comments

System Information
Operating system: Windows 10
Graphics card: GeForce GTX 1060

Blender Version
Broken: everywhere

Short description of error
Gimbal Transform Orientation scaled if parent bone is scaled on one axis
image.png

Exact steps for others to reproduce the error
Open:
gimbal_test.blend

or:

  • Select transform orientation to Gimbal
  • Create two bones, switch rotation mode of both bones to ZYX
  • Change inherit Scale of second bone to None
  • rotate both bones by -30 on x axes
  • Lock scale on x and z axis of first bone
  • scale first bone and gimbal widget on a second bone will broke
**System Information** Operating system: Windows 10 Graphics card: GeForce GTX 1060 **Blender Version** Broken: everywhere **Short description of error** Gimbal Transform Orientation scaled if parent bone is scaled on one axis ![image.png](https://archive.blender.org/developer/F8267480/image.png) **Exact steps for others to reproduce the error** Open: [gimbal_test.blend](https://archive.blender.org/developer/F8048164/gimbal_test.blend) or: - Select transform orientation to Gimbal - Create two bones, switch rotation mode of both bones to ZYX - Change inherit Scale of second bone to None - rotate both bones by -30 on x axes - Lock scale on x and z axis of first bone - scale first bone and gimbal widget on a second bone will broke
Author

Added subscriber: @DanilaPryamonosov

Added subscriber: @DanilaPryamonosov

Added subscriber: @StanislavOvcharov

Added subscriber: @StanislavOvcharov

Added subscribers: @ideasman42, @mano-wii

Added subscribers: @ideasman42, @mano-wii

I don't know exactly how gimbal orientation works.
In the example shown, apparently the transformation axes are being scaled along with the first bone.

@ideasman42, is this expected?

I don't know exactly how gimbal orientation works. In the example shown, apparently the transformation axes are being scaled along with the first bone. @ideasman42, is this expected?
Germano Cavalcante changed title from Gimbal Transfor Orientation dont work if parent bone scaled on one axis to Gimbal Transfor Orientation scaled if parent bone scaled on one axis 2020-01-09 16:59:39 +01:00

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

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

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

For the unscaled bone, the gizmo rotates around the bone's local Y axis. For the bone with the scaled parent, the gizmo rotates around a different axis. This looks like a bug to me, but whether it really is a bug in the implementation depends on how Gimbal mode is supposed to work.

The gimbal transformation mode is described in the manual as:

Uses a Gimbal behavior that can be changed depending on the current Rotation Mode.

This doesn't explain at all what the behaviour is, just that it can be changed.

A different manual page describes it as:

Align each axis to the Euler rotation axis as used for input.

This doesn't make sense, as it doesn't explain the input for what.

Both are IMO non-descriptive and should be clarified, so this could just be resolved by fixing the manual.

For the unscaled bone, the gizmo rotates around the bone's local Y axis. For the bone with the scaled parent, the gizmo rotates around a different axis. This looks like a bug to me, but whether it really is a bug in the implementation depends on how Gimbal mode is supposed to work. The gimbal transformation mode is described in [the manual](https://docs.blender.org/manual/en/dev/scene_layout/object/editing/transform/control/orientations.html) as: > Uses a Gimbal behavior that can be changed depending on the current Rotation Mode. This doesn't explain at all what the behaviour is, just that it can be changed. A [different manual page](https://docs.blender.org/manual/en/dev/editors/3dview/controls/orientation.html) describes it as: > Align each axis to the Euler rotation axis as used for input. This doesn't make sense, as it doesn't explain the input for *what*. Both are IMO non-descriptive and should be clarified, so this could just be resolved by fixing the manual.
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:36:17 +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#71514
No description provided.