Document that VisionOS is supported

skyace65 · skyace65 · commit e780869e4f19 · 2025-07-25T07:06:12.000-04:00
diff --git a/about/list_of_features.rst b/about/list_of_features.rst
@@ -652,6 +652,8 @@ Mobile
   and :ref:`iOS <doc_plugins_for_ios>`.
 - Support for advertisements using third-party modules.
 
+.. _doc_xr_support:
+
 XR support (AR and VR)
 ----------------------
 
@@ -663,6 +665,11 @@ XR support (AR and VR)
 
   - Including support for popular stand alone headsets like the Meta Quest 1/2/3 and Pro, Pico 4, Magic Leap 2, and Lynx R1.
 
+- Out of the box limited support for visionOS Apple headsets.
+
+  - Currently only exporting an application for use on a flat plane within the
+    headset is supported. Immersive experiences are not supported.
+ 
 - Other devices supported through an XR plugin structure.
 - Various advanced toolkits are available that implement common features required by XR applications.
 
diff --git a/tutorials/export/img/export_preset.webp b/tutorials/export/img/export_preset.webp
diff --git a/tutorials/xr/setting_up_xr.rst b/tutorials/xr/setting_up_xr.rst
@@ -9,7 +9,12 @@ Introduction to the XR system in Godot
 Godot provides a modular XR system that abstracts many of the different XR platform specifics away from the user.
 At the core sits the :ref:`XRServer <class_xrserver>` which acts as a central interface to the XR system that allows users to discover interfaces and interact with the components of the XR system.
 
-Each supported XR platform is implemented as an :ref:`XRInterface <class_xrinterface>`. Supported interfaces register themselves with the :ref:`XRServer <class_xrserver>` and can be queried with the ``find_interface`` method on the :ref:`XRServer <class_xrserver>`. When the desired interface is found it can be initialized by calling ``initialize`` on the interface.
+Each supported XR platform is implemented as an :ref:`XRInterface <class_xrinterface>`.
+A list of supported platforms can be found on the list of features page :ref:`here <doc_xr_support>`.
+Supported interfaces register themselves with the :ref:`XRServer <class_xrserver>`
+and can be queried with the ``find_interface`` method on the :ref:`XRServer <class_xrserver>`.
+When the desired interface is found it can be initialized by calling ``initialize``
+on the interface.
 
 .. warning::
     A registered interface means nothing more than that the interface is available, if the interface is not supported by the host system, initialization may fail and return ``false``. This can have many reasons and sadly the reasons differ from platform to platform. It can be because the user hasn't installed the required software, or that the user simply hasn't plugged in their headset. You as a developer must thus react properly on an interface failing to initialize.
