Skip to content

Clarify the rendergraph section's relationship to the Simple Engine code #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gpx1000 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify the rendergraph section's relationship to the Simple Engine code #486

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions en/Building_a_Simple_Engine/Engine_Architecture/05_rendering_pipeline.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,12 @@ In this tutorial, we use Vulkan's dynamic rendering feature with vk::raii instea

=== Rendergraphs and Synchronization

NOTE: The rendergraph described in this section is an architectural pattern, not something
wired into the Simple Engine code in the attached examples. Treat the sections below as a
guide to a design you could add to the engine yourself, not a description of what
`attachments/simple_engine` currently does at runtime - the engine issues its render passes
directly, without going through a rendergraph abstraction.

A rendergraph is a higher-level abstraction that represents the entire rendering process as a directed acyclic graph (DAG), where nodes are render passes and edges represent dependencies between them. This approach offers several advantages over traditional render pass management:

==== What is a Rendergraph?
Expand Down
Loading