Hello, I will have soon a AR project in my hands. The initial idea was to do it with the original hololens(hololens 1 ? ) but Microsoft stopped selling it at their store so we waited for them to announce hololens 2. My biggest fear right now is when Unity will provide support for them. We can wait a bit but not too long. Anyone knows anything about this?
The HoloLens 2 is not likely to come out until Q3 this year anyway based on news sources so if its going to be with you soon you should just buy some HoloLens via a reseller
The burning question remains: Now that HoloLens 2 was unveiled, will Unity support it? Strangely enough Tim Sweeney from Epic was on the stage. No mention of unity (couldn't even see the logo on the background screen)
Unity already supports HoloLens, although for this device you'll want to move to 2019.1 as it has an ARM64 CPU and we added ARM64 support for UWP apps in 2019.1. Also, see this: https://blogs.unity3d.com/2019/02/26/hololens-2-is-coming-what-you-need-to-know/
Thank you very much. Looks promising, now i have to wait for when Microsoft sells the kit here in Spain
Hi I use Unity (2019.4 LTS) for developing an application for Microsoft HoloLens 2 as the target platform. To do so, I added MRTK (Version v2.5) to my project to use some of the libraries. I regularly get errors in the console that look like this: [XRInputSubsystem] A device disconnection with the id 2000000037 has been reported but no device with that id was connected. It seems to happen somewhat randomly. At first, I thought it was disconnecting or something, but then I realized it was just pausing Unity, and I can click 'play' several times to bypass them. This workaround is annoying and slows me down though. Does anyone have an idea for solving this issue?
@rostamisajad19 When you hit play, I assume you are using a remoting connection to your device? If so, there is a known issue with the Microsoft remoting where we don't get paired or complete connect/disconnect messages for some devices. What you are seeing is remoting telling us to disconnect a device it either a) never told us to connect or b) already told us to disconnect earlier. You can ignore these warnings