Search Issue Tracker
Won't Fix
Won't Fix in 2.4.X
Votes
0
Found in [Package]
2.4.0
Issue ID
XRIT-79
Regression
Yes
[Quest] [XRInteractionToolkit] isTrigger Collider not working when the version is 2.3.1 and above
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Connect Oculus device to PC with Oculus Link
4. Enter the Play Mode
5. Click on each Cube with XR Controller’s Trigger button
Expected result: All Cubes turn Green after clicking them
Actual result: Only the Cube that has isTrigger false on the Collider will turn Green
Reproducible with: 2.3.1 (2023.2.0a23), 2.4.0 (2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23)
Not reproducible with: 2.3.0 (2022.2.16)
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Notes:
- The problem seems to be caused by XRBaseInteractable not linking/adding the Collider to “Colliders” on Awake, in the XrEditorNodeEvent Script on the Cubes, adding the Collider by hand will fix the problem
- In XrInteractionToolkit 2.2 and below the Editors will auto Link, but in 2.3.1 and above it will only auto Link isTrigger=false Collider
- Reproduces in Windows Standalone Player
- Reproduces in Android Player
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
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2.4.X):
There are no fixes planned for this Bug