Build Your MR Game & Publish it on Meta's Horizon Store

Prerequisites

• Unity Hub

• Unity 2022.3 LTS (this course used 2022.3.5f1)

• Unity Android Support

• Unity Windows Support

  
  

Important Links

Install Unity Hub: https://unity.com/download

Unity HubUnity Download Archive: https://unity.com/releases/editor/archive

Description

In this chapter we’ll get Unity installed and configured for Meta Quest devices.

If you’re just installing Unity for the first time, be sure to install a 2022.3 LTS version and during setup make sure to select the following to enable Android and Windows platform support:

You can refer back to the prerequisites document for additional details on setting up Unity.

When Sean instructs you to select the project type “3D (URP)” you may not have it installed on your machine. That’s OK, just click the “Download template” button for it to install and then you can continue.

In this chapter, we’ll import the Meta SDK and get the project ready to build and deploy to a Quest device.

When Sean instructs you to add the Meta package in the Unity Package Manager, here are the details:

Package Name: com.meta.xr.sdk.all

Package Version: 66.0.0

NOTE: If the version number is left blank, Unity will install the latest version of the SDK. Though the content of this course should still be relevant with future SDK versions, it was recorded with version 66.

In this chapter, we’ll create our first scene and get it ready for VR using the Camera Rig Building Block.

Prerequisites

• Quest headset must be in Developer Mode.

• We recommend using the Meta Quest Developer Hub to enable Developer Mode and make it easier to deploy apps to the headset.

  
  

Important Links

Getting Started with Meta Quest Developer Hub https://developer.oculus.com/documentation/unity/ts-odh/

Deploy Build on Headset https://developer.oculus.com/documentation/unity/ts-odh-deploy-build/

Description

In this chapter, we will complete our first build and deploy it to the device for testing.

Before you can deploy an app, your device must be set to Developer Mode. We recommend following the steps in Getting Started with Meta Quest Developer Hub to install the hub and enable Developer Mode on your device.

When it’s time to deploy your app for testing, see Deploy Build on Headset for the steps to install the package.

Once the application is deployed to the device, you’ll need to go under App Library and be sure to select ‘Unknown sources’ to find and launch your application.

Important Links

GorillaZilla Package: https://drive.google.com/file/d/1aRtGjaVPu1Im2Sji_0VH-wG0bG7o7GuF/view?usp=drive_link

Description

In this chapter, we’ll import the GorillaZilla assets into our project so that we can begin building and learning about components, blocks, and scripts.

When Sean opens the " BuildingBlocksVersion " scene, your view may look a little different. This is because Unity defaults to a large icons view, but Sean uses a details view. At the bottom of the Project window, there is a slider. Dragging that slider to the left will result in the same details view that Sean has on his screen.

Let’s learn about the Passthrough camera system, which allows our virtual objects to appear within our physical environment.

In this chapter, we will add passthrough support to our scene.

IMPORTANT: Before you begin this chapter, please rename OurFirstScene to DevScene and open it. Also, if you created a test cube in this scene please delete it now.

In this chapter, we’ll learn how to change the color of the passthrough. This provides a neat effect for important game events.

In this chapter, we’ll be completing your space setup!

In this chapter, we’ll learn about Smart Object Positioning with Scene Understanding.

In this chapter, we’ll add the Game Manager component to our scene and learn how it helps us layout a city in our physical space.

In this module, we’ll learn about the Meta Interaction SDK, a library that allows users to interact with digital worlds through. We’ll learn about controller tracking, hand tracking, and interactions like grab and throw.

Prerequisites

• Quest Link or Air Link

• Sensor streaming over Link enabled in the Oculus App

Important Links

Meta Quest Link and Air Link: https://www.meta.com/help/quest/articles/headsets-and-accessories/oculus-link/connect-with-air-link

Description

