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
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Add comment