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
- [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
- [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”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 0.10.0-preview.3):
Fixed with 2019.4.14f1 (0.10.0-preview.7)