Where does the lat/long G come from in RC? Is it from GPS data or accelerometers? I remember last year that there was a beta that supported internal accelerometers but I don't remember it being announced as a feature and I do remember discussion of Wiimotes!
Comments
I plan to support the accelerometers on the new S60 phones (which are at least N85, N86, N96, N97 and 5800). The old phones' accelerometers will not be supported at least at first due to much worse API (at least 5500, N95 and N82). Windows Mobile does not offer unified accelerometer API. So no accelerometer support there :(
I had a beta supporting the accelerometers last autumn. It was for the older generation accelerometer phones. I abandoned that just because Nokia decided to change (improve) their API.
In that beta, the accelerometer data was just logged, and nothing was done with it. Basically the new accelerometer support is in same stage, now I need to do some code that actually uses the data :)
6210 has Symbian 9.3 like N96, and 5800 has Symbian 9.4
Examining the csv file, the value of lateral Gs is about the half than it should be. In .vbo exports, the G values are correct. Any ideas why this happens?
Here is a comparison video of v.1.40 vs v.1.30:
Is it safe to say all exported .csvs from rc up to 1.36 have incorrect low g data?
while we are on this..a g filter on export would be nice to stop the erroneous spikes