- Home /
Touch.deltaTime returning a negative number on Android
I'm working on a mobile project, and while Touch.deltaTime functions as expected on iOS, it semi-regularly returns a negative number on Android.
It's also strange that the negative number returns can be up to an order of magnitude greater than the expected positive value (0.016 to 0.03 vs -0.05 to -0.246).
Has anyone experienced an issue like this, and/or does anyone know why this is happening?
Have the same issue , did you come up with any solution?
Unfortunately, I never found the cause of this. I just ended up discarding invalid values.. not the best solution, but it worked out well enough for me.
Is your Android phone rooted? Does it have Super User access? Have you over clocked the processor? What model of phone are you using? How many processor cores does it have?
I don't have the device anymore, but off the top of my head: not rooted; had super user access (I think..); not overclocked; don't remember the exact model (motorola droid is co$$anonymous$$g to $$anonymous$$d, though); likely 1 core.
If it had super user access, then it was rooted. Reason I ask, is because thinking from a logical standpoint, a negative deltaTime probably has to do with some kind of inconsistency between cores in a multi-core processor architecture. I can't really narrow anything down for you, but that's just a thought.
Your answer
Follow this Question
Related Questions
Android Touch Input GUITexture 2 Answers
GUITexture and Touch Input 1 Answer
Swipe and Joystick Together on Mobile 0 Answers
GUITexture Touch Problem 2 Answers