Please read the Scene Understanding documentation for more information. Users can incorporate the scene understanding capabilities of HoloLens 2 as a spatial awareness observer in MRTK based projects. Scene Understanding now available in MRTK as an experimental spatial awareness observerĮxperimental support of Scene Understanding is introduced in MRTK 2.6. See our updated Input Simulation Service documentation. To teleport with input simulation, please To teleport withĪrticulated hands, make a gesture with your palm facing up with the index and thumb sticking outwards, completing the teleport by curling the index finger. To teleport with a controller on MR devices with default configurations, use the thumbstick. Users can now use the teleport gesture to move around their play space across all platforms. Teleportation with the teleport gesture now supported on all platforms For more information see State Visualizer Documentation This component creates Animation Clips, sets keyframes and generates an Animator State Machine. The State Visualizer is an animation component that depends on Interactive Element. For more information see Interactive Element Documentation. It contains state management methods, event management and the state setting logic for Core Interaction States. Interactive Element is a simplified centralized entry point to the MRTK input system. Experimental Interactive Element + State Visualizer HP Motion Controllers now supported with MRTKĬontrollers for the HP Reverb G2 now work natively with MRTK. Swap multiple assets in a Unity scene with the new Asset Swap utility. OpenXR in Unity is only supported on Unity 2020.2 and higher.Ĭurrently, it also only supports 圆4 and ARM64 builds. See the MRTK/XRSDK getting started page, Unity's forum post, or Microsoft's documentation for more information. Initial support for Unity's OpenXR preview package and Microsoft's Mixed Reality OpenXR package has been added. Updates the dialog example scene to correctly describe the current dialog scenarios. If you did not remove those samples and do see conflicts related to those in the console, please remove both samples (or the Assets/Samples/Mixed Reality Toolkit Examples folder) and then try importing again. Before updating to 2.6.1 you should delete the imported scene understanding and spatial awareness samples if they are present in your project to avoid possible conflicts. Also updates the sample to no longer have a dependency on the spatial awareness sample scene being imported. Updates the scene understanding sample scene to correctly reflect the shipped state of the Unity plugin. Fixes Leap Motion ObjectManipulator not rotatingįixes a regression where a Leap Motion hand's rotation was not taken into account by the ObjectManipulator script. What's new in 2.6.1 Fixes OpenXR not running on HoloLens 2 / UWPįixes a regression that prevented MRTK's OpenXR support from running on UWP. What's new in 2.6.2 Corrects parenting of the spatial meshįixes the issue where spatial meshes were not being properly located after the Mixed Reality Playspace object was moved (ex: via a teleport). Please import the .tools package to apply a workaround.
Microsoft toolkit 2.6 6 download update#
If you are unable to update Visual Studio, This issue is fixed by updating Visual Studio 2019 to version 16.8 or later. There is a known compiler issue that impacts applications built for Microsoft HoloLens 2 usingĪRM64.