From 349c750b18acf770ef6f0e43643c8a37a3beb450 Mon Sep 17 00:00:00 2001 From: Zak Grumbles Date: Thu, 24 Sep 2020 22:06:55 -0500 Subject: [PATCH] Improve documentation for Camera3D's `current` member * Added additional information to the camera documentation to explain how the 'current' attribute behaves when multiple cameras are in a scene. --- doc/classes/Camera3D.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/classes/Camera3D.xml b/doc/classes/Camera3D.xml index 56e5ce1522c..468fddcfc1c 100644 --- a/doc/classes/Camera3D.xml +++ b/doc/classes/Camera3D.xml @@ -155,6 +155,7 @@ If [code]true[/code], the ancestor [Viewport] is currently using this camera. + If multiple cameras are in the scene, one will always be made current. For example, if two [Camera3D] nodes are present in the scene and only one is current, setting one camera's [member current] to [code]false[/code] will cause the other camera to be made current. If not [constant DOPPLER_TRACKING_DISABLED], this camera will simulate the [url=https://en.wikipedia.org/wiki/Doppler_effect]Doppler effect[/url] for objects changed in particular [code]_process[/code] methods. See [enum DopplerTracking] for possible values.