Neither world nor local position is displayed on panel #49449

Closed
opened 2016-09-25 16:29:48 +02:00 by Vladislav · 7 comments

System Information
Debian x64 unstable Cinnamon

Blender Version
Broken: 2.77a abf6f08
Worked: (optional)

Short description of error
When we choose the child object and look to a panel, very often there is displayed neither it's world, nor it's local position,
but it's previous (before parenting) world position + it's personal moving after parenting.

(Example: (only for clearness, how it will be in real practice, you can remove it!!)
you can see here in attached file. Highlight "glass_r" object, you'll see it's coordinates on the panel.
Now if you create new object and specify to it "glass_r"'s coordinates from panel, it'll be very far
from it's current place. So it's not world coordinates of "glass_r" on the panel.
Origin of parent object is not far away from parent of parent's origin, which is not far away from scene's center:
(i received it through: select object, Shift+S, Origin to selected)
"glass_r": (-0.05851, -1.01855, 0.64272); "noseframe_right":(0.00839, 0.01079, 1.11964);
"glasses_1_main":(0.0, 0.0, 1.24983), so "glass_r"'s true positions are:

  • global is (-0.05851, -1.01855, 0.64272)
  • local is (−0,0669, -1.02934, -0.47692) (i received it by subtracting origin's positions
 ("glass_r" - "noseframe_right"))

SunglassesV4.blend )

Exact steps for others to reproduce the error
(Based on a (as simple as possible) attached .blend file with minimum amount of steps)

Case with error:

  1. We create 2 objects: "Cube" and "Cube-2"
    • their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local)
  2. Make "Cube-2" child of "Cube".
    • their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world)
    • local position of "Cube-2" is (0.0, 1.0, 1.0)
  3. Move "Cube" on +1 unit by X axis.
    • their displayed positions are: (2.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (not world and not local) <<error
    • their world positions are: (2.0, 0.0, 0.0), (2.0, 1.0, 1.0);
    • their local positions are (2.0, 0.0, 0.0), (0.0, 1.0, 1.0)).
  4. Move "Cube-2" on +1 unit by X axis.
    • their displayed positions are: (2.0, 0.0, 0.0) (world and local), (2.0, 1.0, 1.0) (not world and not local) <<error
    • their real world positions are: (2.0, 0.0, 0.0), (3.0, 1.0, 1.0);
    • their real local positions are (2.0, 0.0, 0.0), (1.0, 1.0, 1.0)).
      So from paragraph 4 we see that it's displayed position is counted from it's previous (before parenting)
      world position + changes in local position while it was parented.
      error_child_location.blend (there are 2 scenes: "error case" and "normal case")

(Normal case can be only if starting position of parent object is (0, 0, 0)):

  1. We create 2 objects: "Cube" and "Cube-2"
    • their displayed positions are: (0.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local)
  2. Make "Cube-2" child of "Cube".
    • their displayed positions are: (0.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local)
  3. Move "Cube" on +1 unit by X axis.
    • their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (only local)
    • world position of "Cube-2" is: (2.0, 1.0, 1.0).
  4. Move "Cube-2" on +1 unit by X axis.
    • their displayed positions are: (1.0, 0.0, 0.0) (world and local), (2.0, 1.0, 1.0) (only local)
    • world position of "Cube-2" is: (3.0, 1.0, 1.0).)