• In this chapter, we will add add support for controllers to our scene. We will also start using Unity “Play Mode” to rapidly test and iterate on our experience.

  Please note that Sean moved DevScene from Assets\Scenes to Assets\_Core\Scenes. Feel free to move your DevScene, but it’s also okay to leave it where it is.

  IMPORTANT: If you haven’t already done so, please follow the instructions below to enable Quest Link and enable sensor streaming from your device.

Configure Headset for Quest Link or Air Link

Quest Link allows you to play VR titles made for the PC on your Meta Quest. Quest Link also allows you to rapidly develop in Unity since you’ll be able to press “Play” and immediately start running your experience on the headset without having to build an application and deploy it to the device.

Quest Link works over a high-speed USB-C cable. Air Link is similar to Quest Link but works wirelessly over WIFI. Please note that Air Link depends heavily on having a high-speed low-latency router, so we recommend using Quest Link for this course.

Please set either Quest Link or Air Link:

Setup Quest Link (recommended)

Setup Air Link (optional)

Enable Developer Features Over Link

Testing applications quickly in Unity is tremendously powerful, but we have one more important additional step to complete before it will work properly. By default, sensor data from your Quest headset isn’t allowed to stream to your desktop PC for privacy reasons. You must opt into allowing this streaming of data. To do so:

Go into the Meta Quest Link app, then click on Settings > Beta (tab).

Turn on Developer Runtime Features, then turn on all of the toggles that allow sensor data to be sent over Link.

In this chapter, we enable hand tracking, and we learn how to make objects grabbable and throwable.

In this chapter, we’ll look at the Pokable Item block and how it can be used to make buttons for our menu.

In this chapter, we’ll add hand tracking support to Gorilla Zilla, including pokable menus and cool monster hands!

In this module, we’ll learn about the Movement SDK and how we can use it to enable features like face and eye tracking.

Important Links

Movement SDK Overview https://developer.oculus.com/documentation/unity/move-overview/

Unity Movement Package on GitHub https://github.com/oculus-samples/Unity-Movement.git#v3.1.1

Description

• In this chapter, we’ll import the Movement Samples from GitHub and create the layers necessary for the samples to function.

  When Sean adds the sample package from GitHub, here’s the URL you can copy and paste into Package Manager:

  *https://github.com/oculus-samples/Unity-Movement.git#v3.1.1*

  Note that later versions should work, but this class was recorded with package version 3.1.1.

In this chapter, we’ll create a sample scene to test out the Meta avatar rig and see the Movement SDK in action.

In this chapter, we’ll learn about the various Body Tracking samples and learn about some of the use cases for body, face, and eye tracking.

In this module, we learn about speech capabilities in the Voice SDK. We’ll learn about Intents, and we’ll use Text to Speech to assist users during the GorillaZilla tutorial.

In this chapter, we’ll add Text to Speech to our scene, and leverage it to help users through the tutorial.

In this chapter, we’ll learn about the microphone capabilities in the Voice SDK. We’ll also use the volume sensing capabilities of the SDK to adjust the “Roar” destruction.

• IMPORTANT: When you test the game at the end of this chapter, make sure your system is setup to use the microphone from the Quest. This is only necessary when testing over Link. When you deploy the game to the headset it will of course use the built-in microphone.

  On Windows you can configure the microphone under Settings > System > Sounds > Input.

In this chapter, we’ll learn about publishing our app and learn how we will continue on our developer journey.

Prerequisites

• A Meta developer account

Important Links

Meta Quest Developer Center - https://developers.meta.com/horizon/

Description

• We’ll create an organization and an app where we can upload our application package.

  If you haven’t created an account yet, or to get started:

  Sign into the Meta Quest Developer Center

Important Links
https://developers.meta.com/horizon/discover/programs/start/”

For developers who have launched or are about to launch a title. Start provides access, support, and even discounts on Meta devices.

Description

• As our program comes to a close, let’s talk about where you can go next to continue your journey as a Meta Quest developer. We’ll talk about resources such as Oculus Start, Meta XR Events, and the Meta XR Events.