-->

A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate in the Unity community. Log in Create a Unity ID We use cookies to ensure that we give you the best experience on our website. Unity Intercom is a Full Duplex intercom system that connects over WiFi or Cellular data. Unity Intercom has two parts, the Unity Client apps which run on mobile devices and the Unity Server software running on a Mac. Unity Intercom supports third-party comm integration and program audio feeds. You asked for it. Note that it's not COMPLETED & UNOPTIMIZED.Download. Github: Demo (Windows x64). Install Unity support for Visual Studio. Visual Studio Tools for Unity is a free extension that provides support for writing and debugging C# and more. Visit the Tools for Unity overview for a complete list of what the extensions includes.

Get the tools you need to build applications for Microsoft HoloLens and Windows Mixed Reality immersive (VR) headsets. There is no separate SDK for Windows Mixed Reality development; you'll use Visual Studio with the Windows 10 SDK.

Don't have a mixed reality device? You can install the HoloLens emulator to test some functionality of mixed reality apps without a HoloLens. You can also use the Windows Mixed Reality simulator to test your mixed reality apps for immersive headsets.

We recommend installing either the Unity or Unreal game engine as the easiest way to get started creating mixed reality apps. However, you can also build against DirectX if you'd like to use a custom engine.

If you're using Unity, you can use Mixed Reality Toolkit for Unity's input simulation to test various types of input interactions such as hand-tracking and eye-tracking input. For Unreal projects, use the UX Tools plugin to test common input interactions and user experience features.

Tip

Bookmark this page and check it regularly to keep up-to-date on the most recent version of each tool recommended for mixed reality development.

Installation checklist

Install your engine of choice

Now that you have your Windows 10, Visual Studio, and Windows 10 SDK ready to go, let's install and setup the engine of your choice.

If you still need to choose an engine, see the Introduction to Mixed Reality development.

1. Download the recommended Unity version

The current recommended version for Mixed Reality development is Unity 2019.4 LTS (Long Term Support). The best way to install and manage Unity is through the Unity Hub.

Note

If you’re using Unity 2020 LTS, Mixed Reality support is available for HoloLens 2 development. However, there are currently some known issues. This will become the recommended Unity version later this year.

See Choosing a Unity version and XR plugin to learn what Mixed Reality support is available in different Unity engine and XR plugin versions.

When installing Unity, please make sure to check following components under 'Platforms'.

• Universal Windows Platform Build Support
• Windows Build Support (IL2CPP)

If you installed Unity without these options, you can add them through 'Add Modules' menu in Unity Hub.

2. Install the Mixed Reality Feature Tool

The Mixed Reality Feature Tool is a new way for developers to discover and add Mixed Reality feature packages into Unity projects.

You can search packages by name or category, see their dependencies, and even view proposed changes to your projects manifest file before importing. Once you've validated the packages you want, the Mixed Reality Feature tool will download them into the project of your choice.

Importing the Mixed Reality Toolkit

Mixed Reality Toolkit (MRTK) is an open-source, cross-platform development kit for mixed reality applications.

• Install the Mixed Reality Toolkit package by following the installation and usage instructions and selecting the Mixed Reality Toolkit Foundation package.

We recommend completing the getting started section in our curated HoloLens or VR development journeys. If you're already following the Unity development for HoloLens journey, finish up the rest of the setup steps listed below and continue on to the HoloLens 2 Getting Started tutorials.

Important

Note that installation instructions are targeted for the latest stable combination of MRTK and Unity releases, which are MRTK 2.6.1 and Unity 2019.4 LTS.

Note

If you don't want to use MRTK for Unity, you'll need to script all interactions and behaviors yourself.

Other tools [optional]

• Mixed Reality Companion Kit (GitHub) - code bits and components that might not run directly on HoloLens or immersive (VR) headsets, but instead pair with them to build experiences targeting Windows Mixed Reality.
• Mixed Reality Toolkit - Common (GitHub) - a collection of shared scripts and components.

3. Set up your PC for Mixed Reality development

The Windows 10 SDK works best on the Windows 10 operating system. This SDK is also supported on Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows Server 2008 R2. Note that not all tools are supported on older operating systems.

Unity Oscillate

Note

You can develop and deploy your apps for HoloLens, VR immersive headsets, or both. Make sure you fulfill the requirements below depending on your needs.

For HoloLens development

When setting up your development PC for HoloLens development, please make sure it meets the system requirements for both Unity and Visual Studio. If you want to run your app on a HoloLens device, you need to follow the Windows Device Portal setup instructions. If you plan on using the HoloLens emulator, you'll want to make sure your PC meets the HoloLens emulator system requirements as well.

To get started with the HoloLens emulator, see Using the HoloLens emulator.

If you plan to develop for both HoloLens and Windows Mixed Reality immersive (VR) headsets, use the system recommendations and requirements in the section below.

HoloLens troubleshooting

Setting Developer Mode is grayed out

