Hello everyone.

We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.

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.

The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.

On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.

So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.

HolotoolKit MR branch not compatible with unity 2017 beta ?

I just tried to build the MR branch of the holotoolkit using unity 2017 beta 2(https://github.com/Microsoft/HoloToolkit-Unity/tree/RS2_WindowsMixedReality) and got build errors.
I guess the code base is not compatible with unity 2017 beta ? Can someone confirm ? I suppose it will be supported in the near future?
Thanks

Best Answer

Answers

  • FranklinChenFranklinChen admin
    edited July 2017

    I guess the code base is not compatible with unity 2017 beta ?

    Some Unity APIs have been changed and have Unity project script upgrading issues.

    I opened this scene: Assets\HoloToolkit-Examples\ColorPicker\ColorPickerExample

    1. Open File->Build Settings->Choose "Universal Windows Platform"->Click "Switch Platform"->Close Window->Click Play button. We will see one compile error.
      The solution is to comment this namespace(UnityEngine.VR.WSA) in Assets\HoloToolkit-Examples\SpatialUnderstanding\SpatialUnderstanding-FeatureOverview\Scripts\SpaceVisualizer.cs

    2. Click Play Button, we will see one API issue in the Assets\HoloToolkit\Utilities\Shaders\FastConfigurable\Editor\CustomMaterialEditor.cs file, if we search on the web, we will see some discussions
      The quick fix is to add the first argument for BeginAnimatedCheck method:
      matEditor.BeginAnimatedCheck(Rect.zero, scaleOffsetProp);

    Now this scene will work well:)

  • edited July 2017

    To further clarify, the UnityEngine.VR.WSA namespace needs to be updated to UnityEngine.XR.WSA

    There is a branch of the HTK that is more inline with the new API's that come in Unity 2017, however it still has these broken namespaces in it.

  • ahalimahalim ✭✭
    Thanks Jesse, I will give it a try.
  • ahalimahalim ✭✭
    Franklin, thanks! Hopefully there aren't too many breaking changes. I wonder if those Hololens academy projects will need to be updated so can be used with unity 2017 (released today!)
  • ahalimahalim ✭✭

    Yeah, the 2017.1 released version has not been updated to use the MixedReality sdk (which works for both immersive and HoloLens). It's still pretty much like 5.6 as far as mr sdk is concerned.

  • @ahalim - They have released 2017.2.0b2, which does use the MixedReality SDK

Sign In or Register to comment.