Search Issue Tracker
Fixed in 1.0.0-pre.3
Won't Fix in 0.9.X
Votes
0
Found in [Package]
0.9.4-preview
Issue ID
XRIT-2
Regression
No
[XR Interaction Toolkit] Custom reticle gets displayed on objects without a custom reticle and without the ability to teleport
Repro steps:
1. Open user attached project
2. Build and Run on Quest
3. Target the controller to the floor and notice the custom reticle
4. Target the controller to the cube
Actual: When targeting the teleportation ray to the cube at a certain angle the custom reticle gets shown but you can't teleport to it
Reproducible with: 2019.3.16f1, 2020.1.0b12, 2020.2.0a13 - XR Interaction Toolkit - 0.9.4
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note:
Fixed by addition of property on the XR Ray Interactor called hitClosestOnly: Enable this to make only the closest Interactable receive hover events. Otherwise, all hit Interactables will be considered valid and this Interactor will multi-hover.
Checking this box will send OnHoverExit events to the interactable with the custom reticle that is no longer the closest interactable as before.
Resolution Note (0.9.X):
Not backporting to previous releases.
Resolution Note:
This issue was actually resolved back in 1.0.0-pre.3 with the addition of the 'Hit Closest Only' checkbox added to the XR Ray Interactor. Checking this box will prevent the incorrect reticle from showing on an unintended interactable object.