Search Issue Tracker
Fixed
Fixed in 2.4.0
Votes
0
Found in [Package]
2.3.1
Issue ID
XRIT-71
Regression
Yes
Distance not calculated correctly between the interactor and interactable object when using XRDistanceEvaluator
Reproduction steps:
1. Open user attached project "TestTargetFilter.zip"
2. Open Window > Analysis > XR Interaction Debugger
3. In the XR Interaction Debugger window make sure Target Filter is selected
4. Enter Play mode
5. Move your left controller so it intersects with both intractable cubes in the scene
6. In the XR Interaction Debugger select and expand the “DirectInteractior”
Expected result: Values change dynamically and are different for both cubes
Actual result: Both cubes return 0 value
Reproduced with: 2.3.0 (2022.2.10f1), 2.3.1 (2021.3.24f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a12)
Could not test with: 2.2.0 (2022.2.10f1) (issues with script), 2.3.0-pre.1 (2022.2.10f1) (issues with script), 2.3.0 (2020.3.47f1) (issue with Oculus)
Reproducible on: Windows 10
Note: User mentioned, that this issue seems to be a result of the following change made in 2.3.0-pre.1:
Changed XRInteractableUtility.TryGetClosestCollider and XRInteractableUtility.TryGetClosestPointOnCollider to ignore trigger colliders.
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] Audio sound is lower in the Player compared to the native music player
- Feet slide and misalign when playing retargeted animations
- IndexOutOfRangeException is thrown in NativePassCompiler when a graphics buffer is used in more than 5 render passes
- "Undo Stack Overflow" error is thrown, and Undo History is deleted when multiselected GameObjects are reparented to their GrandParents
- SearchColumn of type "ObjectReference" does not get refreshed for the custom SearchProvider when lighting generation finishes
Resolution Note (fix version 2.4.0):
Added an additional struct to check the scope of using trigger colliders during this calculation. Adding this fixes the issue with the XR Distance evaluator not calculating the proper distance from trigger colliders.