naga
wgpu-rs
Our great sponsors
naga | wgpu-rs | |
---|---|---|
28 | 16 | |
1,491 | 1,699 | |
0.7% | - | |
9.2 | 9.0 | |
5 months ago | almost 3 years ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
naga
- How does webgpu planning to use webgl shaders?
-
I want to talk about WebGPU
That wouldn't have been all that different from WGSL though, the most important thing is that whatever WebGPU uses for its shaders can be translated to and from SPRIV (and WGSL does that too (e.g. via https://dawn.googlesource.com/tint and https://github.com/gfx-rs/naga).
-
Survey: How have shader compilation messages been for you?
Hey all, wanted to put this link in here, where I'm proposing changing the API for errors in naga, so Naga can take ownership of error presentation and actually Make Shader Compilation Messages Comfy™: https://github.com/gfx-rs/naga/issues/2317
-
Start project on Metal, port to DX11?
EDIT: There is also naga but it does not take HLSL as input: https://github.com/gfx-rs/naga but you can use DirectXShaderCompiler to compile to SpirV, then use naga to compile to Metal.
-
Chrome ships WebGPU (available by default in Chrome 113)
And it seems that naga https://github.com/gfx-rs/naga Already has a working front/backend for wgsl.
-
Ray query example in Blade
This is basically Ray Tracing support in Blade. So far, only ray queries are supported. Unlike prior work on ray tracing in Rust, this is original due to all shader code being WGSL, see the Naga PR.
-
Does WGSL work well with vulkan?
There's a compiler that can translate from WGSL to SPIR-V called naga. Having such a compiler is essential, since WebGPU is planned to use WGSL and browsers are expected to implement rendering via Vulkan (and probably Metal and DX12).
-
Glsl transpiler, interpreter?
Not sure about on the CPU, but naga is a shading language transpiler you can write custom front/backends for.
-
Any guides/documentation on the WGSL shading language?
The spec docs are actually pretty useful https://www.w3.org/TR/WGSL/ besides that I was using naga's tests for reference https://github.com/gfx-rs/naga/tree/master/tests
-
How are Vulkan, CUDA, Triton and all other things connected?
For cross-platform support look at WebGPU and Vulkan (e.g,: [0] [1]. Essentially, you would need to write the func in WGSL or GLSL, HLSL or MSL. Each of these can be cross-compiled to SPIR-V (what Vulkan needs) with cross-compilers such as spirv-cross and naga.
wgpu-rs
-
Using WGPU + crates directly or Bevy?
You could start with one of examples from wgpu and tinker with it to see if that's your thing. Ie. copy hello-triangle and add more triangles / make them move, etc.
-
gfx-rs ecosystem releases v0.8
wgpu-rs (https://github.com/gfx-rs/wgpu-rs) is probably closer to what you're looking for, it's a "high level wrapper" over wgpu-core (Which implements "WebGPU", an upcoming browser API for graphics using gfx-rs, and AIUI "implements" means this is what a browser might use to actually call a graphics API when javascript uses webGPU, although if you're compiling for wasm it could just call the browser APIs). It can run natively, ignore the fact it has "Web" in the name
- Rust shader translator is 2.5x faster
-
GPU compute shader for SHA256 using Rust!
rust-gpu) is used for compiling a compute shader written in Rust to SPIR-V. wgpu-rs is used natively for running the GPU computation.
- GPU programming .. SYCL
-
Bevy 0.5
For web assembly there is the unofficial bevy_webgl2 plugin. Official bevy web assembly support would probably use the wgpu webgl backend, which still needs some work, and is currently untested in bevy.
-
Bevy 0.5: data oriented game engine built in Rust
We let wgpu https://github.com/gfx-rs/wgpu-rs handle our graphics backend abstraction, so our OpenGL support will come whenever they implement and release it. Currently, it seems to be a WIP.
-
Help a newbie (in this language) to find directions :)
It's the same thing, the Rust implementation is just called[wgpu](https://wgpu.rs/)
-
Last big wgpu-rs example shaders are fully ported to WGSL now, and validated in it
Same as with GLSL, isn't it? What we do in wgpu-rs examples, and that's something I expect to see more widely, is having an integration test that just parses all the WGSL in the project and reports errors. Ideally though, we'd have a set of IDE plugins to do the parsing and report errors right where you type the code. We'd appreciate any help to get these started!
-
Newbie questions on design patterns in Rust
Also you could use an existing cross-platform graphics library, e.g. wgpu-rs. It supports Vulkan, Metal, DirectX, OpenGL and WebGPU. Oh and it seems to allow switching backends at compile-time via the WGPU_BACKEND environment variable, so maybe check out how they're doing it.
What are some alternatives?
wgsl-cheat-sheet - Cheat sheet for WGSL syntax for developers coming from GLSL.
ash - Vulkan bindings for Rust
shaderc - A collection of tools, libraries, and tests for Vulkan shader compilation.
gfx - [maintenance mode] A low-overhead Vulkan-like GPU API for Rust.
wgsl.vim - WGSL syntax highlight for vim
awesome-bevy - A collection of Bevy assets, plugins, learning resources, and apps made by the community
wgsl-mode - Emacs syntax highlighting for the WebGPU Shading Language (WGSL)
bevy_webgl2 - WebGL2 renderer plugin for Bevy game engine
SPIRV-Cross - SPIRV-Cross is a practical tool and library for performing reflection on SPIR-V and disassembling SPIR-V back to high level languages.
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
gpuweb - Where the GPU for the Web work happens!