You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 11, 2021. It is now read-only.
There seems to be a buffering problem with the accelerometer interface as it takes a while for the accelerometer values to respond to the actual movement of the device.
The text was updated successfully, but these errors were encountered:
This is confirmed as a bug. The problem is that in MonoGame the implementation for Accelerometer uses the Core Motion pulling methodology that handles motion updates at specified intervals using a Queue. This is what creates the perceived buffering effect and non reactiveness to tilt movements. Handling accelerometer data this way introduces additional overhead. In the Core Motion Management documentation provided by apple most game apps are interested only the latest sample of motion data when they render a frame so should use the polling method which provides a periodic sampling of motion data.
There seems to be a buffering problem with the accelerometer interface as it takes a while for the accelerometer values to respond to the actual movement of the device.
The text was updated successfully, but these errors were encountered: