Hello everyone.

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.
Options

Availability of Unity MRTP build

I understand that this build was made available for early access developers who worked on the acer headset some months ago.

But now that the acer headset is officially on sale for all developers (like me), I wonder why this unity build is not made available for all. This is the only build of unity that works with the mixed reality branch of the holotoolkit (https://github.com/Microsoft/HoloToolkit-Unity/tree/Dev_Unity_2017.2.0).
(Unity 2017.2 is still not ready yet and currently won't build against this branch.)
If you don't have access to this build, you just don't have the means to do development on the immersive headset.

Microsoft, please reply and provide a solution. Thanks.

Best Answer

Answers

  • Options

    The Unity 2017.2.0b is the current build that developers should be using for development at this point. The HTK is in the process of being made compatible with it, however there are some breaking changes between the MRTP builds version of the SDK and the one in 2017.2.0b, so the HoloToolkit team is trying to manage that so as not to upset a bunch of people at once.

    I was able to take the current RS3 branch of the HTK and "fix" the issues with it in about 30 to 40 minutes, so it is doable if you need it right now.

  • Options
    Thanks for the reply Jesse!
    Do you mind sharing the fix that you did here ? I am sure many devs will benefit from it.
  • Options
    Last I did try to build it though I was getting Build errors. Maybe this one will work this time.
  • Options

    There are generally a few things that I had to do to get the project working.

    First and foremost, the namespace needs to be changed from UnityEngine.VR.WSA to UnityEngine.XR.WSA

    Next, some of the handlers for the different inputs have changed signatures, so you have to specify the correct argument type for the method

    Finally, there is a missing stage component, and that whole section of code can be commented out.

    I know this isn't very specific, however it was really just a matter of seeing what items threw errors in unity, and then going into visual studio and correcting them.

  • Options
    Yes I saw all of those and fixed them. I thought I was done then suddenly I got another bunch of 48 Build errors. They are related to something else.
  • Options

    Thank you Microsoft! this is what all of us need now, and you guys delivered!

    Thank you @Jesse_McCulloch , you are the man!

Sign In or Register to comment.