Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.7f1
Issue ID
1084761
Regression
No
[HoloLens] Tracking Loss image is rendered behind game object
Steps to reproduce:
1. Download attached project
2. Switch platform to UWP and build project
3. Deploy to HoloLens
4. When app launches cover HoloLens sensors
Expected results: Tracking Loss image renders on top of all other app content.
Actual results: Tracking loss image will be displayed 'underneath' game object.
Reproducible when game objects material's render queue is >2000
Reproduced with: 2019.1.0a2, 2018.3.0b3, 2018.2.8f1, 2018.1.9f2, 2017.4.12f1
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 (2018.3.X):
We are no longer fixing issues in 2018.3. If your issues still occurs in Unity 2018.4 or Unity 2019.3 and greater, please re-submit your bug for consideration.