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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment