If user's previous Experience Scale settings do not match the new Experience Settings Profile, they will be prompted to correct it in the inspector. Users can now configure Experience Settings, which will allow MRTK to display Mixed Reality Scene Content appropriately based on the targeted experience. Users can toggle Show null data providers in the profile inspector under Edit -> Project Settings -> Mixed Reality Toolkit to debug unexpected behaviors with missing data providers.Īdded Experience Settings and an associated Mixed Reality Scene Content behavior To accommodate this, null data providers will now no longer be loaded and displayed in the profile inspector. To accommodate this, Legacy XR and XR SDK Data Providers are now organized under different tabs within the profile view, helping users determine whether they have the correct profile for their targeted XR pipeline. Legacy XR and XR SDK data providers can now be used within the same profileĭata providers will now also only be loaded when the appropriate pipeline is selected, allowing both Legacy XR and XR SDK data providers to co-exist within the same profile. Btw, we’ve restructured our full release notes with more notable fixes and known issues.Support for HoloLens 2 articulated hand mesh on OpenXR.Support for WinMR gestures (select, hold, manipulation, navigation) on OpenXR.Support for system-provided motion controller models on OpenXR.This makes it easier to activate buttons with eyes. The eye Dwell feature graduated from experimental.You can now use the same profiles for both LegacyXR and XR SDK.A redesigned Configurator now makes it easier to create a new project in Unity.Like what you see? Download MRTK today from the Mixed Reality Feature Tool or from Github.

In addition, we’ve packed in a bunch of new features and bug fixes to improve the developer experience for Mixed Reality Devs. This release brings official support for OpenXR as we move the Mixed Reality Toolkit to Unity 2020.3 LTS. On May 27 th, 2021 we released MRTK 2.7, so you know we had to be up to something special.

Microsoft auto update 4.6.0