Example projects that use XR Interaction Toolkit to demonstrate its functionality with sample assets and behaviors.
The intention of this repository is to provide a means for getting started with the features in the XR Interaction Toolkit package.
The XR Interaction Toolkit is available as a preview package, so it is still in the process of becoming stable enough to release. The features and documentation in this package might change before it is ready for release.
Additionally, the behaviors included in this example may change in a way that does not maintain backwards compatibility.
These projects are compatible with the following versions of the Unity Editor:
- 2019.4 and later
These example projects rely on additional Unity packages that are 2019.4 verified:
The XR Interaction Toolkit and Input forum is the best place to open discussions and ask questions. Please use the public roadmap to submit feature requests. If you encounter a bug, please use the Unity Bug Reporter in the Unity Editor, accessible via Help > Report a Bug. Include “XR Interaction Toolkit” in the title to help our team triage things appropriately!
We are not accepting pull requests at this time.
- Clone or download this repository to a workspace on your drive
- Click the ⤓ Code button on this page to get the URL to clone with Git or click Download ZIP to get a copy of this repository that you can extract
- Open a project in Unity
- Download, install, and run Unity Hub
- In the Installs tab, select Locate or Add to find or install Unity 2019.4 LTS or later
- In the Projects tab, click Add
- Browse to the AR or VR folder within your downloaded copy of this repository and click Select Folder
- Click the project which should now be added to the list to open the project
- For the VR project, open the Scene at
Assets\Scenes\WorldInteractionDemoby double clicking it in the Project window. For the AR project, open the Scene atAssets\Scenes\ARInteraction. - Configure the VR project for XR devices
- From Unity’s main menu, go to Edit > Project Settings > XR Plug-in Management, and select the platform(s) you plan to deploy to
- To run the VR sample on a headset, go to File > Build Settings and build the app. If you have a PC VR headset, you can also preview the app by connecting your device and clicking Play (►)
If using VR, make sure the Game view has focus (required for XR input currently) by clicking it with your mouse. A Lock Input to Game View option is available in the Input Debugger window (Window > Analysis > Input Debugger). Enabling this option forces input to continue processing even when the Game view does not have focus.
This repository contains two different example Unity projects, one with a focus on a Virtual Reality (VR) experience, and another with a focus on an Augmented Reality (AR) experience for mobile.
This example project contains several Scenes located in Assets\Scenes and Assets\VR Examples\Scenes.
| Scene | Description |
|---|---|
Scenes\WorldInteractionDemo |
This Scene contains several demo stations that demonstrate various features of the XR Interaction Toolkit. This scene also uses an XR Rig to showcase various ways of navigating the virtual environment via locomotion, including snap-turning, continuous turning, continuous movement, and teleportation. This Scene also makes use of several custom behaviors included with this Unity project, including a Controller Manager which manages a logical controller state to selectively enable or disable certain input actions and behaviors. Your left hand can grab objects remotely using a Ray Interactor, and your right hand can grab objects directly using a Direct Interactor. Pushing up on the thumbstick will switch to a different Ray Interactor used for teleportation, and releasing the thumbstick will teleport when aiming at a valid location. Pushing left, right, or down on the thumbstick will turn left, right, or around, respectively. Use the trigger to interact with the UI in the world while pointing at it with the left controller. The station in the Scene labeled Locomotion Configuration can be used to change locomotion control schemes and configuration preferences. For example, using the controller to enable Continuous Move will make it so the rig will move based on the left controller thumbstick instead of being used to turn and teleport. |
Scenes\DeprecatedWorldInteractionDemo |
A similar environment to WorldInteractionDemo, but with an alternate XR Rig setup that uses the Device-based variants of behaviors that do not use the Input System. It is recommended that you use the Action-based variant of behaviors used in WorldInteractionDemo instead of the Device-based variant to take advantage of the benefits that the Input System package provides. Some features, such as the XR Device Simulator, are only supported when using Actions. This Scene is included mainly as a reference for users who began using the package before version 0.10.0. |
VR Examples\Scenes\Initial Tracking |
This is a basic scene that shows how to set up device tracking. Look around in your VR headset and identify the tracked hand controllers. |
VR Examples\Scenes\Grab Interaction |
This scene shows how to set up a grab interactable that can be grabbed by either hand controller. Your left hand can grab the cube remotely using a Ray Interactor, and your right hand can grab it directly using a Direct Interactor. |
VR Examples\Scenes\Socket Interaction |
This scene shows how to set up a socket to hold an interactable. Grab the cube then try throwing it to the socket. You will see the cube snap to the socket. |
VR Examples\Scenes\Teleportation |
This scene shows examples of configuring Teleportation Areas, Anchors, and options on visuals and orientation. Use the Trigger (Select) button on your controller to teleport when pointing to a platform. |
VR Examples\Scenes\UI Interaction |
This scene shows how to set up a world canvas UI. Use the trigger button to interact with the UI elements. |
This project contains two variants of a Controller Manager behavior to manage multiple Interactors depending on different conditions of the player.
The ActionBasedControllerManager script makes use of Input System Actions to both read input to detect logical controller state changes, and to enable or disable shared Actions. This is used in the WorldInteractionDemo Scene to swap between two mutually exclusive Interactor behaviors for each controller. For example, for the right-hand Controller Manager, when detecting input to activate a teleportation mode, the behavior as configured in the Scene will swap between the Direct Interactor used for grabbing objects, and the Ray Interactor used for aiming a teleportation arc.
The ControllerManager script is similar to the ActionBasedControllerManager script, but uses the API to read features values of an InputDevice directly rather than from Input System Actions. It also differs in that it only manages transitions between two states: a normal selection state, and a teleportation state. This is used in the DeprecatedWorldInteractionDemo Scene.
The LocomotionSchemeManager script in the example project is used in the WorldInteractionDemo Scene. It is used as a central manager to configure locomotion control schemes and configuration preferences.
The LocomotionConfigurationMenu script is used to present locomotion control schemes and configuration preferences, and respond to player input in the UI to set them. It is attached to a Canvas in the WorldInteractionDemo Scene as a way for the player to adjust settings related to locomotion.
The Default Input Actions sample included with the XR Interaction Toolkit package is installed in this example project, which contains an Input Actions Asset with different locomotion control schemes. When used with the Locomotion Scheme Manager as configured in the Scene, this allows the player to swap between different input styles for locomotion, such as changing between snap-turning left and right, and smooth turning.
A modified Android manifest file is used to enable the Oculus system keyboard when an input field receives focus, an example of which is in the WorldInteractionDemo Scene. This was done by editing the generating AndroidManifest.xml file created by first opening Edit > Project Settings > Player, clicking the Android settings tab, and then under the Build header clicking to enable Custom Main Manifest. The following line was added to the manifest element:
<uses-feature android:name="oculus.software.overlay_keyboard" android:required="false"/>This example project contains a Scene located in Assets\Scenes. The AR example project currently supports only mobile AR platforms. See the ARKit documentation or the ARCore documentation for more details on how to set up the project to deploy to either platform.
| Scene | Description |
|---|---|
Scenes\ARInteraction |
This scene shows how to set up a Gesture Interactor and a Placement Interactable for a mobile AR experience. Place a cube onto a detected plane, and use gestures to move, rotate, and scale the placed object. This demonstrates the functionality of |
Scenes\ARInteraction_MultipleObjects |
This scene is similiar to Known Limitations: Taps on the dropdown UI when over a tracked plane will also place an object. |
If you are deploying to Android, you must change a few build settings in order to build the app.
- Open a web browser and go to https://gradle.org/releases/
- Download Gradle v5.6.4 (binary-only is fine) and unzip it into a location of your choosing.
- Go to Edit > Preferences > External Tools, then under the Android header uncheck Gradle Installed with Unity, then set the Gradle location to the location where you unzipped the download.
Build files have already been modified in the AR example project to support building to Android 11. See Build for Android 11 for steps needed to build using Unity 2019.4 for a new project.
- Go to Edit > Project Settings > Player and click the Android settings tab.
- Click to expand Publishing Settings, then under the Build header uncheck Custom Main Gradle Template and Custom Launcher Gradle Template. Those modified build files are only necessary when using Unity 2019.4.