The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Unity Far Plane Clipping Way too Short
Acer headset. Windows build 16275.rs3_release.170822-1423. Unity 2017 2.0b9.
After Windows updated, Unity has error in Player:
Failed to get rendering parameters for main camera - view transforms may get out of sync! Error code: '0x8000000e'
The far clipping plane is a few meters away meaning the scene only renders a few meters and then clips out. Adjusting it larger than 1000 does not affect it.
All worked well on Unity 2.0b5 prior to Windows update. Once Windows updated, Unity 2.0b5 started flickering violently in the Player making it unusable. Verified on 2 systems with 2 seperate headsets - same versions of software and operating systems, Upgraded Unity to 2.0b8 which introduced the clipping issue. Upgraded to 2.0b9 and the issue still exists. Is anyone else experiencing this? I find it odd that it is present on both my systems and both headsets.
Best Answer
-
Options
Jesse_McCulloch
admin
Yes, the far clipping plane being set to 20m and the error about the camera transforms are known issues. Flipping plane was introduced in b7, camera error in b8.
These are both unity errors that we ate waiting on them to resolve.
I never had the shaking issue myself, but I understand that was a unity issue as well.6
Answers
These are both unity errors that we ate waiting on them to resolve.
I never had the shaking issue myself, but I understand that was a unity issue as well.