Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.5.1
Issue ID
ISXB-467
Regression
Yes
Screen position starts from around 30,30 instead of 0,0 with mobile devices
*Steps to reproduce:*
# Open the "[InputSystem-TestProject|https://github.cds.internal.unity3d.com/unity/InputSystem-TestProject]" project
# In File > Build Settings switch to Android Platform
# Build and Run to the device
# Select "Touchscreen" from the list
# Press on the bottom left corner
# Observe the "screenPosition" value
*Expected:* "screenPosition" value is (0,0)
*Actual:* "screenPosition" value is around (30,30)
*Reproducible with:* 1.5.1(2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a10), 1.6.0(2023.2.0a10)
*Not reproducible with:* 1.5.0(2020.3.47f1, 2021.3.22f1, 2022.2.13f1)
*Reproducible with devices:*
- VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 13
- VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 12
- VLNQA00230 - OnePlus 6T (ONEPLUS A6013), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9.0.0
- VLNQA00119 - Xiaomi Mi 5 (MI 5), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 8.0.0
- VLNQA00090 - Samsung Galaxy S8 (USA) (SM-G950U), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 7.0.0
- VLNQA00352 - iPhone 12 Pro (MGML3ET/A), CPU: A14 Bionic, GPU: Apple designed
- VLNQA00346 - iPad Air (4th generation)
- VLNQA00258 - iPhone Xs Max (MT502ET/A), CPU: A12 Bionic, GPU: Apple designed, OS: 13.2
*Not reproducible with devices:*
- Macbook Pro, M1 Max, OS: 13.2.1
- Lenovo Chromebook Duet 2 in 1. Laptop; Tablet. 103.0.5060.64 (32 bit). Android version 9. Build number: R103-14816.82.0
*Notes:*
- On Samsung devices also tested with the S-pen, values are still incorrect
- With 2020.3, 2021.3 versions, values are a little bit lower, but never zero
- With iPad value is lower, around (5,15)
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
- [Silicon] Crash with multiple StackTraces when entering Play Mode in a project with corrupted FBX files
- Index Out Of Range exception when trying to use Rendering Layer Override in Probe Adjustment Volume without a mask defined in lighting settings
- [Android] [Vulkan] [WebCamTexture] "WebCamTexture.Play" crashes the application when the camera is started
- Huge performance overheads appear when there is a large amount of bindings in the UI Toolkit
- Visual Effects Graph Blackboard can't be scrolled horizontally
Resolution Note:
Round corners means (0,0) is not reachable.