Search Issue Tracker
By Design
Fixed in 2.3.1
Votes
0
Found in [Package]
3.0.6
Issue ID
1219811
Regression
No
[XRSDK] Initialize on Startup toggle is being ignored with boot.config is generated
1. What happened
boot.config should not contain the following lines when "initialize on startup" is unchecked and a build is made
1) early-boot-windows-holographic=1
2) force-primary-window-holographic=1
2. How we can reproduce it using the example you attached
- open attached project
- verify platform loader is added to the providers list
- uncheck "initialize on startup" if it's checked
- build the project
- open the VS SLN
- open boot.config
- verify the above lines are present
expected result:
the two lines above are not present when "initialize on startup" is off
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
- "DirectoryNotFoundException" is thrown and Shader Graph does not open when opening a .shadegraph from a long path
- “Full Screen Pass Renderer Feature_Old GUID” text is cut off in Renderer Features window
- "Undo: Already found nextRootTransform, but with different state cached" error thrown when undoing changes made to the Hierarchy using a script
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
Resolution Note:
Initialize on startup does not control early-boot-windows-holographic. force-primary-window-holographic is controlled by the Use Primary Window toggle under Windows Mixed Reality settings and does work properly.
Resolution Note (fix version 2.3.1):
Initialize on startup does not control early-boot-windows-holographic. force-primary-window-holographic is controlled by the Use Primary Window toggle under Windows Mixed Reality settings and does work properly.