Presently, the acceleration table's columns are set to be float(4,3), which means the max value is 9.999. This is problematic because when acceleration is saved (and exceeds 9.999), it is set to 9.999.
With the change of making the acceleration table's columns an int, their max value would be 2147483647, allowing a more-useful range of data. Additionally, this data is only ever coming through as short, so we can guarantee we are never going to need to store double values in here.
Presently, the
accelerationtable's columns are set to befloat(4,3), which means the max value is9.999. This is problematic because when acceleration is saved (and exceeds 9.999), it is set to 9.999.With the change of making the
accelerationtable's columns anint, their max value would be2147483647, allowing a more-useful range of data. Additionally, this data is only ever coming through asshort, so we can guarantee we are never going to need to storedoublevalues in here.