MRTK 2.6 and the New MRTK Docs Experience are available now!

koujaku I did find a workaround and I had posted an issue in https://github.com/MicrosoftDocs/mixed-reality/issues/280 on the topic.  The https://docs.microsoft.com/en-us/windows/mixed-reality/develop/unity/choosing-unity-version kind of follows what you suggest stick with a specific version. The very first sentence of the topic says it all. However, the MRTK versions are rolling out with features in HoloLens we need. A lot of these allow us to use our Azure tools and connect to our Azure resources. This necessarily forces us to "upgrade" to a newer version of MRTK. That is when the trouble starts.  No one it seems is looking at the fallout from configuration modifications in Unity of the MRTK that cause something else to break. I know Unity is on its own trajectory but that does not mean that MRTK has to also be free-wheeling. Seems to me the QA testing is completely in the hands of the community of developers.  I did open the scripts in the project looking for comments to help troubleshoot - nada.