**System Information** Debian x64 unstable Cinnamon **Blender Version** Broken: 2.77a abf6f08 Worked: (optional) **Short description of error** When we choose the child object and look to a panel, very often there is displayed neither it's world, nor it's local position, but it's previous (before parenting) world position + it's personal moving after parenting. (Example: (only for clearness, how it will be in real practice, you can remove it!!) you can see here in attached file. Highlight "glass_r" object, you'll see it's coordinates on the panel. Now if you create new object and specify to it "glass_r"'s coordinates from panel, it'll be very far from it's current place. So it's not world coordinates of "glass_r" on the panel. Origin of parent object is not far away from parent of parent's origin, which is not far away from scene's center: (i received it through: select object, Shift+S, Origin to selected) "glass_r": (-0.05851, -1.01855, 0.64272); "noseframe_right":(0.00839, 0.01079, 1.11964); "glasses_1_main":(0.0, 0.0, 1.24983), so "glass_r"'s true positions are: - global is (-0.05851, -1.01855, 0.64272) - local is (−0,0669, -1.02934, -0.47692) (i received it by subtracting origin's positions ``` ("glass_r" - "noseframe_right")) ``` [SunglassesV4.blend](https://archive.blender.org/developer/F367897/SunglassesV4.blend) ) **Exact steps for others to reproduce the error** (Based on a (as simple as possible) attached .blend file with minimum amount of steps) Case with error: 1. We create 2 objects: "Cube" and "Cube-2" - their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local) 2. Make "Cube-2" child of "Cube". - their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world) - local position of "Cube-2" is (0.0, 1.0, 1.0) 3. Move "Cube" on +1 unit by X axis. - their displayed positions are: (2.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (not world and not local) <<error - their world positions are: (2.0, 0.0, 0.0), (2.0, 1.0, 1.0); - their local positions are (2.0, 0.0, 0.0), (0.0, 1.0, 1.0)). 4. Move "Cube-2" on +1 unit by X axis. - their displayed positions are: (2.0, 0.0, 0.0) (world and local), (2.0, 1.0, 1.0) (not world and not local) <<error - their real world positions are: (2.0, 0.0, 0.0), (3.0, 1.0, 1.0); - their real local positions are (2.0, 0.0, 0.0), (1.0, 1.0, 1.0)). So from paragraph 4 we see that it's displayed position is counted from it's previous (before parenting) world position + changes in local position while it was parented. [error_child_location.blend](https://archive.blender.org/developer/F367918/error_child_location.blend) (there are 2 scenes: "error case" and "normal case") (Normal case can be only if starting position of parent object is (0, 0, 0)): 1. We create 2 objects: "Cube" and "Cube-2" - their displayed positions are: (0.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local) 2. Make "Cube-2" child of "Cube". - their displayed positions are: (0.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (world and local) 3. Move "Cube" on +1 unit by X axis. - their displayed positions are: (1.0, 0.0, 0.0) (world and local), (1.0, 1.0, 1.0) (only local) - world position of "Cube-2" is: (2.0, 1.0, 1.0). 4. Move "Cube-2" on +1 unit by X axis. - their displayed positions are: (1.0, 0.0, 0.0) (world and local), (2.0, 1.0, 1.0) (only local) - world position of "Cube-2" is: (3.0, 1.0, 1.0).)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @vlad1777d

Added subscriber: @vlad1777d

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-09-26 12:37:45 +02:00

Thanks for the report, but no bug here, this is expected behavior (when you parent an object to another, at least when using the operator, you store the inverse transformation matrix of the parent, such that parented object can “visually” keep same world position as it had before parenting.

Thanks for the report, but no bug here, this is expected behavior (when you parent an object to another, at least when using the operator, you store the inverse transformation matrix of the parent, such that parented object can “visually” keep same world position as it had before parenting.
Author

Thank's for detailed answer.

But 3d artists have no need in inverse transformation matrix.
They only need to see the actual global or local position.

Also, due to Bledner's UI Paradigms ( https://wiki.blender.org/index.php/Dev:2.5/Source/UI/UIParadigms ), there is no need in placing there inverse transformation matrix.

Is there any places for feature requests?
(I would write there about such behavior)

Best regards,
Vladislav.

Thank's for detailed answer. But 3d artists have no need in inverse transformation matrix. They only need to see the actual global or local position. Also, due to Bledner's UI Paradigms ( https://wiki.blender.org/index.php/Dev:2.5/Source/UI/UIParadigms ), there is no need in placing there inverse transformation matrix. Is there any places for feature requests? (I would write there about such behavior) Best regards, Vladislav.

Feature requests and general discussion/suggestion like that should go through IRC (#blendercoders on freenode.net) or ML (bf-funboard@blender.org).

Feature requests and general discussion/suggestion like that should go through IRC (#blendercoders on freenode.net) or ML (bf-funboard@blender.org).
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
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#49449
No description provided.