Search Issue Tracker
Fixed in 1.0.0-pre.3
Votes
2
Found in [Package]
1.0.0-pre.2
Issue ID
1312217
Regression
No
[XR Interaction Toolkit] XRRayInteractor interacts with Interactables when the GameObject is behind UI element
Reproduction steps:
1. Open the attached project "case_1312217.zip"
2. Load the "UI Interaction" scene
3. Enter Play mode
4. Try grabbing the red cube GameObject behind UI using XR controller
Expected result: XR controller cannot interact with the red cube
Actual result: XR controller grabs the red cube
Reproducible with: XR Interaction Toolkit (2019.4.18f1, 2020.2.4f1, 2021.1.0b6, 2021.2.0a4)
Could not test with 2018.4.30f1 (XR Interaction Toolkit not available)
Tested with:
- Oculus Touch Controller
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.0.0-pre.3):
This has now been fixed. As an important point of clarification, a UI element must have a "Tracked Device Graphic Raycaster" component to block interactions with the objects behind it. When adding GameObjects for UI, if you use the XR submenu, this will be part of the object automatically. Otherwise, you will have to add this component separately.