- Home /
Input.touchCount bug? Not counting the right number of fingers
Hi everyone...
I've stumbled across a pretty big bug (or so it seems).
While using the Unity Remote for Android, or running the app in my android phone standalone, for some reason, if I touch the screen several times, with several fingers, makes the Input.touchCount eventually end up counting the wrong number of fingers, which just seems weird.
I even have a Debug.Log with it just to check how many fingers are being counted, and when this happens, even if I'm not touching the screen it keeps registering 1 touch, sometimes even more. If I then tap the screen a few times with several fingers, it seems to reset the touchCount back to normal.
Anyone else had this problem? And if so, is there a solution or is it an actual bug?
Answer by Tricephalus · Jul 23, 2014 at 06:09 PM
I am not 100% sure this is a bug.
Try the following:
Create a new project
Create a single script
use Debug.Log(Input.touchCount); on the script in the update function
run it, and it will start logging the right number of touches, but if you quickly tap several fingers on screen, it will go completely crazy. I just tested it now, and it ended up saying I had 4 touches actives on the screen when I had none.
Your answer
Follow this Question
Related Questions
Infuriating bug: Android build occasionally dropping touch input. 0 Answers
WWW http request loads way to long on IOS 0 Answers
Mobile Input Not Accurate 0 Answers
Stuck on splash screen android 0 Answers