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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.10.0-preview.3):
Fixed with 2019.4.14f1 (0.10.0-preview.7)