2014-04-13 snapshot

[AWood]

As a general rule, it's best to keep the radius of the spheres less than the maximum distance the bikes can travel in one 1/128 second step. So guessing around 60 MPH as the top speed, 60 MPH is 88 feet/sec divided by 128 steps/second is .6875 feet/step. So if you have a sphere < .6875 radius traveling at 60 MPH and it hits another sphere with a radius < .6875 feet. there's a chance of it thinking the collision is from the wrong side.

The same thing would apply to meshes. You'd probably want to keep the meshes even thicker since meshes have more corner cases than spheres when the collision detector has to pick the normal vector for the collision.

Using the 60MPH rule, what happens when two riders collide head on at full speed? They go through each other?

you die

[jlv]

Using the 60MPH rule, what happens when two riders collide head on at full speed? They go through each other?

At a 120 MPH relative speed there'd be a 50% chance of the normal being reversed with a .6875 radius. The reversed normal would make it want to go through, but since there are usually multiple spheres in a bike body it'd most likely get stuck between two spheres.

[AWood]

Using the 60MPH rule, what happens when two riders collide head on at full speed? They go through each other?

At a 120 MPH relative speed there'd be a 50% chance of the normal being reversed with a .6875 radius. The reversed normal would make it want to go through, but since there are usually multiple spheres in a bike body it'd most likely get stuck between two spheres.

is that why now you can get stuck in another person and fly away?

[jlv]

It's a combination of that and the lagged collisions when online.

[AWood]

It's a combination of that and the lagged collisions when online.

hehehe. awesome.