Search Issue Tracker
Fixed in 2019.3.X
Votes
1
Found in
2017.4.0f1
2018.2.2f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1119934
Regression
No
Touch.Radius is always 0 when using Windows touch screen
How To Reproduce:
1. Open the "SampleScene" in the attached "TouchSizeTest.zip" Project on a Windows device with a touch screen
2. Enter Play Mode
3. Try to touch somewhere on the Game View
4. Observe the Console
Expected behavior: Valid touch radius is shown in the console
Actual behavior: Touch radius is always shown as 0
Reproducible with: 2017.4.19f1, 2018.3.2f1, 2019.1.0b1, 2019.2.0a2
Note: Tested on the Windows OS device Surface Pro. Touch.RadiusVariance behaves the same as Touch.Radius.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2019.3):
Touch.Radius hadn't been implemented since many Windows touch devices doen't seem to support it.
The Surface line of devices does support this API, and so it will now return non-zero values for both the Editor and Standalone player when running on a 'Surface'. However, for other touch-enabled devices, it may still return 0.