Search Issue Tracker
Fixed in 0.9.0-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1091906
Regression
No
[Windows][Touch] touch.pressure is always reported as 0
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/171
Device: Microsoft Surface Pro (Model: 1796) + Microsoft Surface Pen (Model: 1776)
Pressure is always reported as 0
Rene-Damm commented on Jul 18
The Windows 7 touch API does not support pressure. I think what we ultimately want is Windows 8+ pointer API-based touch support. Unfortunately, as long as we haven't dropped Win 7 support (which likely won't be the case for quite a while), that'll mean that the touch codepath will get split in two, making it quite likely the old Win7 codepath will break more often.
Anyway, something to look into. For now, as long as we support pressure on pens, I'm not terribly concerned about not supporting pressure on touch.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment