Search Issue Tracker
In Progress
Under Consideration for 3.0.X, 3.1.X
In Progress in 3.2.X
Votes
0
Found in [Package]
3.0.5
3.1.1
3.2.0-pre.1
Issue ID
XRIT-250
Regression
No
"Select Exited" is not called when manually touching a GameObject that is using XRSimpleInteractable in the Player
How to reproduce:
1. Open the attached “IN-95686.zip” project
2. Build and Run the project with the “TestScene” Scene added
3. In the Player physically touch the Cube GameObject
4. Observe the Cubes color
5. Pull away your hand and observe the Cubes color
Expected result: The Cube GameObject turns back to white
Actual result: The Cube GameObject stays green after no longer touching the Cube
Reproducible with: 2.0.4 (6000.0.41f1), 2.1.2 (6000.0.41f1, 6000.1.0b9, 6000.2.0a6)
Couldn’t test with: 1.3.11 (2022.3.58f1) - “Unable to resolve reference 'Unity.PolySpatial'.” error is thrown
Reproducible on: Apple Vision Pro 2.3.1
Testing environment: macOS Sequoia 15.3 (M3 Pro)
Comments (1)
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
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
chris-massie
Mar 13, 2025 00:34
In the project submitted, the Pokeable Cube (XRSimpleInteractable) has a child GameObject used as the poke collider. That child GameObject Transform has a position offset that is causing the bounds to be incorrectly computed in the XR Poke Filter component. As a workaround for this issue until it is fixed in a new package version, zero out the offset on the collider's Transform. Then adjust the Poke Direction value on the XR Poke Filter to be the expected axis you want the user to poke from (e.g. X).