We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
HoloLens Cursor Issue
In my current scene, for some reason when I added the DefaultCursor it only shows up when I am 'travelling backwards'. Tested in both Unity (using HoloLens Camera GazeControls) and in HoloLens emulator.
It is as if the cursor is inside the camera so it can only be seen when it trails slightly behind.
I did manage to get around it by setting Surface Cursor Distance to 0 however I wasn't able to interact with the UI elements I added. I'm hoping that has something to do with my Surface Cursor Distance work-around.
I created a test scene with nothing but the cursor and some UI elements and it works perfectly so any hints as to what could be causing the problem would help.