Search Issue Tracker
Fixed in 2019.4.X
Fixed in 2020.3.X, 2021.1.X
Votes
8
Found in
2019.3.2f1
Issue ID
1223767
Regression
No
Enabling Graphics Jobs in 2019.3.x results in a crash (or nothing rendering) on HoloLens 2
1. What happened
When creating a new project in 2019.3.x Graphics Jobs are enabled by default. Having graphics jobs on and launching to HoloLens 2 results in either nothing rendering or a crash in the Unity player.
2. How we can reproduce it using the example you attached
- Build and launch the SampleScene onto a HoloLens 2
- Note the player crashes or runs and renderings nothing.
- Go back to the Unity editor and disabled Graphics Jobs under Project Settings->Player->Other Settings->Graphics Jobs
- Build and launch the SampleScene again for HoloLens 2
- The player now renders the scene appropriately.
Reproduced in Built-in XR
Have not confirmed if this occurs in XR SDK
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
- GameObject is not being rendered through render texture when Upscaling Filter is set to Spatial-Temporal Post-Processing and Alpha processing is enabled
- [Android] The external monitor does not display a secondary display when the monitor is reconnected in the Player
- Layer render order is not respected inside the Android Player when using GPU Resident Drawer.
- “You are not using the recommended Android NDK, versions other than 27.2.12479018 are not officially supported.” warning is still displayed when Android SDK is set to the correct NDK version manually
- OnWillSaveAssets receives an empty paths array when saving a new Scene
Resolution Note (fix version 2019.4):
Now the proper multithreading system will be used for hololens 2