Search Issue Tracker
Fixed
Votes
7
Found in
5.1.2p1
Issue ID
717707
Regression
No
Touch Input randomly drops out at high FPS
How to reproduce:
1. Open attached project
2. Build to iOS and run
3. Make some shapes without lifting finger
- Note how every once in a while the green lines get a red cross on them
- The red cross means that the touch system has reported a stationary touch event, even though there was constant movement
- Input handling has been improved in 5.3.0b5, so the issues with touch input events should be less of a problem. That said however, some touch events still fail to arrive when they should. Apple was contacted and should be aware about this issue. In the meantime we're doing what we can from our side to reduce missed events.
- What can be done from the user side is to increase the performance of the code to leave more time for the processor to gather and process touch inputs. For example having loads of lines instead of one polyline has a lot of overhead when drawing.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment