Align Tools - Transform Bug: 'Align Selected to Active' #104653

Open
opened 2023-05-29 17:44:09 +02:00 by Evan-Davies · 1 comment

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

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
Worked: (newest version of Blender that worked as expected)

Short description of error
There is a consistent problem using 'Align Selected to Active' when the active objects is controlled by 'Follow Path' constraint.

Exact steps for others to reproduce the error
In the example scene:

Select Obj-1.
Shift Select Obj-2.
Under 'Object/Transform' menu select 'Align Selected to Active'.
You will see that Obj-2 has now shifted away from the path.

System Information Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49 Blender Version Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7 Worked: (newest version of Blender that worked as expected) Short description of error There is a consistent problem using 'Align Selected to Active' when the active objects is controlled by 'Follow Path' constraint. Exact steps for others to reproduce the error In the example scene: Select Obj-1. Shift Select Obj-2. Under 'Object/Transform' menu select 'Align Selected to Active'. You will see that Obj-2 has now shifted away from the path.
Evan-Davies added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-05-29 17:44:09 +02:00
Evan-Davies changed title from Transform Bug: 'Align Selected to Active' to Align Tools - Transform Bug: 'Align Selected to Active' 2023-05-29 17:44:58 +02:00

Looking through some old reports, can confirm this with current Align Tools addon version 0.3.5 in blender 4.1+.
Seems like the transforms source object get's it's transform vector overriden with the current actual position, not taking in account any modifiers or constraints which may have influenced the actual display position without changing it.

In attached demo file Cube is the source location and has a follow path constraint. Cube.001 is the target object, which should get aligned to Cube.

Cube before (0,0,0); Cube.001 before (0,0,0)
Cube after (-2.16441,0,0); Cube.001 after (-2.16441,0,0)
Cube after expected (0,0,0), Cube.001 after expected (-2.16441,0,0)

when only alining y or z axis (as the follow path changed the x position offset):

Cube before (0,0,0); Cube.001 before (0,0,0)
Cube after (-2.16441,0,0); Cube.001 after (0,0,0)
Cube after expected (0,0,0), Cube.001 after expected (0,0,0)

In regular cases this should pose no problem, but since the follow path constraint modifies the location without changing the actual transform values the override get's visible and thus creates an offset.

Looking through some old reports, can confirm this with current `Align Tools` addon version `0.3.5` in blender 4.1+. Seems like the transforms source object get's it's transform vector overriden with the current actual position, not taking in account any modifiers or constraints which may have influenced the actual display position without changing it. In attached demo file Cube is the source location and has a follow path constraint. Cube.001 is the target object, which should get aligned to Cube. ``` Cube before (0,0,0); Cube.001 before (0,0,0) Cube after (-2.16441,0,0); Cube.001 after (-2.16441,0,0) Cube after expected (0,0,0), Cube.001 after expected (-2.16441,0,0) ``` when only alining y or z axis (as the follow path changed the x position offset): ``` Cube before (0,0,0); Cube.001 before (0,0,0) Cube after (-2.16441,0,0); Cube.001 after (0,0,0) Cube after expected (0,0,0), Cube.001 after expected (0,0,0) ``` In regular cases this should pose no problem, but since the follow path constraint modifies the location without changing the actual transform values the override get's visible and thus creates an offset.
Sign in to join this conversation.
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-addons#104653
No description provided.