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.
spectator view
I'm attempting to get SpectatorView setup. I'm having issues arranging the Unity source code. I've not made any alterations to the source code and I'm getting an aggregate error.
Assets/HoloToolkit/Utilities/Shaders/FastConfigurable/Editor/CustomMaterialEditor.cs(103,24): error CS1501: No over-burden for strategy BeginAnimatedCheck' takes 1' contentions
The line of code being referred to is in the namespace HoloToolkit.Unity in a class named CustomMaterialEditor in a strategy named TextureScaleOffsetVector4Property.
Best Answer
-
Optionssally ✭
This is still valid: I am receiving the same error in Unity 2017.1.1f1 with the latest SpectatorView code from git.
I have resolved this for now by changing the effected line to:
matEditor.BeginAnimatedCheck(new Rect(), scaleOffsetProp);In accordance with the comments found here:
https://github.com/Microsoft/MixedRealityCompanionKit/issues/1715
Answers
@Jackson could you help here? thanks!
This is still valid: I am receiving the same error in Unity 2017.1.1f1 with the latest SpectatorView code from git.
I have resolved this for now by changing the effected line to:
matEditor.BeginAnimatedCheck(new Rect(), scaleOffsetProp);
In accordance with the comments found here:
https://github.com/Microsoft/MixedRealityCompanionKit/issues/171
Thank You @sally .It is resolved