If you're running into issues enabling Developer Mode on your device you might not be the device owner. In multi-user mode, the person who uses the device first is the device owner - any subsequent users won't have the required permissions to enable Developer Mode or other configuration changes. However, there is an exception where the first user may not be the device owner in an Autopilot environment, which is detailed in the HoloLens security documentation.

Possible solutions include:

• Having the device owner turn Developer Mode on before passing the device to other users or developers
• Suggesting that your IT/MDM Admin enables CSP Policy ApplicationManagement/AllowDeveloperUnlock for the specific device or a developer device group.
  • This policy can be set by Provisioning Packages or via MDM for HoloLens devices
• Using the Advanced Recovery Companion (ARC)

Note

You can learn more about device management in the HoloLens device management overview.

I can't deploy over USB

If you're not able to deploy an application directly over USB, make sure you've met all the installation requirements listed above and follow our step-by-step tutorial.

Immersive (VR) headset requirements

Note

The following guidelines are the current minimum and recommended specs for your immersive (VR) headset development PC, and are updated regularly.

Warning

Do not confuse this with the minimum PC hardware compatibility guidelines, which outlines the consumer PC specs to which you should target your immersive (VR) headset app or game.

If your immersive headset development PC does not have full-sized HDMI and/or USB 3.0 ports, you'll need adapters to connect your headset.

There are currently known issues with some hardware configurations, particularly notebooks that have hybrid graphics.

If you're new to MRTK development with Unity, we recommend following our curated Unity development journey:

Next Development Checkpoint

If you're following the Unity for HoloLens development checkpoint journey we've laid out, your next task is to work through our HoloLens 2 tutorial series.

If you're following the Unity for VR journey, your next task is to setup your project.

You can always go back to the Unity development checkpoints for HoloLens and VR at any time.

1. Download the latest version

We recommend installing Unreal Engine version 4.25 or later to take full advantage of built-in HoloLens support.

Go to the Library tab in the Epic Games Launcher, select the dropdown arrow next to Launch and click Options. Under Target Platforms, select HoloLens 2 and click Apply.

2. Import Mixed Reality Toolkit (MRTK)

Mixed Reality Toolkit (MRTK) 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. The toolkit is intended to accelerate the development of applications targeting Microsoft HoloLens, Windows Mixed Reality immersive (VR) headsets, and the OpenVR platform.

For installation, we recommend completing the Getting Started section of our curated Unreal development journey. If you're already following the Unreal development journey, finish up the rest of the setup steps listed below and continue on to the HoloLens 2 Getting Started tutorials.

Note

If you don't want to use MRTK for Unreal, you'll need to script all interactions and behaviors yourself.

Other tools [optional]

• Mixed Reality Companion Kit (GitHub) - code bits and components that might not run directly on HoloLens or immersive (VR) headsets, but instead pair with them to build experiences targeting Windows Mixed Reality.
• Mixed Reality Toolkit - Co mmon (GitHub) - a collection of shared scripts and components.

3. Set up your PC for mixed reality development

The Windows 10 SDK works best on the Windows 10 operating system. This SDK is also supported on Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows Server 2008 R2. Note that not all tools are supported on older operating systems.

Note

You can develop and deploy your apps for HoloLens, VR immersive headsets, or both. Make sure you fulfill the requirements below depending on your needs.

For HoloLens development

When setting up your development PC for HoloLens development, please make sure you meet the system requirements for Unreal and and Visual Studio. If you want to run your app on a HoloLens device, you need to follow the Windows Device Portal setup instructions. If you plan on using the HoloLens emulator, you'll want to make sure your PC meets the HoloLens emulator system requirements as well.

If you plan to develop for both HoloLens and Windows Mixed Reality immersive (VR) headsets, use the system recommendations and requirements in the section below.

HoloLens troubleshooting

Setting Developer Mode is grayed out

If you're running into issues enabling Developer Mode on your device you might not be the device owner. In multi-user mode, the person who uses the device first is the device owner - any subsequent users won't have the required permissions to enable Developer Mode or other configuration changes. However, there is an exception where the first user may not be the device owner in an Autopilot environment, which is detailed in the HoloLens security documentation.

Possible solutions include:

• Having the device owner turn Developer Mode on before passing the device to other users or developers
• Suggesting that your IT/MDM Admin enables CSP Policy ApplicationManagement/AllowDeveloperUnlock for the specific device or a developer device group.
  • This policy can be set by Provisioning Packages or via MDM for HoloLens devices
• Using the Advanced Recovery Companion (ARC)

Note

You can learn more about device management in the HoloLens device management overview.

I can't deploy over USB

If you're not able to deploy an application directly over USB, make sure you've met all the installation requirements listed above and follow our step-by-step tutorial.

Immersive (VR) headset requirements

Note

The following guidelines are the current minimum and recommended specs for your immersive (VR) headset development PC, and are updated regularly.

Warning

