I agree . It ' s not only the quitters , cause a lot of matches don ' t start with a full lobby . And for the record , sometimes the lobbies don ' t even get full the entire match . <| sep |> I mean , there is plenty of space for the bullet to graze past the player as you can see . <| sep |> No Putin in an authoritarian dictator , he ' s a scary man and that why he doesn ' t want Romney as secretary of state because Romney won ' t just bend over . <| sep |> This sandwich tastes awful . I want my money back . <| sep |> Damn you ' re sexy . Pm me . Let ' s have some fun <| sep |> I don ' t actually know how their system works . However , sensor saturation doesn ' t really anything to do with overflow or memory at least with the system in general . It means the sensor maxed out . They were almost certainly using control logic to stabalize the device . This type of algorithm requires that the sensor values change with respect to changes made to the system . A saturated sensor will no longer respond to changes to the system . This results in something like division by zero the derivative of the model will be zero . Then was it a developer error ? Probably not . In fact , they probably had a line in the code like this , If deltaX 0 logwe ' re fuckedThe question is then why was the sensor saturated ? I doubt they miscalculated the expected entry force and even if they did sensors are usually at least 1 . 5 requirements . They would have to be really wrong . Because they never stated there was a failure prior to that phase that suggest the sensor values were real my guess is that the an accelerometer had an electrical failure . Their next design will probably have like 2 extra redundant sensors as a fuck you .