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.
Holograms 100 tutorial errors w/ Emulator
Hello. I'm currently trying to get Hololens development working with a couple Coworkers, and we're having some difficulties.
We've been following this tutorial to set our machines up with the Emulator, Unity, etc, and following this tutorial to build the first app.
However, we run into two separate issues depending on which version of Unity we use. The Emulator is version 10.014393.1358.
If I create the project in Unity 5.6.0f3 (the version that was installed when I selected " Game Development with Unity" from the Visual Studio 2017 installer), I get the following error: . I've had no luck finding a fix for this error.
However, if I create the project in Unity 2017.2.0b7, following the Holograms 100 tutorial again, I use the Release version, target x86, and select HoloLens Emulator 10.0.14393.1358, Visual Studio will build the app, open the Emulator, but then nothing happens. I can mess around with the emulator itself, but if I try to access the MixedRealityIntroduction app, nothing happens. I just get blank screen.
While writing up this question, I did however try building to something different with interesting results. On the 2017.2.0b7 version, if instead of targeting the emulator, I target 'Local Machine', I get the view that I expected to get, but in it's own application.
Let me know if there's any more information I need to share.
My boss was trying to get it working on his machines, but he had the exact same problems for both versions as described above. He even tried following a different tutorial on Pluralsight, but to no avail. That makes consistent errors on four different machines using one or both versions of Unity.
Best Answer
-
Optionsjames_ashley ✭✭✭✭
dmidcap,
Which version of Visual Studio are you using? If it is Visual Studio 2017 ver 15.3.3, you may need to get Unity 2017.1.05p to run it.
Have you tried using VS 2015 to build instead? build against SDK 14393 instead of "Latest installed" also.
http://www.imaginativeuniversal.com/blog/2017/09/05/hololens-and-mr-device-dev-advisory/
James Ashley
VS 2017 v5.3.3, Unity 2017.3.0f3, MRTK 2017.1.2, W10 17063
Microsoft MVP, Freelance HoloLens/MR Developer
www.imaginativeuniversal.com1
Answers
dmidcap,
Which version of Visual Studio are you using? If it is Visual Studio 2017 ver 15.3.3, you may need to get Unity 2017.1.05p to run it.
Have you tried using VS 2015 to build instead? build against SDK 14393 instead of "Latest installed" also.
http://www.imaginativeuniversal.com/blog/2017/09/05/hololens-and-mr-device-dev-advisory/
James Ashley
VS 2017 v5.3.3, Unity 2017.3.0f3, MRTK 2017.1.2, W10 17063
Microsoft MVP, Freelance HoloLens/MR Developer
www.imaginativeuniversal.com
You need to edit the "project.lock.json" file and replace each occurrence of "UAP,Version=v10.0.10240" with "UAP,Version=v10.0". You can find this project.lock.json file when you click on 'Show all files' in VS 2017.
Note that each time you rebuild the VS project the "project.lock.json" file will be recreated and you will need to redo the edit. See this link for more information.
https://forum.unity3d.com/threads/net-scripting-backend-and-visual-studio-2017-3-incompatibility.487833/
So one of my other coworkers found a combination that worked. Using Visual Studio 2017 ver 15.3.0 (according to the About Visual Studio menu), and Unity 20171.1f1, I was able to get the tutorial app running on the emulator!
@Dmidcap , Excellent! If VS makes you to move to 15.3.3, that could force you to get a later release of Unity 2017. Also, at some point, you'll want to do remote debugging -- hopefully the final release of 2017.2 will work that out.
James Ashley
VS 2017 v5.3.3, Unity 2017.3.0f3, MRTK 2017.1.2, W10 17063
Microsoft MVP, Freelance HoloLens/MR Developer
www.imaginativeuniversal.com
You need to edit the "project.lock.json" file and replace each occurrence of "UAP,Version=v10.0.10240" with "UAP,Version=v10.0" . Note that each time you rebuild the VS project the "project.lock.json" file will be recreated and you will need to redo the edit. See this link for more information.
https://forum.unity3d.com/threads/net-scripting-backend-and-visual-studio-2017-3-incompatibility.487833/