Search Issue Tracker
Fixed in 1.0.0-pre.2
Votes
0
Found in [Package]
0.9.4
Issue ID
1231482
Regression
No
[XR Interaction Toolkit] Adding an XRGrabInteractable to Game object in Play mode does not work
How to reproduce:
1. Open attached project ("UnityBugXRGrabInteractableFails.zip")
2. Open SampleScene scene
3. Enter Play mode
4. Pick up the cube with the right controller
5. Release cube
6. Pick up the cube with the right controller
Expected result: Cube is picked up
Actual result: Cube stays on the ground
Reproducible with: 2019.3.9f1 (0.9.3), 2020.1.0b5 (0.9.4), 2020.2.0a7 (0.9.4)
Could not test with: 2017.4.39f1 (Packages are not present), 2018.4.20f1 (No XR Interaction package)
Notes:
- Tested with Oculus Rift
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Resolution Note (fix version 1.0.0-pre.2):
The problem was caused by the project adding a Grab Interactable component to a parent GameObject that shares Colliders with the child Grab Interactable. However, the initial child Interactable would only unregister from the Interaction Manager during OnDestroy, which is invoked later after the Destroy call. When the new Grab Interactable was registered with the Interaction Manager, its Colliders list conflicted with the still registered child Interactable.
With changes made with 1.0.0-pre.2, the Interactable will unregister during OnDisable, which is invoked immediately. The new Interactable is thus able to associate the Collider with it.