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.
Hololens frustum is set below my head
I'm gaining experience with the Hololens by creating a simple app. The only object in this app is a 3d cube. The cube has a position of X:0, Y:0, & Z: 2. But when I deploy the app to my Hololens it appears in front, above my head, and to the right. Even if I set the position to 0,0,0 it appears above my head and to the right.
Looking at the 3D View on the Hololen's tools webpage I noticed the following.
Namely that the floor is too high and the frustum is set below my head. I re-ran the configuration to see if that would solve the issue with no luck.
What would cause this to occur? How can I resolve it?
It seems like the spatial data is incorrect. This is not a problem in the Hololens emulator. It also does not seem to affect the native Holograms.
Best Answer
-
Options
Found that by running a reset on the Hololens itself this problem was resolved. Not sure what caused it to occur in the first place.
5
Answers
Can you verify that your Main Camera position is still set to 0,0,0??
Sorry Jesse I should have mentioned that. I can confirm the camera is at 0,0,0. This is one thing that popped up as maybe causing the problem so I made sure to verify it's correct.
Found that by running a reset on the Hololens itself this problem was resolved. Not sure what caused it to occur in the first place.
there also a bulit-in app called Sensor Tuning may help you.
At the time I tried the sensor tuning but it did not resolve the issue.
If you hit this issue in the future, please file a feedback using the Feedback Hub app.
Will do. But have not seen a repeat so far.