Search Issue Tracker
Fixed in 0.10.0-preview.3
Votes
0
Found in [Package]
0.9.4
Issue ID
1252532
Regression
No
[XR Interaction Toolkit] "m_StopLineAtFirstRaycastHit" variable is not used anywhere in "XRInteractorLineVisualEditor.cs"
Reproduction steps:
1. Create a new project
2. Install XR Interaction apckage
3. Find and open "XRInteractorLineVisual.cs" file in packages folder
4. Find "m_StopLineAtFirstRaycastHit" boolean variable
5. Find and open "XRInteractorLineVisualEditor.cs" file in packages folder
Expected result: "m_StopLineAtFirstRaycastHit" variable is exposed in "XRInteractorLineVisualEditor.cs" file
Actual result: "m_StopLineAtFirstRaycastHit" is not used anywhere
Reproducible with: XR Interaction Toolkit 0.9.4 (2019.4.7f1, 2020.1.1f1, 2020.2.0a20)
Could not test with: 2018.4.26f1 (XR Interaction Toolkit not available)
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
- "Fatal signal 6 (SIGABRT)" is shown in the Console instead of crash details when "androidChainedSignalHandlerBehavior" is set to "legacy"
- BakeTrailsMesh Errors in the console when the Trails module of the particle system is enabled, the Mode is set to Ribbon and it's count is more than 1
- Global shortcut bind is set to default instead of previous value when setting it to a disallowed key
- Shortcut bind is removed when editing shortcut and clicking outside the Shortcut Manager window
- MeshColliders ignore contactOffset when Rest Offset > 0 on TerrainCollider causing jitter
Resolution Note (fix version 0.10.0-preview.3):
Fixed with 2019.4.14f1 (0.10.0-preview.7)