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.
Comments (4)
-
nehasing
Mar 22, 2024 06:25
I had never read any post before, but ever since I read your article, it has become more useful to me. Thank you.
-
agratajcityour
May 25, 2022 06:53
Superb blog
-
MonkeyYao
Apr 22, 2019 03:04
Dell XPS 15 with touch sreen. The touch size can be obtained by flash.events.TouchEvent .sizeX and flash.events.TouchEvent .sizeY in the Adobe Flash.but Touch.Radius returns 0 in Unity.
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
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
- No longer able to change the Toggle or Slider GameObjects' Target Graphic value and a NullReferenceException is thrown when the Target Graphic value is set to None at any point
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.