Do not confuse this with the minimum PC hardware compatibility guidelines, which outlines the consumer PC specs to which you should target your immersive (VR) headset app or game.

If your immersive headset development PC does not have full-sized HDMI and/or USB 3.0 ports, you'll need adapters to connect your headset.

There are currently known issues with some hardware configurations, particularly notebooks that have hybrid graphics.

If you're new to MRTK development with Unreal, we recommend following our curated Unreal development journey:

Next Development Checkpoint

If you're following the Unreal development checkpoint journey we've laid out, your next task is to work through our HoloLens 2 tutorial series.

You can always go back to the Unreal development checkpoints at any time.

Native OpenXR development doesn't have an engine for you to download. You can find everything you need to begin development in the Getting started with OpenXR document.

1. Set up your PC for mixed reality development

The Windows 10 SDK works best on the Windows 10 operating system. This SDK is also supported on Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows Server 2008 R2. Note that not all tools are supported on older operating systems.

Glass Os

For HoloLens development

When setting up your development PC for HoloLens development, please make sure you meet the system requirements for Visual Studio. If you want to run your app on a HoloLens device, you need to follow the Windows Device Portal setup instructions. If you plan on using the HoloLens emulator, you'll want to make sure your PC meets the HoloLens emulator system requirements as well.

If you plan to develop for both HoloLens and Windows Mixed Reality immersive (VR) headsets, use the system recommendations and requirements in the section below.

Note

You can develop and deploy your apps for HoloLens, VR immersive headsets, or both. Make sure you fulfill the requirements below depending on your needs.

HoloLens troubleshooting

Unity Osoyoos

Setting Developer Mode is grayed out

If you're running into issues enabling Developer Mode on your device you might not be the device owner. In multi-user mode, the person who uses the device first is the device owner - any subsequent users won't have the required permissions to enable Developer Mode or other configuration changes. However, there is an exception where the first user may not be the device owner in an Autopilot environment, which is detailed in the HoloLens security documentation.

Possible solutions include:

• Having the device owner turn Developer Mode on before passing the device to other users or developers
• Suggesting that your IT/MDM Admin enables CSP Policy ApplicationManagement/AllowDeveloperUnlock for the specific device or a developer device group.
  • This policy can be set by Provisioning Packages or via MDM for HoloLens devices
• Using the Advanced Recovery Companion (ARC)

Note

You can learn more about device management in the HoloLens device management overview.

Immersive (VR) headset requirements

Note

Unity Osu

The following guidelines are the current minimum and recommended specs for your immersive (VR) headset development PC, and are updated regularly.

Warning

Do not confuse this with the minimum PC hardware compatibility guidelines, which outlines the consumer PC specs to which you should target your immersive (VR) headset app or game.

If your immersive headset development PC does not have full-sized HDMI and/or USB 3.0 ports, you'll need adapters to connect your headset.

There are currently known issues with some hardware configurations, particularly notebooks that have hybrid graphics.

If you're new to Native development with MRTK, we recommend following our curated Native development journey:

Next Development Checkpoint

If you're following the Native development checkpoint journey we've laid out, your next task is to configure your development environment for HoloLens 2.

You can always go back to the Native development checkpoints at any time.

You can switch virtual machines that have Windows XP or later guest operating systems to Unity mode to display applications directly on the host system desktop.

In Unity mode, virtual machine applications appear on the host system desktop, you can use the virtual machine Start or Applications menu from the host system, and the virtual machine console view is hidden. Items for open virtual machine applications appear on the host system taskbar in the same way as open host applications.

On host system and virtual machine applications that are displayed in Unity mode, you can use keyboard shortcuts to copy, cut, and paste images, plain text, formatted text, and email attachments between applications. You can also drag and drop and copy and paste files between the host system and the guest operating system.

If you save a file or attempt to open a file from an application in Unity mode, the file system you see is the file system inside the virtual machine. You cannot open a file from the host operating system or save a file to the host operating system.

For some guest operating systems, application windows in Unity mode can appear only on the monitor that is set as the primary display when you have multiple monitors. If the host and guest operating systems are Windows XP or later, the application windows can appear on additional monitors.

Unity mode is not available in full screen mode on Windows.

• Verify that the latest version of VMware Tools is installed in the guest operating system.
• Verify that the guest operating system is Windows XP or later.
• Power on the virtual machine.
• If you are entering Unity mode, open applications in the virtual machine to use in Unity mode.

Procedure

• To enter Unity mode, select the virtual machine and select View > Unity.
  The console view in the Workstation Pro window is hidden, and open applications appear in application windows on the host system desktop. A check mark appears next to Unity in the View menu.
• To navigate between multiple Start or Applications menus when multiple virtual machines are in Unity mode, press the arrow keys, Tab, or Shift+Tab to cycle through the virtual machine menus and press Enter and the spacebar to select a virtual machine.
• To exit Unity mode, select View > Unity and deselect Unity.