marsultor/learn-wgpu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add validation layer discussion to GPU init section

Browse Source
This commit is contained in:
Krishna Ayyalasomayajula
2026-05-30 20:49:40 -05:00
parent 2586e9b813
commit 689b43da98
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/01-rainbow-triangle.md
View File

@@ -432,6 +432,16 @@ becomes a [command buffer](concepts/GLOSSARY.md#command-buffer) that is submitte
to this queue. On Vulkan, the device corresponds to `VkDevice` and the queue to this queue. On Vulkan, the device corresponds to `VkDevice` and the queue
to a `VkQueue`. to a `VkQueue`.
> **Key insight — Validation layers catch GPU errors at runtime:** wgpu ships
> with built-in validation layers that inspect your API calls for common
> mistakes: incorrect buffer bindings, mismatched pipeline state, out-of-bounds
> buffer slices, and resource lifecycle violations. These layers run
> automatically during development and surface errors as log messages or
> panics, saving hours of debugging silent GPU corruption. The tradeoff:
> validation adds measurable overhead to every frame. In release builds,
> disable validation by setting `DeviceDescriptor::device_type` or using
> the `WGPU_BACKEND` environment variable to skip the validation path.
**Step 5 — SurfaceConfiguration:** This allocates the **Step 5 — SurfaceConfiguration:** This allocates the
[swapchain](concepts/GLOSSARY.md#swapchain) [framebuffers](concepts/GLOSSARY.md#framebuffer). [swapchain](concepts/GLOSSARY.md#swapchain) [framebuffers](concepts/GLOSSARY.md#framebuffer).
We negotiate the pixel format with the driver (preferring an We negotiate the pixel format with the driver (preferring an