| title | description | author | ms.author | ms.date | ms.topic | ms.localizationpriority | keywords |
|---|---|---|---|---|---|---|---|
Getting started with MRTK version 2 |
For new developers who are interested in leveraging MRTK |
cre8ivepark |
dongpark |
05/15/2019 |
article |
high |
Windows Mixed Reality, test, Mixed Reality Toolkit, MRTK version 2, MRTK, tools, SDK, HoloLens, HoloLens 2, mixed reality headset, windows mixed reality headset, virtual reality headset, cross-platform |
The MRTK is an amazing open source toolkit that has been around since the HoloLens was first released, and would not be where it is today without the hard work of our developer community who have contributed to it. Over the past 3 years, we have listened to the feedback of our developer community, and built MRTK v2 to take the biggest concerns into account.
MRTK for Unity is an open-source, cross-platform development kit for mixed reality applications. MRTK provides a cross-platform input system, foundational components, and common building blocks for spatial interactions. MRTK version 2 is intended to accelerate the development of applications targeting Microsoft HoloLens, Windows Mixed Reality immersive (VR) headsets and OpenVR platform. The project is aimed at reducing barriers to entry, creating mixed reality applications, and contributing back to the community as we all grow.
[!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4IkCG]
See the MRTK's documentation on GitHub to explore more. To get started, follow the steps on the Installation guide page.
We want to stress our commitment to these platform tools. In fact, we leveraged MRTK version 2 to develop our inbox experiences, such as the out-of-box setup experience (OOBE) and our Mixed Reality Tips application. You can also expect to see new HoloLens 2 capabilities first exposed through MRTK because we believe it’s the best way to develop on our platform.
We have built it in a modular way, so there's no need to take every bit of the toolkit into your project. There are actually a few benefits to this. It keeps your project size smaller, and makes it easier to manage. Additionally, because it’s built with scriptable objects and is interface-driven, it’s also possible for you to replace the components that are included with your own, to support other services, systems, and platforms.
Speaking of other platforms, it has cross-platform support. And while this doesn’t mean every single platform is supported out of the box, we have made sure none of the toolkit code will break when you switch your build target to other platforms. The robustness and extensibility with the modular design sets you up on a good path to be able to support multiple platforms, such as ARCore, ARKit, and OpenVR.
Working with mobile platforms, we constructed it with performance in mind. This is super important, and we wanted to ensure that the tools are not going to work against you.