Search Issue Tracker
Fixed in 0.9.0-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1091903
Regression
No
[Windows][Touch] A new touchId isn't assigned to stylus input after the "Ended" state.
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/170
Original Title: A new touchId isn't assigned after the "Ended" state if between taps the distance between the screen and the pen is very little
Device: Microsoft Surface Pro (Model: 1796) + Microsoft Surface Pen (Model: 1776)
There's this special behaviour with surface pro, where it detects input even if the stylus is not touching the screen directly (dot shaped cursor)
When you stop touching (with the distance between the screen and pen being up to 1cm or so) it switches to "Ended". BUT, when you touch again, it gets the same ID, unless you make the aforementioned distance larger (and the dot shaped cursor disappears) then touch again.
I'm not sure if it's intended
Rene-Damm commented on Jul 18
ATM we don't really have stylus support/handling in the Windows touch input code path. So, not surprised that we're getting into issues when the "touches" are actually coming from the pen. Anyway, ultimately the code should handle that reliably so the reuse of IDs here is likely to be an issue we want fixed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment