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
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
- A particle is not rendered for the first frame when the duration and lifetime values match
Resolution Note (fix version 0.10.0-preview.3):
Fixed with 2019.4.14f1 (0.10.0-preview.7)