Skip to content

Commit 8855514

Browse files
authored
Merge pull request godotengine#7567 from dsnopek/improved-meta-quest-setup
Make the steps for deploying to Meta Quest 2 (and other Android headsets) clearer
2 parents c780bee + 968e8a7 commit 8855514

File tree

4 files changed

+33
-10
lines changed

4 files changed

+33
-10
lines changed

tutorials/export/one-click_deploy.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@ Using one-click deploy
5959

6060
.. image:: img/remote_debug.webp
6161

62+
.. _doc_one-click_deploy_troubleshooting:
63+
6264
Troubleshooting
6365
---------------
6466

tutorials/xr/deploying_to_android.rst

Lines changed: 31 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,25 @@ Deploying to Android
55

66
Setup
77
------------
8-
Most mobile headsets run on Android and OpenXR support is making its way to these platforms. There are specific requirements for deploying XR projects to Android.
9-
For general requirements around exporting to Android, please first read :ref:`doc_exporting_for_android`.
8+
Most mobile headsets run on Android and OpenXR support is making its way to these platforms.
9+
10+
Before following the OpenXR-specific instructions here, you'll need to first setup your system to export to Android in general, including:
11+
12+
- Installing OpenJDK 11
13+
- Installing Android Studio
14+
- Creating a debug.keystore
15+
- Configuring the location of the Android SDK and debug.keystore in Godot
16+
17+
See :ref:`doc_exporting_for_android` for the full details, and return here when you've finished these steps.
18+
19+
Custom Android build
20+
--------------------
1021

1122
.. note::
1223
Official support for the Android platform wasn't added to the OpenXR specification initially resulting in various vendors creating custom loaders to make OpenXR available on their headsets.
1324
While the long term expectation is that all vendors will adopt the official OpenXR loader, for now these loaders need to be added to your project.
1425

15-
Custom Android build
16-
--------------------
17-
In order to deploy the loaders into your project you will need to setup a custom Android build.
26+
In order to include the vendor-specific OpenXR loader into your project, you will need to setup a custom Android build.
1827

1928
Select **Install Android Build Template...** from the **Project** menu:
2029

@@ -35,14 +44,15 @@ There is a subfolder called **plugins** containing the new files.
3544

3645
You can find the main repository of the loader plugin `here <https://github.com/GodotVR/godot_openxr_loaders>`__.
3746

38-
Creating the export templates
39-
-----------------------------
40-
You will need to setup a separate export template for each device as each device will need its own loader included.
47+
Creating the export presets
48+
---------------------------
49+
You will need to setup a separate export preset for each device, as each device will need its own loader included.
4150

4251
Open **Project** and select **Export..**.
4352
Click on **Add..** and select **Android**.
44-
Next change the name of the export profile for the device you're setting this up for, say **Meta Quest**.
53+
Next change the name of the export preset for the device you're setting this up for, say **Meta Quest**.
4554
And enable **Use Gradle Build**.
55+
If you want to use one-click deploy (described below), ensure that **Runnable** is enabled.
4656

4757
If the loader plugins were installed correctly you should find entries for the different headsets, select the entry for meta:
4858

@@ -56,7 +66,7 @@ The hand tracking and passthrough settings here currently only work for the Meta
5666
.. image:: img/xr_export_features.webp
5767

5868

59-
Now you can repeat the same process for the other devices. Note that if you wish to test your game with Godots one-click deploy, you have to mark the export profile for your device as **Runnable** so Godot knows which loader to deploy.
69+
Now you can repeat the same process for the other devices.
6070

6171
.. note::
6272
There are separate loaders for the Meta Quest, Pico and Lynx R1 headsets.
@@ -70,3 +80,14 @@ Now you can repeat the same process for the other devices. Note that if you wish
7080

7181
Note that we are awaiting driver updates on various devices before Vulkan support will work on these.
7282

83+
Running on your device from the Godot editor
84+
--------------------------------------------
85+
If you've setup your export settings as described above, and your headset is connected to your computer and correctly recognized, you can launch it directly from the Godot editor using :ref:`doc_one-click_deploy`:
86+
87+
.. image:: img/android_one_click_deploy.webp
88+
89+
For some devices on some platforms, you may need to perform some extra steps in order for your device to be recognized correctly, so be sure to check the developer documentation from your headset vendor.
90+
91+
For example, with the Meta Quest 2, you need to enable developer mode on the headset, and if you're on Windows, you'll need to install special ADB drivers. See the `official Meta Quest developer documentation <https://developer.oculus.com/documentation/native/android/mobile-device-setup/>`_ for more details.
92+
93+
If you're having any issues with one-click deploy, check the :ref:`Troubleshooting section <doc_one-click_deploy_troubleshooting>`.
5.89 KB
Loading
13.8 KB
Loading

0 commit comments

Comments
 (0)