UPDATE
I'm sorry, but I got ahead of myself in posting. I checked and is not the order of behaviours. The sprite that shows the "bug" has the right order of behaviours (1. 8-Direction 2. BoundToLayout).
So I began to test one more time:
Redid the example one more time. This time the "bug" does not happen. Order of behaviours doesn't matter.
https://drive.google.com/open?id=1I_sHeTvYs-Ru0r_d8m9RCdYp-_pvJg2R
Next, I cloned the second "car" sprite (since that was how I made the original capx), added the events for this new object and this time the bug appears in the new instance.
Now I check what happens if I add a fourth car by not cloning. This car4 also does show the bug.
https://drive.google.com/open?id=1MDNk_YMDroGb_GG5a1p6Mi9t1gZYCRmF
All cars have 1. 8-direction 2. BoundToLayout. I've also tried changing the order of behaviours but it doesn't change anything.
What do you think?
PS:
For Construct 3, were you running the C3 or C2 runtime in your version built from scratch ?
It was the C2 runtime