Transforming Parent's Origin Also Effects Child's Origin (Pivot Point -> Affects Only -> Origins) #69283

Closed
opened 2019-08-29 11:17:34 +02:00 by Abid Maqbool · 17 comments

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: a7ac8a22f8
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 effectingothers (child objects origin)

Exact steps for others to reproduce the error

  • Create two objects e.g. Cube& Sphere
  • ParentCube toSphear
  • Enable Affects Only -> Origins:
    image.png
  • 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:
image.png
After:
image.png
(Parent's Origin is Rotated)

Parents Origin Transform Test.blend

Note:

There is an option Parents (Skip Childrens), which somehow solves this problem...
image.png
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!

**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: `a7ac8a22f8` 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**: ![image.png](https://archive.blender.org/developer/F7709298/image.png) * 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:** ![image.png](https://archive.blender.org/developer/F7709310/image.png) **After:** ![image.png](https://archive.blender.org/developer/F7709315/image.png) (Parent's Origin is **Rotated**) [Parents Origin Transform Test.blend](https://archive.blender.org/developer/F7710359/Parents_Origin_Transform_Test.blend) Note: ------ There is an option **Parents (Skip Childrens)**, which **somehow solves** this problem... ![image.png](https://archive.blender.org/developer/F7710365/image.png) **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!
Author

Added subscriber: @AbidMaqbool

Added subscriber: @AbidMaqbool
Abid Maqbool changed title 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) 2019-08-29 11:21:27 +02:00
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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 #69299)

@AbidMaqbool : makes sense? (Or did I misunderstand something here?)

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 #69299) @AbidMaqbool : makes sense? (Or did I misunderstand something here?)
Author

@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

@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
Author

@lichtwerk Hope this will helps to understand the prob.
Childs Origin Transform Test.blend

Origin Transform Gizmo Problem.gif

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

@lichtwerk Hope this will helps to understand the prob. [Childs Origin Transform Test.blend](https://archive.blender.org/developer/F7709693/Childs_Origin_Transform_Test.blend) ![Origin Transform Gizmo Problem.gif](https://archive.blender.org/developer/F7709697/Origin_Transform_Gizmo_Problem.gif) Let me know, you **need more info**? (actually i 'am not mentally refresh at this time)

Added subscriber: @nokipaike

Added subscriber: @nokipaike

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

Screenshot (335).png

Screenshot (336).png

Screenshot (334).png

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 ![Screenshot (335).png](https://archive.blender.org/developer/F7709722/Screenshot__335_.png) ![Screenshot (336).png](https://archive.blender.org/developer/F7709720/Screenshot__336_.png) ![Screenshot (334).png](https://archive.blender.org/developer/F7709719/Screenshot__334_.png)
Member

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...
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...
Author

Hum, But it's very confusionbehavior...
Or at least it must be default.
For example, when you apply Ritht Click -> Set Origin -> Orion To 3d Cursor
image.png
for parent object, child's origin/mesh not effected (this must be consistent all across Blender)
However, currentlywhen same action is performed with Pivot Point -> Affects Only -> Origins
image.png
Which is totally un-necessary, as can i imagine...
or we have to enable too Parents (Skip children) to prevent this
@lichtwerk , @WilliamReynish ???

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** ![image.png](https://archive.blender.org/developer/F7710315/image.png) 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** ![image.png](https://archive.blender.org/developer/F7710329/image.png) Which is **totally un-necessary**, as can i imagine... or we have to enable too **Parents (Skip children)** to prevent this @lichtwerk , @WilliamReynish ???
Author

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish
Abid Maqbool changed title 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) 2019-08-30 05:36:43 +02:00

Added subscriber: @Znio.G

Added subscriber: @Znio.G

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.
org.gif

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. ![org.gif](https://archive.blender.org/developer/F7710362/org.gif)
Author

@Znio.G 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..

@Znio.G 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..
Member

@Znio.G: jiggle is reported seperately in #69299

@Znio.G: jiggle is reported seperately in #69299
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Philipp Oeser self-assigned this 2019-09-02 10:25:31 +02:00
Member

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Member

@ideasman42 committed 6ff675f830, so this can be closed...

@ideasman42 committed 6ff675f830, so this can be closed...
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#69283
No description provided.