mirror of
https://github.com/storytold/wgpu.git
synced 2026-11-20 06:21:13 +01:00
523: Change buffer binding to not take a slice r=cwfitzgerald,grovesNL a=kvark This has been a constant source of confusion w.r.t dynamic offsets. What it looks like it's doing: user provides a slice of buffer visible to the shader. Just like they provide slices to vertex and index buffer bindings. What it's actually doing: it takes the offset and size separately, modifying the offset later on based on the dynamic offset. We don't need this confusion. Semantics is different from `BufferSlice` and so we should have a different API here. Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
Structure
For the simplest examples without using any helping code (see framework.rs here), check out:
hellofor printing adapter informationhello-trianglefor graphics and presentationhello-computefor pure computing
Notably, capture example shows rendering without a surface/window. It reads back the contents and saves them to a file.
All framework-based examples render to the window.
Feature matrix
| Feature | boids | cube | mipmap | msaa-line | shadow | skybox | texture-arrays | water |
|---|---|---|---|---|---|---|---|---|
| vertex attributes | ⭐ | ⭐ | ⭐ | ⭐ | ⭐ | ⭐ | ⭐ | |
| instancing | ⭐ | |||||||
| lines and points | ⭐ | |||||||
| dynamic buffer offsets | ⭐ | |||||||
| implicit layout | ||||||||
| sampled color textures | ⭐ | ⭐ | ⭐ | ⭐ | ⭐ | ⭐ | ||
| storage textures | ⭐ | |||||||
| binding array | ⭐ | |||||||
| comparison samplers | ⭐ | |||||||
| subresource views | ⭐ | ⭐ | ||||||
| cubemaps | ⭐ | |||||||
| multisampling | ⭐ | |||||||
| off-screen rendering | ⭐ | ⭐ | ||||||
| stencil testing | ||||||||
| depth testing | ⭐ | ⭐ | ||||||
| depth biasing | ⭐ | |||||||
| read-only depth | ⭐ | |||||||
| blending | ⭐ | |||||||
| render bundles | ⭐ | ⭐ | ||||||
| compute passes | ⭐ | |||||||
| optional extensions | ⭐ | |||||||
| - binding indexing | ⭐ | |||||||
| - push constants | ⭐ | |||||||
| - depth clamping | ⭐ | |||||||
| - BCn compressed textures | ⭐ | |||||||
| WGSL shaders |
Hacking
You can record an API trace any of the framework-based examples by starting them as:
mkdir -p trace && WGPU_TRACE=trace cargo run --features trace --example <example-name>