I understand there are two ways of getting touch input: using get touch or on pointer down.
is there any speed advantage of one over the other? I have a working input using get touch but there seems to be at least 500 ms lag between the time I touch the screen and the character moving. I am using Galaxy Note 5. So now I am trying to do it with OnPointerDown. However if there will be the same lag I will not waste my time.
Instead of “getting the character to move,” why don’t you turn on and off a single UI Text object based on when you touch the screen and see if the lag is really in the input mechanism you choose, or perhaps in the animator that makes the character move.
Remember also that the Unity Input system offers various forms of low-pass filtering which can also slow your apparent responsiveness down. They do this to smooth out input controller noise, but you can also get at the raw values, generally speaking.
Did you ever figure this one out?
I’ve never noticed any major input lag when using GetTouch on mobile devices (Android).
I seem to remember that using OnPointerDown generated a compiler warning that it wasn’t ideal to use it for mobiles and recommended using GetTouch instead, although there again I don’t recall seeing any visible difference myself.
If you’re getting input lag I’d suggest the problem lies elsewhere in the code.