Search Issue Tracker
By Design
Votes
0
Found in
5.4.0b1
Issue ID
756050
Regression
No
altitudeAngle and azimuthAngel variable of Input.GetTouch always return unexpected values
1. Run the attached project (or use any script that shows values of altitudeAngle and azimuthAngel variable of Input.GetTouch) on iOS and Android devices
2. Check what values of altitudeAngle and azimuthAngel variable are while you touch the screen of the devices
Actual result:
1. Input.GetTouch (i)..altitudeAngle is always 0 on iOS
2. Input.GetTouch (i).radiusVariance is always NAN on Android
Input.GetTouch (i).radiusVariance is always 0 on iOS
altitudeAngle of the 1st touch is 1.401298E-45, and 0 the rest touches on Android
3. Input.GetTouch (i) azimuthAngel is always 0 both on iOS and Android
Platforms: iOS, Android
Devices: iPhone 5S, iPad 2, Sony Xperia 1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment