Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.20f1
2022.2.0b12
2023.1.0a15
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-17069
Regression
No
[Android] ViewportPointToRay coordinates are incorrect when TargetDisplay != 0
How to reproduce:
1. Open the attached “test_13420.zip“ project
2. Build and Run the “SampleScene“ Scene on Android
3. In the Scene check the “Toggle“ box
Expected result: “Hit succeeded“ is printed in the Scene
Actual result: “Failed to Hit“ is printed in the Scene
Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a15
Reproducible with these devices:
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Not reproducible with these devices:
VLNQA00494 - iPhone 14 Pro Max, 16.0 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
iPhone 12 Pro (iOS 14.2.1)
iPhone 13 Pro (iOS 15.6.1)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Closing as the issue is not widespread and bug is old and no resources are allocated to fix it.