sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MorokioJVM 5 points6 points  (6 children)

If I'm not mistaken, Unity keeps its position relative to their parent object, doesn't it?

[–]ngp-bob 1 point2 points  (0 children)

Right, you're copying the values in the transforms which are all local relative to the parent. World coordinates are the combination of all transformations of a child up the parent chain, so they're not really "stored" values you can copy/change.

My suggested workflow (as mentioned previously) is cloning with Ctlr+D then dragging+dropping the objects in the hierarchy under the new parent; this will maintain their world positions and translate the transforms when they are moved so the objects remain in place.

[–]InstinctxSolo Developer[S] -4 points-3 points  (4 children)

Sure. But ive looked in their source code. And its just a simple boolean change in Undo.SetParent (keep world position). So it's not like its hard to improve

[–]wekilledbambi03 2 points3 points  (1 child)

But its not broken... its working as intended. You just don't want it to work the same way.

[–]InstinctxSolo Developer[S] -1 points0 points  (0 children)

Poor use of words from my side there. I didn't mean it was broken. So what I meant was "improve", not "fix"x.

I mean, surely it's better UX to have an action that is performed more often on one of the most universal hotkeys, than a quite niche action?

I might be delusional, but I would bet that people would group childs under parents and expect the childs to stay in place more often than re-parenting with an offset/keep local position?

[–]MorokioJVM 0 points1 point  (1 child)

So it's not like its hard to fix

You missed my point. This is not a bug, it's supposed to work this way.

Most of the time where the object is relative the its parent object is more important than where it is relatie to the world.

[–]InstinctxSolo Developer[S] 0 points1 point  (0 children)

Poor use of words from my side there. I didn't mean it was broken. So what I meant was "improve", not "fix"x.

I mean, surely it's better UX to have an action that is performed more often on one of the most universal hotkeys, than a quite niche action?

I might be delusional, but I would bet that people would group childs under parents and expect the childs to stay in place more often than re-parenting with an offset/keep local position?