According belowing:
https://developer.microsoft.com/en-us/windows/mixed-reality/Install_the_tools.html#installation_checklist_for_immersive_headsets
If I want to development App for immersive headset, I will need unity private build MRTP.
Where can I get the private build?
2 Likes
Hi NeilLee - sorry for the delayed response.
Microsoft is the key-holder for access to MRTP builds. They recently updated the documentation in the link you posted to say that you should work with a Microsoft account manager to try to get access.
However, support for Windows Mixed Reality has been migrating out of the preview branch used for those builds - you should be able to get betas of 2017.2 when they start coming out so you can work on apps for your immersive headset with Windows Mixed Reality. Be forewarned that the earlier the beta, the more likely you may run into bugs, but we appreciate any help we can get from you with filing bugs you run into!
Does anyone know how to get access to MRTP builds with Microsoft account manager?
Apparently, getting access to the MRTP builds is going to take a while so I was wondering if itâs possible to use 5.6 or 2017.1 beta for Windows Mixed Reality development?
Thanks
Windows Mixed Reality support for VR HMDs is landing in early 2017.2 betas. 5.6 and 2017.1 arenât supported.
1 Like
Hod do you get access?
thanks
Is there an ETA on the 2017.2 beta? Iâm actually able to get Windows Mixed Reality running on 5.6, but, unsurprisingly, itâs very finicky.
@pero58 : Iâm afraid I donât have a good answer for that. All I know is what it says on the website: âyouâll need to acquire a private build of the Mixed Reality Technical Preview (MRTP) by working with your Microsoft account manager.â I donât know what you would need to do if youâre not already in contact with one, or how you would get one. I would suggest poking around the Microsoft forums and seeing if you can find anything there.
@penrose_stanley : Iâm not in the know about the public release of a 2017.2 beta, but I think it should be pretty soon.
Sorry I couldnât be of more help to either of you on this front.
Heyo! I was following this thread all day yesterday, then lo and behold look what just appeared on Unity Editor Beta Releases The first 2017.2 beta release! Letâs get cracking.
Aaaannnd so much for that. Up and running in Unity using these settings (Unity development for HoloLens - Mixed Reality | Microsoft Learn) and when I press Play in Unity, my headset goes black. My Unity Editor windows show that tracking is working, but I canât see anything in the headset.
Have fun! I just wanted to make sure I pointed out a known issue posted in the release notes relevant to this platform:
- XR: New API surface for recent UnityEngine.VR.WSA.Input changes has forthcoming breaking changes to land in another beta soon.
QA is currently hammering on said breaking changes, and we hope to have them out to you soon.
@ibrews : That beta should definitely have working Play mode in the editor for supported Windows Mixed Reality HMDs. Would you mind filing a bug on that for me? Itâd be useful to get machine specs out of, if nothing else.
Sure @unity_andrewc I was soooo close to getting started too!
@unity_andrewc bug report submitted from alex.coulombe@gmail.com! hope itâs helpful.
@ibrews : It looks like you didnât switch to UWP - the bug report says you have support for Windows standalone enabled (weird and confusing that thereâs this difference, I know).
If you bring up the Build Settings window (Ctrl+Shift+B, or under the File menu), you need to select the âWindows Storeâ platform and click âSwitch Platformâ. Then, click âPlayer SettingsâŚâ and make sure that support is enabled for Windows Mixed Reality.
Also, your bug report says this is a crash? The editor definitely shouldnât be crashing just because youâre trying to use a headset that doesnât match what platform you enabled XR for. Please let me know whether itâs a crash or if it just renders black - either way, it sounds like something we should fix, or at least emit a warning for so you have some clue as to whatâs going on.
Let me know how it goes!
@unity_andrewc very strange! I donât believe much of that is accurate. In the new Unity beta, thereâs a platform called âUniversal Windows Platformâ and there is no longer a âWindows Storeâ platform. I definitely had and have UWP enabled and Windows Mixed Reality set up in Player Settings/ XR Settings.
And no the Editor isnât crashing, the Acer headset is. Everything in the Editor behaves as it would if I had a Rift or Vive plugged in. But in the headset it fades to black, blinks, then fades to blue, then goes through the headset setup process again, then re-enters the âhomeâ mode. Seems like a crash to me.
@ibrews : My bad, I was just working in some 5.6 code and forgot that the âWindows Storeâ was changed to âUniversal Windows Platformâ at some point.
But youâre sure that in Player Settings, itâs Windows Mixed Reality thatâs enabled? Either way, itâs rather odd that the bug report says you have Windows Standalone enabled instead of UWPâŚ
Yeah Iâm certain:
Very strange about the bug report. Any chance thereâs a bug with the bug reporting 
?
It seems there has to be a bug with something there, I just have no idea whether it would be the bug reporter or the settings themselves that are being reported.
I do have one more thing to ask you to test out, though: can you disable the âVuforia ARâ toggle and try again? I havenât messed around with that option recently, and there might be a bug with trying to use that with Windows Mixed Reality on desktop. (You might need to restart your machine first, QA has been telling me that they occasionally have to either do that or kill DWM when the Acer headset - or the code supporting it - gets messed up.)
@unity_andrewc tried turning off Vuforia AR and killing DWM. Same results. Hm! Should I reach out to Microsoft or Acer as well?