That's debatable. Cars have this tendency of backing out too, and then have you never seen cars moving sideways? You might have noticed different colors at edges of driving spaces around objects. They seem to mean different things (1 color per different value, but we do not know what the values mean. perhaps some means "this is a car front/side/whatever"?) 2d bouding box might just be a debug aid for a different team for al we know and not used by the actual driving algorithm that uses interpreted data in the drivable space, though? That's why I say 3D bounding box while neat eyecandy, might have the same data expressed in other ways. There's radar return to tell you things and then of course there's relative speed. There is a huge difference on hilly roads. HUGE. Also I have no way of extracting data like this from eyeq3 Well, instability is definitely there, no argument about it. Like I said in the comment, more information is availble, just did not want to update the old tool. there's still speed and direction and lane and overlap information and all that. The relative speed tells us if it's going in the same direction or not. Other ways to tell if the car is turning, like it stays withing turning lane bounding lines? Just forget about the 2D bounding box, ok? Let's assume all the really useful info is reflected via the driving space border around the obstacle. Nah, not really. I need to know the direction of their movement, though. There's little indication any such planning is actually going on in this mostly current firmware, though, so this point is kind of moot.