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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment