MRTK v3.0.0 GA

[AMollis]

The Mixed Reality Toolkit Organization is happy to announce the general availability of MRTK3. This has been a huge effort by many, and it is inspiring to see this milestone come to completion. Thank you to the founding MRTK members and the new team for all your amazing work. Also, thank you to the community for your help, we couldn't have reached this moment without you.

We recommend that applications use Microsoft's Mixed Reality Feature Tool to obtain the latest version of MRTK3. Follow Microsoft's instructions for setting up a new MRTK3 project, these steps include instructions for using the Mixed Reality Feature Tool.

Please note, this will be the final "multi-package" release for MRTK. Future releases will be done on a per package basis.

As always, we welcome your feedback and look forward to working together to make MRTK even better!

Changelog for MRTK v3.0.0

[v3.0.0] - 2023-9-6 - 48686f9

The format is based on Keep a Changelog. The content is mirrored at the changelog page of the Microsoft docs website, for now.

Fixed

• Fixed scripts for generating release packages. (37, 427, 434, 445)
• Fixed ExperimentalDrawer so it compiles in Unity Editor 2022.3.2 and above. (40)
• Fixed project template for new project. (446)
• MRTK3 now compiles in Unity 2022 without automated code changes. (11668)

---

This discussion was created from the release MRTK v3.0.0 GA.

[LocalJoost]

Hi, are you aware the upgrade feature of the MRTK feature tool is not longer working properly with this release? If I select an existing project, now on pre-17, it doesn't register the pre-17 packages being installed (didn't even have time to upgrade to pre-18)

If I install 3.0.0GA the new packages are added, but the old ones not deleted (like what happened before), so I end up with all kinds of duplicate definition errors. You might want to address that, or at least mention that in documentation.

Also, changing all the name spaces from Microsoft.MixedReality.Blah to MixedReality.Blah will make a lot of people unhappy. I understand why, but it's a bit late in the release cycle. I seem to get away with a search & replace.

[shaynie]

@LocalJoost , In the feature tool settings, there is a setting to show deprecated packages. If you select that, you will see new com.microsoft.mrtk.* packages that bring in the new org.mixedrealitytoolkit.* packages. That is what we decided to provide for an upgrade path. Please let me know if it works for you.

Thanks,
Scott

[AMollis]

@LocalJoost , the pre.18 packages will help with the upgrade path. Hopefully people caught this in the previous release notes, https://github.com/orgs/MixedRealityToolkit/discussions/426

To avoid new user confusion, we decided it best to hide the old packages under the deprecation flag (as mentioned by @shaynie). Unfortunately, the MRFT does not show deprecated packages that are already installed, if the deprecation flag is not set.

[LocalJoost]

Thank you for this clarifications. Since the previous .18 release was so short ago, I think people might have missed it - I did. I am not sure if showing the deprecated packages will help, but anyway, now at least people can see directly under the announcement what they might have missed and what the consequences and necessary actions following of upgrading are. In the mean time, THANKS! We were really waiting for this GA!

[Suman-298]

Will Mrtk 3 work as cross platform for Oculus quest 2, windows, mobile and HoloLens 2.

[LocalJoost]

@Suman-298 as you might have seen on my blog previous versions worked on all of them, and Magic Leap 2 as well. This stuff is pretty cross platform

[LocalJoost]

@AMollis you are you aware of the fact that after upgrading successfully to MRTK3 GA, which I did, the MRKT Feature Tool does no longer recognize the installed packages. So if you want to install additional packages, you will need to remember which one you already installed, or look in the manifest file yourself. I am using FT 1.0.2209.0, downloaded Sept 8. (ie 2 days ago)