First off, I promise this is the last thread I post for a while as not to saturate the board!
I have a problem with parenting when using track to actuators. With a default cube I can get the movement to go as normal. I add a track to actuator and again, all is well. Then I add a child to the cube aiming at the target- and the movement goes anywhere but towards the target. Try the blend to see what I mean! I have tried the animation hacks but again, no joy.
Can anyone tell me what is going on? This has happened several times with me and I cant figure it out.
BTW, as far as I can tell, the motion actuaor is in +ve x, animation hacks +ve x.
I’ve never tracked a parent to a child because I figure that as the parent rotates the child will orbit and that it wouldn’t stop. What I can’t figure out is why it stops and at that particular angle (looks like about -145’.).
Interesting phenomena but not a bug. It’s often recommended that simple motion not be used for dynamic objects especially when there are going to be collisions as in this case with the plane. Throw in a track to actuator and…
It’s not a bug and it’s not even a limitation. If you were to get to the bottom of it, it would be an ordinary logical fact, like… you can’t catch a train without leaving the house. And it’s not taking away from anything that you can and should be able to do in blender. There’s a few other apparently strange things that can appear to happen in 3d software, what with tan 90’ being infinity and stuff like that.
I pretty much started again when this stuff happens- the other golden rule I have found is that +y is forward…always. Mess with that and crazy stuff happens!