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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
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.