[Bf-docboard-svn] bf-manual: [9837] trunk/blender_docs/manual/compositing/realtime_compositor.rst: Document realtime compositor output

[Omar Emara]

Revision: 9837
          https://developer.blender.org/rBM9837
Author:   OmarSquircleArt
Date:     2022-12-31 14:51:54 +0100 (Sat, 31 Dec 2022)
Log Message:
-----------
Document realtime compositor output

Modified Paths:
--------------
    trunk/blender_docs/manual/compositing/realtime_compositor.rst

Modified: trunk/blender_docs/manual/compositing/realtime_compositor.rst
===================================================================
--- trunk/blender_docs/manual/compositing/realtime_compositor.rst	2022-12-31 01:19:59 UTC (rev 9836)
+++ trunk/blender_docs/manual/compositing/realtime_compositor.rst	2022-12-31 13:51:54 UTC (rev 9837)
@@ -315,3 +315,20 @@
 horizontal direction using the :ref:`Blur node <bpy.types.CompositorNodeBlur>`, the blurring will
 apparently take place along the vertical direction instead, because the node is applied in the local
 pixel space of the input.
+
+Output
+======
+
+The realtime compositor only supports a single active output target, that is, only one of the
+:ref:`Composite nodes <bpy.types.CompositorNodeComposite>`, :ref:`Viewer nodes
+<bpy.types.CompositorNodeViewer>`, or :ref:`Split Viewer nodes
+<bpy.types.CompositorNodeSplitViewer>` in the node tree will be considered active and the rest will
+be ignored. In particular, the compositor searches the *Active Node Tree Context* and falls back to
+the *Root Node Tree Context* if no active output was found in the active node tree context. The
+active node tree context is the node tree of an expanded node group, that is, when the users selects
+a node group node and edits its underlying tree, while the root node tree context is the top level
+node tree without any expanded node groups. The compositor searches for the active *Composite* node,
+if non was found, it searches for the active *Viewer* node, be it a *Viewer* or a *Split Viewer*
+node, if non was found, the compositor doesn't run altogether. Consequently, note that adding a
+*Viewer* node will have no effect if there is a *Composite* node, since the priority is given to
+*Composite* nodes.