Wrong position in the inheritance, third child

[Epihaius]

@serega-kkz

Hmm, it’s strange that this is not the case in the blender.

Perhaps Blender always shows/uses the net coordinates? As I’ve only just begun working with Blender, I’m not in a good “position” to comment on that.

@serega-kkz

when I set the coordinates via the set_pos () method, then without specifying an explicit node, this is done relative to “render”

Are you sure about that? As far as I know, set_pos always sets the given coordinates relative to the parent (even if the node currently has no parent; the coordinates are still assumed to be in the (future) parent’s local space), unless you specify the reference node as first argument.

@serega-kkz

This has no effect whatsoever.

That would indeed have no effect. What happens is this:

• you assign a position relative to root, which has coordinates (0, 0, 0). That’s the same as not specifying a reference node at all.

• When you reparent the box nodes, the positions that were set previously will still be interpreted as relative to the new parent (that’s how it always worked, as far as I can tell).

@serega-kkz

they should remain in their original places, after being attached to some node.

If you want the boxes to stay in place after reparenting, you can call wrt_reparent_to instead. That’s what it’s for. But it can introduce numerical inaccuracies, so use with caution.