Search Issue Tracker
Fixed in 4.1.0
Votes
1
Found in [Package]
4.0.1
Issue ID
1343655
Regression
No
[XR][Management]No proper way to list assigned XR providers
How to reproduce:
1. Open the attached "XR-Framework-2020.3.zip" project
2. Open the console Window
3. Open the Project Settings -> XR Plug-in Management
4. Open the "Toggle" Script
5. In Editor click on the MenuItem "XR -> Enable WMR" to call "XRPackageMetadataStore.AssignLoader" to enable the Windows Mixed Reality Provider
6. Click on "XR -> All Loaders" from the Menu Bar to print all active loaders to the Console Window
7. Compare the console output ("Windows MR Loader") with the used argument for "XRPackageMetadataStore.AssignLoader" in the "Toggle" script (Static string with value "WindowsMRLoader").
Expected result: "XRManagerSettings.activeLoaders -> XRLoader.name" returns the same string, as used for "XRPackageMetadataStore.AssignLoader"
Actual result: "XRManagerSettings.activeLoaders -> XRLoader.name" and required string argument for "XRPackageMetadataStore.AssignLoader" and "XRPackageMetadataStore.RemoveLoader" differ
Reproducible in: 2019.4.28f1 (4.0.1), 2020.3.13f1 (4.0.3), 2021.1.13f1 (4.0.5), 2021.2.0b1 (4.0.5)
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
- UI Toolkit Button text is not rendered when the Button has fixed height with specific Icon font
- Unable to bind RenderTexture to the VisualElement's StyleBackground property
- SVG fails to import when 'stroke-miterlimit' is less than 1
- Test Runner fails to create a script in the active path when selecting a file as the active path
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
Resolution Note (fix version 4.1.0):
Added public APIs to get the raw package metadata information. This allows for users gather and to pass correct information to the rest of the APIs without having to manual dig for the information.