From 8b16ea409320117b5e870eadf2a5e966a79dceee Mon Sep 17 00:00:00 2001 From: David Snopek Date: Thu, 29 Jan 2026 13:13:18 -0600 Subject: [PATCH] Update `XRCamera3D` docs to clarify what it provides and overrides --- doc/classes/XRCamera3D.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/classes/XRCamera3D.xml b/doc/classes/XRCamera3D.xml index ca1cd431f68..73d632c56b2 100644 --- a/doc/classes/XRCamera3D.xml +++ b/doc/classes/XRCamera3D.xml @@ -1,11 +1,12 @@ - A camera node with a few overrules for AR/VR applied, such as location tracking. + A camera node which automatically positions itself based on XR tracking data. - This is a helper 3D node for our camera. Note that, if stereoscopic rendering is applicable (VR-HMD), most of the camera properties are ignored, as the HMD information overrides them. The only properties that can be trusted are the near and far planes. - The position and orientation of this node is automatically updated by the XR Server to represent the location of the HMD if such tracking is available and can thus be used by game logic. Note that, in contrast to the XR Controller, the render thread has access to the most up-to-date tracking data of the HMD and the location of the XRCamera3D can lag a few milliseconds behind what is used for rendering as a result. + A camera node which automatically positions itself based on XR tracking data. + In contrast to [XRController3D], the render thread has access to more up-to-date tracking data, and the location of the [XRCamera3D] node can lag a few milliseconds behind what is used for rendering. + [b]Note:[/b] If [member Viewport.use_xr] is [code]true[/code], most of the camera properties are overridden by the active [XRInterface]. The only properties that can be trusted are the near and far planes. $DOCS_URL/tutorials/xr/index.html