Skip to content

Rephrase wording around dynamic rendering regarding performance #349

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

Merged
gpx1000 merged 1 commit into from
Mar 28, 2026
+1 −2
Merged

Rephrase wording around dynamic rendering regarding performance #349

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
3 changes: 1 addition & 2 deletions en/Building_a_Simple_Engine/Mobile_Development/05_vulkan_extensions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,8 +316,7 @@ Different mobile vendors and devices vary in which Vulkan extensions they expose

Different mobile GPU vendors have varying levels of support for Vulkan extensions:

* *Dynamic Rendering Support*: Many mobile GPUs have optimized
implementations of `VK_KHR_dynamic_rendering`. This can lead to significant performance improvements compared to traditional render passes, especially on tile-based renderers.
* *Dynamic Rendering Support*: Many mobile GPUs support `VK_KHR_dynamic_rendering`. This simplifies the API surface, but can be slower than using traditional render passes when multiple sub passes are involved, unless one of the following tile-based optimizations is supported.

* *Tile-Based Optimizations*: On tile-based GPUs (e.g., Mali, PowerVR), `VK_EXT_shader_tile_image` and `VK_KHR_dynamic_rendering_local_read` are effective because they keep reads and writes in tile memory. See the extension sections above for details; benefits are workload- and GPU-dependent.

Expand Down
Loading