Search Issue Tracker
Duplicate
Duplicate in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2018.1
Issue ID
1186686
Regression
Yes
Jitter/Instability when using Shared Depth Buffer for HoloLens/
Forum post: https://forum.unity.com/threads/unity-2018-3-and-hololens-holograms-are-not-stable.647734/
Favro Card: https://favro.com/organization/c564ede4ed3337f7b17986b6/2cb994fca38e514c8629373e?card=Uni-98229
Since the introduction of 2018, there has existed a bit of instability in the rendering of Holograms on HL devices. The worse case was for v2 devices brought up by Microsoft early in 2019 development. The fix at the time was to strip out the second call to UpdateCurrentPrediction. This stabilized v2 rendering but did not fix the stability issue in v1.
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
This is a duplicate of issue #1174865