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.
Referencing the HoloToolkit version?
I'd like to make a note about which version of the HoloToolkit that I've used with my project. What's the best way to do that?
I looked into how to make a reference to the Git revision. The SHA and rev-list solutions that give a type of reference to the commit seem clunky.
The toolkit's readme specifies the Unity Editor Project Version with which it is aligned (5.5.0f3), but I anticipate the toolkit may change out-of-step with Unity, so multiple Toolkit versions will be aligned with each version of Unity.
https://github.com/Microsoft/HoloToolkit-Unity/blob/fd2b5d31bbdfa7f43e76e4462663d66089c0b21d/README.md
similarl Unity version specification: https://github.com/Microsoft/HoloToolkit-Unity/blob/63dabf4826332a82ff369569a7f1d7435b9ebb48/ProjectSettings/ProjectVersion.txt
Answers
@EMebane we have releases with version tags for example here.
Master does not get version as there could be several checkins before we mark a release. The ProjectVersion.txt specifies the Unity version Master is compatible with. HTH!
Got it. That's helpful.
Would it be possible to also add the HoloToolkit release version to the ProjectVersion.txt file when making a new release? Here's a scenario: I have a HoloToolkit integrated into an old project and I'd like to be able to identify from the HoloToolkit files themselves which release that particular HoloToolkit is associated with. I'm not sure what the common protocol is when there is an active GitHub project with tagged releases.
Also, should the Unity build number in ProjectVersion.txt be seen as a minimum requirement, or simply the highest version of Unity that release of HoloToolkit has been tested with? e.g., I have a copy of the latest HoloToolkit release (v1.5.8.0) which lists a companion Unity version of 5.6.2f1, but I only have Unity 5.6.1f1. Should I read that as there is something in the HoloToolkit that requires Unity 5.6.2f1 and I must upgrade Unity to use that version of the HoloToolkit, or should I read it as Unity 5.6.2f1 is the highest version of Unity tested against that version of the HoloToolkit so they're compatible, but the newer Unity is not a requirement.
I just compiled a project with HoloToolkit release (v1.5.8.0) and Unity 5.6.1f1 (older than the Unity version specified in the HoloToolkit release) and it seems to work fine.