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.
HoloLensInputModule in latest HoloToolkit broken?
So I grabbed the latest version of HoloToolkit from Github to start a blank new Hololens project in 5.4.0b8HTP and when I follow these instructions:
http://forum.unity3d.com/threads/unity-ui-on-the-hololens.394629/
They simply don't work anymore. The older version of HoloToolkit included with HoloAcademy 240 etc. works fine. But with this latest version, it seems that it does not raycast into the World Space GUI correctly. The cursor either never collides with the canvas, or if it does, the active GUI elements do not get highlight until the cursor is WAY off.
I'm probably doing something wrong here--but I've boiled it down to just a basic scene with a canvas with a single button, hololensinputmodule on the event system, gaze manager on the camera, cursor prefab and the cursor never hits the canvas.
ralphbarbagallo.com - flarb.com - @flarb
Best Answer
-
Options
Flarb
✭
Yes, I do mean 18-HTP
So--apparently it turns out the problem is I'm testing in the Editor using my Rift headset (CV1). It used to work in 16, but now in 18 it's unsupported. The GUI works on the device, just not in the editor using Rift.
PUHLEEEEEZZZEE can Microsoft make the Rift and HoloLens SDKs work nicely in the editor together? It's SUPER convenient to be able to test in Editor using the Rift. It would be even cooler if there was some kind of rift compatibility mode where it would display a box around the FOV to know when the objects are outside of a real HoloLens display's FOV.
Being able to test on the Rift makes iteration time so much faster than compiling and deploying to the device all the time.
ralphbarbagallo.com - flarb.com - @flarb
5
Answers
@Flarb does your bare bones test app behave differently when run on the side by side older 10.0.11082.1039 version of the emulator?
I also gather you mean 5.4.0b18-HTP (instead of 5.3.0b8-HTP) of the Unity HoloLens beta bits?
Do you believe it is the new emulator or the new Unity bits?
I gather since you haven't mentioned the device that you have not run this test on either the initial shipping version of the OS on the device or the May Update of the OS?
Windows Holographic User Group Redmond
WinHUGR.org - - - - - - - - - - - - - - - - - - @WinHUGR
WinHUGR YouTube Channel -- live streamed meetings
Yes, I do mean 18-HTP
So--apparently it turns out the problem is I'm testing in the Editor using my Rift headset (CV1). It used to work in 16, but now in 18 it's unsupported. The GUI works on the device, just not in the editor using Rift.
PUHLEEEEEZZZEE can Microsoft make the Rift and HoloLens SDKs work nicely in the editor together? It's SUPER convenient to be able to test in Editor using the Rift. It would be even cooler if there was some kind of rift compatibility mode where it would display a box around the FOV to know when the objects are outside of a real HoloLens display's FOV.
Being able to test on the Rift makes iteration time so much faster than compiling and deploying to the device all the time.
ralphbarbagallo.com - flarb.com - @flarb