Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
5.6.0f3
Issue ID
899209
Regression
Yes
Windows touch input events are out of sync from positioning events
Steps to reproduce:
1. Open the attached project (InputTestProject.zip)
2. Open the Assets/test.unity scene
3. Play the Scene
4. Double tap the upper left corner
5. Double tap the opposite corner
6. The Input.mousePosition is always one frame behind the state of the button being pressed
Expected result: Windows touch input events and positioning events should be synced
Actual result: Always one frame behind the state of the button being pressed
Note:
Tested with Surface 3
Reproduced with: 5.6.0p1, 2017.1.0b1
Not reproduced with: 5.5.3p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
- Broken compute shaders propagate via the cache server
Add comment