Then you need someone who knows bricks better then me, all i can say at this point it that it wont work due to the fact that dynamic objects lose its physics as soon as it get’s parented to an other object.
#edit
does it need to be parented in front, before it reaches the red cube? Or can it be parented after reaching the red cubes position?
Not a neat way to do this, but does what you want.
What is your goal here, cube walking to an other cube, or is red cube some sort of node to go to?
Because your way will not be a good solution if you add a lot more. you could change the red cube to an empty if it just functions as a node.
anyway with bricks:
edit object(track to)
motion, loc at 0.1, L selected
will move it to the position, but reaching upon the red cube it will keep spinning until it gets out of control, so here is a python version that works. But again i would not use collision/physics settings for the red cube.
I opened your original .blend with Upbge 2.5 and it just works. The cubes blue and purple act identical relative to their respective parents. Except that the purple one gets warped. What am i missing?
if using bge 2.79 then going to upbge is not bad, only a little bit that you need to adjust, and that little bit is 99.9% scripting, so try it i would say.
I looked at this earlier and thought about it. Figured it had something to do with the way dynamics get suspended when parenting and how it must lose it’s steering function…or something. And this seems like it could be a mess with bricks. Not sure why I came back to it later.
Anyway, I didn’t realize Cotaks had uploaded a blend already but I went ahead and put this one up since it has the stipulation of facing the same direction the OP was looking for. Maybe it will help.cubes_parrent_python.blend (99.8 KB)