Current transform orientation not taken into account when using 'Align to transform orientation' AGAIN #82777

Closed
opened 2020-11-17 10:40:31 +01:00 by Pasang Bomjan · 13 comments

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-14 03:52, hash: 83d0810a9f
Caused by 388b916246

Short description of error
'Align to transform orientation' operator uses the default value of 'GLOBAL' even if the scene has a different one. And you manually have to choose the right one.

Exact steps for others to reproduce the error
Align to transform orientation bug.blend
Open the given example file
The current transform orientation is a custom 'FACE'
The object is already selected and all you have to do is use 'Align to Transform Orientation'.

**Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-14 03:52, hash: `83d0810a9f` Caused by 388b916246 **Short description of error** 'Align to transform orientation' operator uses the default value of 'GLOBAL' even if the scene has a different one. And you manually have to choose the right one. **Exact steps for others to reproduce the error** [Align to transform orientation bug.blend](https://archive.blender.org/developer/F9309743/Align_to_transform_orientation_bug.blend) Open the given example file The current transform orientation is a custom 'FACE' The object is already selected and all you have to do is use 'Align to Transform Orientation'.
Author

Added subscriber: @Pasang

Added subscriber: @Pasang

#84264 was marked as duplicate of this issue

#84264 was marked as duplicate of this issue
Member

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

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

Added subscribers: @mano-wii, @lichtwerk

Added subscribers: @mano-wii, @lichtwerk
Member

Caused by 388b916246

@mano-wii: reading the commit message, this rectified it for a certain scenario, but I assume for Align to Transform Orientation this should keep the current orientation?
Setting to High since it is a regression (but feel free to set back if not appropriate)

Caused by 388b916246 @mano-wii: reading the commit message, this rectified it for a certain scenario, but I assume for `Align to Transform Orientation` this should keep the current orientation? Setting to High since it is a regression (but feel free to set back if not appropriate)

Added subscriber: @dfelinto

Added subscriber: @dfelinto

As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel.

As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel.
Germano Cavalcante self-assigned this 2020-11-18 12:14:45 +01:00
Member

In #82777#1056891, @dfelinto wrote:
As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel.

That is probably what the reporter meant by

And you manually have to choose the right one.

> In #82777#1056891, @dfelinto wrote: > As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel. That is probably what the reporter meant by > And you manually have to choose the right one.

This issue was referenced by d0426a4ed5

This issue was referenced by d0426a4ed50862e012e4314e74f50354fed093c2

This issue was referenced by 20f8130d6f

This issue was referenced by 20f8130d6f905321059200756d18e9fffab60b7f
Author

In #82777#1056916, @lichtwerk wrote:

In #82777#1056891, @dfelinto wrote:
As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel.

That is probably what the reporter meant by

And you manually have to choose the right one.

Yes, it should be automatic.

> In #82777#1056916, @lichtwerk wrote: >> In #82777#1056891, @dfelinto wrote: >> As a workaround the axis used for the alignment can be changed after the operation is done in the "redo" panel. > > That is probably what the reporter meant by >> And you manually have to choose the right one. Yes, it should be automatic.

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'

Added subscribers: @Larsen, @Stan_Pancakes

Added subscribers: @Larsen, @Stan_Pancakes
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
6 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#82777
No description provided.