Search Issue Tracker
Fixed
Fixed in 3.0.4
Votes
2
Found in [Package]
3.0.2
Issue ID
XRIT-154
Regression
No
[Quest] Can Hover or Select XRInteractables through GameObject with a collider when the NearFarInteractor is used
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/XR Interaction Toolkit/3.0.3/Starter Assets/DemoScene.unity” Scene
3. Enter the Play Mode
5. Use the right controller’s thumbstick to move closer to the grey cube and quad
6. Try interacting with Interactable objects through grey quad or cube
Expected result: The Interactable objects cannot be hovered/selected
Actual result: Can Hover and Select Interactable objects
Reproducible with: 3.0.0-pre.1 (2021.3.35f1), 3.0.3 (2021.3.38f1, 2022.3.28f1, 6000.0.1f1)
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Play Mode
Android Player
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Resolution Note (fix version 3.0.4):
Fixed an issue where the Near-Far Interactor would not be properly blocked by non-interactive 3D obstructions during far interactions.