As long as the updatevehicle() function isn't deleting or moving type instances in the list, I can't see how it can MAV. :/
Neither can I, but it does in the racer.
and no, at the point of the error, Updatephysics isnt actually updating the physics, just doing some checks, using VEH, which at the time was global, and unfortunately, the FOR loop was using it....um.... yeh.... lol.
No idea :/
Found an old pic i threw together when it very first happened:
lol...
[edit]
Didn't click at the time, but that bug report is almost certainly about what caused the issue. I *really* hope it sorts it!