Tutorial code does not work with the latest stable HoloToolkit

[logicologist]

Hi folks! These tutorials have fallen substantially behind the latest release of HoloToolkit, even without accounting for the MRTK v2 beta or the HoloLens 2. (I’m looking in particular at Holograms 240.) The current notice prefacing the tutorials is as follows:

“The Mixed Reality Academy tutorials were designed with HoloLens (1st gen) and Mixed Reality Immersive Headsets in mind. As such, we feel it is important to leave these tutorials in place for developers who are still looking for guidance in developing for those devices. These tutorials will not be updated with the latest toolsets or interactions being used for HoloLens 2. They will be maintained to continue working on the supported devices. There will be a new series of tutorials that will be posted in the future that will demonstrate how to develop for HoloLens 2. This notice will be updated with a link to those tutorials when they are posted.”

Although the code does work on HoloLens 1, the above notice is misleading: HoloToolkit 2017.4 does not work with these tutorials out of the box, even though it’s the current stable release for HoloLens 1 development. A few examples of how much has changed:

• The gesture input workflow has changed dramatically since 2017.2 — GestureManager is now obsolete, and InputManager with the IInputClickHandler interface has replaced it. (The same goes for other input modalities.)

• The hologram sharing scripts and prefabs have changed — e.g., AutoJoinSession isn’t part of the standard Sharing.prefab anymore. I’m still in the process of figuring out how to get the 2017.4 version working.

• Even some basics like the Billboard.cs script semantics have changed — replacing the current version with the new version makes billboarded objects face constantly away from instead of toward the user.

Could the tutorials (especially 240) please be updated to 2017.4, for those of us looking to use the tutorial code as a general foundation for understanding and as a starting point for our own apps? Or, alternatively, could the aforementioned notice be updated to warn developers about the updates that have been made between 2017.2 and 2017.4? Thanks!