• Products
  • Solutions
  • Made with Unity
  • Learning
  • Support & Services
  • Community
  • Asset Store
  • Get Unity

UNITY ACCOUNT

You need a Unity Account to shop in the Online and Asset Stores, participate in the Unity Community and manage your license portfolio. Login Create account
  • Blog
  • Forums
  • Answers
  • Evangelists
  • User Groups
  • Beta Program
  • Advisory Panel

Navigation

  • Home
  • Products
  • Solutions
  • Made with Unity
  • Learning
  • Support & Services
  • Community
    • Blog
    • Forums
    • Answers
    • Evangelists
    • User Groups
    • Beta Program
    • Advisory Panel

Unity account

You need a Unity Account to shop in the Online and Asset Stores, participate in the Unity Community and manage your license portfolio. Login Create account

Language

  • Chinese
  • Spanish
  • Japanese
  • Korean
  • Portuguese
  • Ask a question
  • Spaces
    • Default
    • Help Room
    • META
    • Moderators
    • Topics
    • Questions
    • Users
    • Badges
  • Home /
avatar image
1
Question by nztree · Oct 16, 2016 at 09:23 AM · androidinputbugtouchtouchcount

Infuriating bug: Android build occasionally dropping touch input.

In brief:

  • I'm checking for touch input at the top of Update()

  • I'm checking for touch input through NGUI's OnPress method

When running the app, every so often (perhaps 10% of the time) a direct touch to the phone screen will not be registered as a touch. This means that my bool flags are not set, and Input.touchCount is 0.

  • If I leave my finger held down on the phone, at no point will a touch be registered until I release the touch and repress.

  • If I drag my finger on a missed touch event, the touch input will flick on and off sporadically over the course of the drag phase.

I do not believe this is an issue of hidden UI elements consuming touch. I am tracking Input.touchCount which should register touch regardless of whether the input is being consumed by an NGUI element. I am also testing NGUI touch input separately.

Adb logging suggests that EventDispatch isn't recognising the touch when touch is missed. I'm running the app on a Galaxy J7. I have not experienced any dropped touch input in other apps. I'm running Unity 5.3.0f4.

At this point even just a suggestion would be great!

Comment
Add comment
10 |3000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

0 Replies

· Add your reply
  • Sort: 

Your answer

Hint: You can notify a user about this post by typing @username

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Welcome to Unity Answers

The best place to ask and answer questions about development with Unity.

To help users navigate the site we have posted a site navigation guide.

If you are a new user to Unity Answers, check out our FAQ for more information.

Make sure to check out our Knowledge Base for commonly asked Unity questions.

If you are a moderator, see our Moderator Guidelines page.

We are making improvements to UA, see the list of changes.



Follow this Question

Answers Answers and Comments

3 People are following this question.

avatar image avatar image avatar image

Related Questions

Android: Touch Input Timeout Issue 1 Answer

TouchPhase not firing correctly - Android 3 Answers

Android: TouchScreenKeyboard not functioning 2 Answers

Buttons touches dont work if touch splash screen 1 Answer

multi-touch woe, index out of bounds? 1 Answer

  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Default
  • Help Room
  • META
  • Moderators
  • Explore
  • Topics
  • Questions
  • Users
  • Badges