Search Issue Tracker
Feature Request
Feature Request in 2021.2.X
Votes
6
Found in
2019.4.19f1
2020.2.3f1
2020.3.0f1
2021.1.0b5
2021.2.0a4
Issue ID
UUM-1501
Regression
No
[XR SDK] CameraWorldToScreenPoint returns offset coordinates
Reproduction steps:
1. Open the attached project ("1304082.zip")
2. Open the "SampleScene" scene
3. Enter the Play mode
4. Select the "Sphere" Game object in the Hierarchy window
5. Change X or Y Position values so that the Sphere Game object is on the edge of the screen
6. Observe Output values in the middle of the game window
Expected result: Output value should be (0.0|1.0,...) or (..., 0.0|1.0)
Actual result: Output value never reaches 0.0 or 1.0 corrdinates (see "2021-01-29 13-44-45.mp4" video)
Reproducible with: 2019.4.19f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4
Not reproducible with: 2018.4.31f1 (XR SDK not available)
Tested:
- MockHMD
- Oculus Rift S
- Acer WMR
Comments (2)
-
tmarlok
Aug 20, 2022 10:58
Same problem with cable-linked Meta Quest2.
-
dhami-nitin
Jun 17, 2022 12:54
The same issue exists for Neal glasses as well,
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
We have created a feature request to explore enabling CameraWorldToScreenPoint functionality in XR
Resolution Note (2021.2.X):
We have created a feature request to explore enabling CameraWorldToScreenPoint functionality in XR