Search Issue Tracker

Fixed

Fixed in 3.3.0

Votes

4

Found in [Package]

3.2.0

Issue ID

XRIT-322

Regression

No

[XRIT] NearFarInteractor created "Attach" and "Stabilization Cast Origin" objects are not destroyed when NearFarInteractor is destroyed

Package: XR Interaction Toolkit

-

Steps to reproduce:
1. Open the attached user's project "Test XRIT.zip"
2. Connect Quest 2/3/3S to Meta Link
3. Open "Assets/_AssetsForReport/TestScene.unity" and enter Play Mode
4. Observe in the Hierarchy the creation of NearFarInteractor object, it then creates "Attach" and "Stabilization Cast Origin" objects under XR Origin object
5. Observe the previously created NearFarInteractor objects get destroyed

Expected result: created at step 4 "Attach" and "Stabilization Cast Origin" objects are destroyed
Actual result: created at step 4 "Attach" and "Stabilization Cast Origin" objects are not destroyed (See attached Repro.mp4)

Reproducible with: XRIT 3.0.8 - 3.2.0 (6000.0.54f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3)
Could not test with 2.6.4 and below due to scripting errors after downgrading (relating to NearFarInteractor)

Environment tested: Windows 11 24H2

Notes:
-NearFarInteractor always creates attach and stabilization objects under the XR Origin. Even when those interactor is not connected to XR Origin and belongs to some other game entity.

  1. Resolution Note (fix version 3.3.0):

    Fixed the Near-Far Interactor components to destroy the `Attach` and `Stabilization Cast Origin` GameObjects under the XR Origin that it creates when it is destroyed. This fix added new `OnDestroy` methods to `InteractionCasterBase` and `InteractionAttachController`. Users who had already implemented either method in derived classes will need to call the base method.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.