Page MenuHome

Affect Only: Origin not working in Transform Panel of the 3D View
Closed, InvalidPublic

Description

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-07 20:33, hash: rBeefd806afc15
Worked: (optional)

Short description of error
Affect Only: Origin not working in Item > Transform Panel of the "N" context panel of the 3D View.

When Affect Only: Origin is toggled on changing the properties of the "N" context panel should not be affecting to geometry.

I'm trying to reset origin rotation but it also changes the geometry.

Event Timeline

I'd generalize this a bit. When Affect Origins is set, most of the transforms seem to indeed affect origin only (i.e. Object -> Transform, Object -> Mirror). Unfortunately, neither the Transform panel, nor Object -> Clear operators seem to be aware of that setting, and still affect the object, and not just origin.

Thanks for reporting. I can reproduce this too. Investigating...

This might be intentional, because the transform panel also ignores locking constrains for location, rotation and scale, whereas tools that operate on objects have to respect constrains / affect only.

Maybe solve this by adding an Origin Panel that edits Transform, Rotation, and Scale like the 3D Cursor has it's own panel for changing that stuff. Under View > 3D Cursor.

Jean First (robbott) changed the task status from Unknown Status to Unknown Status.Nov 30 2019, 5:18 PM
Jean First (robbott) claimed this task.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hello! I am do not understand, why it not a bug? Please help me:

  1. Affect only is option of Transformation:

  1. Location of object also is Transformation:

If the “Affect only” is enabled as Origins and is part of the Transformation, the changing values in the “Item” panel should be applied to the Origins, and not to the object. Isn't that a bug?

When I change values at Location, option Affect only with Origins does not work as expected

Thanks!

That "Affect Only" refers to tools, like when you press 'G' to grab or 'R' to rotate. The transform panel refers to the object as a whole. That's why this is not a bug.

Now this might be bad design or confusing to users, but as mentioned before, intentional behavior is not defined as a bug.

That "Affect Only" refers to tools, like when you press 'G' to grab or 'R' to rotate. The transform panel refers to the object as a whole. That's why this is not a bug.

Thanks! Now I understand difference.

Hello!
I was also prepearing to report this as a bug when I found this bug report.
If this is not a bug then the fact that when the affect only origins is enabled you can go to the object_menu/transform/align_to_transform_orientation and only the object's origin is rotated should be a bug. The other commands in the menu like randomize_transform and align_objects have no effect on the origin just to the object as a whole.

The align_to_transform_orientation aplied only to the origin is the only way I can find to align the object's origin to a known orientation, so if it's a bug and get resolved then I'm in trouble when, for example, I import a model wich has all its parts's origins at 0,0,0.