Search Issue Tracker
Fixed in 2018.1.X
Votes
52
Found in
2017.2.0p1
2017.2.1f1
Issue ID
982876
Regression
Yes
HoloLens jittering 3D model causing color separation possibly due to incorrect stabilization plane
1. What happened
3D models are jittering and much more unstable than before the 2017.2.0p1 release. The jittering causes extreme color separation on the HoloLens.
This issue applies to these Unity versions 2017.2.0p1, 2017.2.0p4, 2017.2.1f1, 2017.3.0
It does NOT happen when the project is build with 2017.1.1f1, 2017.1.2p4, 2017.2.0f3 so you may want to look at the differences between 2017.2.0f3 and 2017.2.0p1
2. How we can reproduce it using the example you attached
Run the attached project on the HoloLens and wait for the white sphere to appear in front of you. Walk a few steps to the right or the left and see that jittering becomes worse at an angle of 45 degrees from the initial direction. If you move my head from left to right across that particular spot youcan trigger it again. Because of the rapid movement of the model it is experienced as extreme color separation when wearing the HoloLens, but I recorded a video of it and that showed that model quickly slides away and then comes back.
I looked at the stabilization plane that is used by running the HoloLens device Portal. It looks like the stabilization plane moves behind the viewer instead of staying in front. This may cause the instability.
-
JeffreyJacobson
Apr 28, 2018 20:31
Nikos,
Earlier, I built my project in 2017.2.1p2 and saw this bug, exactly as described.
I just installed 2017.2.2p1 and opened my project there, and the colors do not separate! Very nice.
But my Vuforia object, a simple cube, does seem to drift. I have extended tracking on, so when I take the marker away, the cube drifts only a little. Looks like Vuforia successfully made the handoff to Hololens tracking! Again, excellent.
That said, I'll still want to anchor the object and turn Vuforia off for performance reasons. It would be great if this could be done with a single call to Vuforia, rather than having to mess with world anchors and such.
Thanks to you and your team for all the hard work.
-
John-Unveil
Feb 14, 2018 19:42
We've been having this issue as well. It's forced us to backport our Hololens app to Unity 5x, which is not ideal. When is this issue going to be fixed?
-
jghospital
Feb 08, 2018 11:19
When is the fix version going to be released?
-
RussellXie_7
Feb 07, 2018 20:17
Exactly same issue. Even the simplest build of HoloLens project are super jittering with Unity 2017.3.0, which is not happening on 2017.1.1
-
shaddad
Jan 25, 2018 17:04
Can someone link a URL to the duplicate for this? I can't find it.
-
jghospital
Jan 25, 2018 14:09
+1 How can I solved it or vote for that issue? I can't find the duplicated one.
-
KBVDev
Jan 19, 2018 18:12
I'm also experiencing this issue. Where is the link to the issue? :)
-
Xinli
Jan 19, 2018 02:34
+1. Having this annoying problem.
-
lbrahim12
Jan 15, 2018 14:21
برنمج جيد
-
HighSkillz
Jan 13, 2018 18:49
We encountered this problem as well... Too bad we cannot vote on this for being a duplicate
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Unity-Nikos
Mar 04, 2018
The link to the duplicate is not shown because the duplicate ticket is not public. Sorry about that. I can verify that it is fixed and backported to 2018.1.0b7, 2017.3.1p1 and 2017.2.2p1