Search Issue Tracker
Fixed in 1.1.0-pre.4
Votes
0
Found in [Package]
3.2.17
Issue ID
1308480
Regression
No
[XR SDK] Tracked Device Raycaster does not work correctly with Worldspace Canvas when XR Camera is offset from origin
Reproduction steps:
1. Open the attached project ("1308480.zip")
2. Open the "SampleScene" scheme
3. Enter Play mode
4. Using the mouse, try to select/hover over any of the white tiles
Expected result: White tiles can be selected/hovered
Actual result: The selection point is offset and it's impossible to select the correct tile (see "6oX4ZBgNm5.mp4" video)
Reproducible with: XR SDK 3.2.17, 4.0.0-pre.3 (2019.4.20f1, 2020.2.4f1, 2021.1.0b7, 2021.2.0a4)
Not reproducible with: 2018.4.32f1 (XR SDK not available)
Note:
- After moving the headset no tiles can be selected
Tested:
- Oculus Rift S
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 1.1.0-pre.4):
Fixed with Input System 1.1.0-pre.6 (2020.3.18f1)