Also I wanted to see if there was any change if I tried to run the built version of the app, but the built result doesn’t seem to have an executable. How do I run it?
No, I don’t think reaching out directly to Microsoft or Acer would have much success. I just tried opening your project again, and each time I open it up from a fresh download of your repro project, it thinks it was set to Windows Standalone instead of UWP.
I’ve been trying to play around with fresh projects on the same install of Unity that you downloaded, and I’m getting some strange results that I think will require some further investigation on our side. Rendering to the headset in play mode (which I wrote, and I know worked a week or so before b2 was cut) and ability to actually generate a solution are inconsistent between my machines: one of them is on the Creators Update of Windows 10, and the other is on the Insider preview builds. I was hoping that maybe this was just another bug with spaces appearing in the project name or something again, but no such luck - recreating the project without spaces in the project name doesn’t seem to do anything.
But I’m unable to recreate this issue I’m seeing with your project thinking (on my end, at least) that it’s targeting Windows Standalone instead of UWP, as this would at least explain both why it fails miserably at rendering in-editor to the headset on every attempt and why you can’t generate a build that has any hope of working. The only thing I can think of suggesting shy of taking a gamble and updating your OS to Insider Preview would be to try recreating your project. Before you do anything else, go to the build settings in your fresh project, switch to UWP, enable XR, remove Vuforia from the list, and ensure the toggle for it is disabled. Then, close Unity, reopen the project, and double-check that the build settings are still the same. From there, just try playing in editor again and see what happens, assuming that the project settings are preserved for targeting UWP and Windows Mixed Reality.
Also, is the Mixed Reality Portal running and rendering to the headset before you start trying to play in-editor?
Sorry for this blocking issue. I appreciate you working through it with me.
thanks for continuing the conversation @unity_andrewc
- new project, followed your steps in order, and it’s working! No headset crash-- fades to black then I see inside Unity. Weird… went back to my previous project and that one still isn’t working despite settings being identical (as far as I can tell).
- I’m currently using Windows 10 Pro Insider Preview Build 16232.rs_prerelease.170624-1334
- yes everything is running in the headset with the mixed reality portal before I press play
Oh man so weird. Okay now I went back to the new project I made and it’s crashing again.
Just tried to create new project from scratch, same steps as before, and this time the headset fades to black and doesn’t crash, but then it stays black and I can’t even get back to the home screen, even if I exit Unity entirely.
We sometimes have to restart our machines (or supposedly just kill Mixed Reality Portal and DWM as a shortcut) to get the headsets to respond and render. This stuff does rely on early flights of Windows updates, so it’s bound to be unstable here and there, unfortunately. We’ll definitely investigate on our end, but for now, and based on the information you’ve shared, my only suggestion is to restart your machine, make another fresh project and make sure the HMD works in-editor again, and just try to keep using that project - if it stops working again after this, reboot your machine again, and hopefully the same project will continue to work.
gotcha! thanks very much
Just an update on all this-- it could be the problem is my CPU doesn’t read AVX instructions. Take a look at the thread over here:
Yep! Using the beta on a new computer now and it works very smoothly.
Happy to hear!
I’m new to Unity IDE and very impressed so far by completing some tutorials.
The author of this article mention permission from Microsoft Account Manager? I installed Unity 2017.1.0f3 (64-bit). I have the Acer Headset and aim to develop mixed reality apps. Am I good to go with the Unity version I have installed?
The mention of permission from a Microsoft Account Manager is for the technical preview where we were initially standing up Windows Mixed Reality’s VR HMDs but weren’t able to get the feature to mainline on that version - what you want is 2017.2, as no non-preview version of Unity has any support for those HMDs. It’s currently in beta.
1 Like
I’m having some trouble getting Unity 2017.2 to work with my Acer headset. I have installed beta 5, and followed all of the steps of the “install the tools” page on Microsoft. The computer is updated to the latest “fast” insider preview and I have the insider SDK installed as well. The headset runs fine in the MR portal app (the cliff house) but when I start Unity with the headset plugged in the editor is blank (all white) I can select the menus but all of the windows (hierarchy, project, game, scene, etc…) are not visible. If I select Play from the menu the headset just restarts the MR portal app and doesn’t render the unity project.
I have unity setup for the windows universal platform and virtual reality checked (with the mixed reality SDK selected in player settings).
If I try to run Unity without the headset plugged in I get all of the windows in the editor and can use Unity just fine by itself. As soon as I plug in the headset all of the UI in the editor freezes but I can still quit the editor.
Do you know what build of the RS3 OS you are using?
What is RS3 OS?
Sorry RS3 == Red Stone 3, it refers to to the release cycle of the Windows 10 OS. I think in order to get RS3 you need to be on Windows Insider, that is the current supported Mixed Reality OS. If you are on RS3 you should see a small OS number in the bottom right of your desktop screen.
I see, and how does one get this version? I signed up for the insider program and set my update settings to Fast (Active Development of Windows). My current version is 1703 build 15063.502
Did you update to RS2 the creative update, it doesn’t appear your OS is up do date. My build is currently on Version 1703 OS build 16257.1, I would double check your windows insider settings
Ok finally got it working. Getting windows to update to this version was very difficult on our computer. But once we updated by using an ISO download from the windows insider website it updated and now Play mode works in Unity 2017.2 
Thanks for your help pointing out we needed a different version. We now have build 16257 as well. Is single pass rendering supported yet for Mixed Reality?
Single Pass is supported for Windows MR