deploy: 5647fba

.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: 37c8e6399b0a128fb5f8e2f0b494c911
+tags: 645f666f9bcd5a90fca523b33c5a78b7

_sources/dagor-render/index.rst.txt

@@ -0,0 +1,12 @@
+.. Dagor Engine Render documentation master file
+
+Dagor Engine Render
+===============================================
+
+.. toctree::
+   :maxdepth: 4
+   :caption: Contents:
+   :glob:
+
+   index/*
+

_sources/dagor-render/index/d3dAPI.rst.txt

@@ -0,0 +1,15 @@
+D3D API
+=================================================
+
+D3D API is our unified API which hides GAPI calls for different platforms.
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Contents:
+
+   d3dAPI/Buffers
+   d3dAPI/RenderPass
+   d3dAPI/other
+   d3dAPI/constants
+   d3dAPI/textures
+   d3dAPI/helperClasses

_sources/dagor-render/index/d3dAPI/Buffers.rst.txt

@@ -0,0 +1,5 @@
+Buffers
+=================================================
+
+.. autodoxygenfile:: dag_drv3d_buffers.h
+  :project: d3dAPI

_sources/dagor-render/index/d3dAPI/RenderPass.rst.txt

@@ -0,0 +1,31 @@
+RenderPass
+=================================================
+
+* See samples/testDrv3d/render_pass_tests.h for example usage
+
+Callable d3d:: methods
+
+.. doxygengroup:: RenderPassD3D
+  :project: d3dAPI
+  :members:
+  :undoc-members:
+  :content-only:
+
+=================================================
+
+Related structures
+
+.. doxygengroup:: RenderPassStructs
+  :project: d3dAPI
+  :members:
+  :undoc-members:
+  :content-only:
+
+=================================================
+
+Related constants
+
+.. doxygengroup:: RenderPassConsts
+  :project: d3dAPI
+  :members:
+  :content-only:

_sources/dagor-render/index/d3dAPI/constants.rst.txt

@@ -0,0 +1,5 @@
+Constants, Structures and Enumerations
+=================================================
+
+.. autodoxygenfile:: dag_drv3dConsts.h
+  :project: d3dAPI

_sources/dagor-render/index/d3dAPI/helperClasses.rst.txt

@@ -0,0 +1,10 @@
+Helper classes for D3D API
+=================================================
+
+These classes are not part of core D3D API, but they simplifies common usages of D3D API.
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Contents:
+
+   helperClasses/multidrawContext

_sources/dagor-render/index/d3dAPI/helperClasses/multidrawContext.rst.txt

@@ -0,0 +1,5 @@
+MultidrawContext
+=================================================
+
+.. autodoxygenfile:: dag_multidrawContext.h
+  :project: d3dAPI

_sources/dagor-render/index/d3dAPI/other.rst.txt

@@ -0,0 +1,5 @@
+All other methods
+=================================================
+
+.. autodoxygenfile:: dag_drv3d.h
+  :project: d3dAPI

_sources/dagor-render/index/d3dAPI/textures.rst.txt

@@ -0,0 +1,5 @@
+Textures
+=================================================
+
+.. autodoxygenfile:: dag_tex3d.h
+  :project: d3dAPI

_sources/dagor-render/index/daBFG.rst.txt

@@ -0,0 +1,20 @@
+daBFG API
+=================================================
+
+daBFG is a library for constructing and executing a *frame graph*, a computational graph for specifying a rendering pipeline of an real time application. It supports many fun features, such as:
+ * Homogenous management of many types of resources: transient and temporal, CPU data, GPU textures and buffers, external resources like system backbuffers
+ * Memory aliasing for all internally managed resources (even temporal ones!)
+ * Automatic barriers
+ * Global state management: (fake) render passes, bindings, VRS and more!
+ * Multiplexing support: want to run your graph multiple times for VR? No problem! It just works (as long as you annotate node multiplexing modes correctly and don't do any global state crimes)
+ * More to come soon!
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Contents:
+
+   daBFG/core
+   daBFG/declaringNodes
+   daBFG/graphState
+   daBFG/runtime
+   daBFG/das

_sources/dagor-render/index/daBFG/core.rst.txt

@@ -0,0 +1,28 @@
+Core Functions
+=================================================
+
+The library exposes several global functions for controlling the global
+graph state encapsulated inside the library, listed below. The graph
+is always singular and global by design. This allows for the most
+effective optimization of memory and other resources due to all
+information being visible and available to the backend.
+
+However, for separating different logical parts of the global graph,
+e.g. for different viewports (editor and game preview) all daBfg entities
+(nodes, resources, automatic resolutions, etc) are namespaced. A node
+might have the name "/foo/bar/node", but you never actually use this
+name to refer to a node, as we don't want to be parsing strings.
+Instead, wrapper objects describing a particular namespace are used.
+
+Hence, the code that wants to register various objects inside the graph,
+like nodes and resolutions, must use the :cpp:class:`dabfg::NameSpace`
+class to do so, although aliases for calling methods of this class on
+the global namespace :cpp:func:`dabfg::root` are available.
+
+.. doxygengroup:: DabfgCore
+  :project: daBFG
+  :members:
+
+.. doxygengroup:: DabfgCoreAliases
+  :project: daBFG
+  :members: