Page MenuHome

Transforming Parent's Origin Also Effects Child's Origin (Pivot Point -> Affects Only -> Origins)
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.16299 64 Bits
Graphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0

Blender Version
Broken: version: 2.81 (sub 4), branch: master, commit date: 2019-08-28 20:33, hash: rBa7ac8a22f8eb
Worked: (probably never)

Short description of error
Transforming Origin of Parent Object also effects Child's Origin transform, which is un-expected behavior.
Expected behavior Origins must-be freely transform without effecting others (child objects origin)

Exact steps for others to reproduce the error

  • Create two objects e.g. Cube & Sphere
  • Parent Cube to Sphear
  • Enable Affects Only -> Origins:

  • Move Child's Origin (It's okey behavior)
  • Move Parent's Origin

You will notes: Child's origin is too moving (un-expected behavior)

Before Transforming:


After:

(Parent's Origin is Rotated)

Note:

There is an option Parents (Skip Childrens), which somehow solves this problem...


Recommended Behavior:
With the case of origin transforming,.... Affects Only -> Origins by defaults only effects Parent's Origin, Not Child's too... (This is common operation users wants & is more consistent with previous operations e.g. Origin to 3d Cursor)
Mostly there is no case in which User's wants Transform Origin of Parent & Child together without transforming Mesh it'self or for this action implement alt solution(maybe another checkbox)...
Thanks! Have a nice day!

Details

Type
Bug

Event Timeline

Abid Maqbool (cto.abid) renamed this task from Transforming Child's Origin Also Effects Parent's Origin (**Affects Only -> Origins**) to Transforming Child's Origin Also Effects Parent's Origin (Pivot Point -> Affects Only -> Origins).Aug 29 2019, 11:21 AM
Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Aug 29 2019, 4:05 PM

I think this is working as expected:

  • moving the parent origin will move the parents origin as well as the childs origin
  • moving the child origin only really moves the child origin for me (and it actually looks like that in your "After" picture as well: parent/cubes origin is still in the cubes center, whereas the relationship line points to the moved child origin [now outside the sphere geometry])
  • if you want to move the parent origin without affecting the child origin, enable Parents (Skip Children)

If you do that though [enable Origins and Parents (Skip Children)] I noticed two quirks though (reported in T69299)

@Abid Maqbool (cto.abid) : makes sense? (Or did I misunderstand something here?)

@Philipp Oeser (lichtwerk) I 'am sorry, I am too late to reply (as just read now)!
Ah! I think, i miss understand the report, the prob was more like a Parent Origin effects Child (un-expacted)
I think, Close as invalid as totally miss-understanding!
Thanks

@Philipp Oeser (lichtwerk) Hope this will helps to understand the prob.

Let me know, you need more info? (actually i 'am not mentally refresh at this time)

I am of the opinion that it does not work as expected because moving the pivot of the object that interests us, it also moves the center of the other object ... without even really making it see .. we realize it only when we select the other object

I still think this is expected (at least I would expect it):

  • if you move a parent "normally" (with Origins OFF), you would move both parent and child (origin + mesh geo),
  • if you move a parent (with Origins ON), i would expect to move both parent and child origins (without mesh geo).
  • if you want only want to move the origin of the object that 'interests you', make sure to ignore children, that's what Parents (Skip Children) is for...

Hum, But it's very confusion behavior...
Or at least it must be default.
For example, when you apply Ritht Click -> Set Origin -> Orion To 3d Cursor


for parent object, child's origin/mesh not effected (this must be consistent all across Blender)
However, currently when same action is performed with Pivot Point -> Affects Only -> Origins

Which is totally un-necessary, as can i imagine...
or we have to enable too Parents (Skip children) to prevent this
@Philipp Oeser (lichtwerk) , @William Reynish (billreynish) ???

Abid Maqbool (cto.abid) renamed this task from Transforming Child's Origin Also Effects Parent's Origin (Pivot Point -> Affects Only -> Origins) to Transforming Parent's Origin Also Effects Child's Origin (Pivot Point -> Affects Only -> Origins).Aug 30 2019, 5:36 AM
Abid Maqbool (cto.abid) updated the task description. (Show Details)

Correct me if i am wrong, but it seems blender's origin is used both as the center of object/transform and as a pivot point the child inherits the parent's transform even on the origin level so it moves with, but when u enable (skip children) it tries to zero it out but at the same time inherit's the transform... u end up witht this wiggly effect, i think other softwares on a pseudo pivots so both child & parent are in the same global space or something like that.

@Zino Guerr (Zino) Blender p-point/origin is where all the transform are counted, effects physics sim too...
Child's inherit form this point, too.
In other software, mostly transform is counted globally & locally, both. Currently in Blender Only Local Transform (form parent) is available.
wiggly effect I think, it's not yet stable.. currently under development..