naga VS vange-rs

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).

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

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.

And it seems that naga https://github.com/gfx-rs/naga Already has a working front/backend for wgsl.

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.

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).

Not sure about on the CPU, but naga is a shading language transpiler you can write custom front/backends for.

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

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.

This is a new rendering method I was working on in Rusty Vangers. It's based on using a hierarchical voxel grid (mipmapped 3D texture) as an acceleration structure for ray tracing. Allows viewing the level from any perspective, and is faster than the "painter" method.

You don't need to depend on Angle in the build system, or link to it statically. For the purposes of your program it's just a GL driver. You'd just take libEGL.dll and a few dependencies from somewhere and place it in your folder with the executable. You can either copy it from Chrome or Firefox distribution, or as an artifact from https://github.com/DileSoft/gfbuild-angle, which my friend has set up for http://vange.rs/ builds on older Windows.

I couldn't find any mention of it in the official documentation or online, and I looked in some repositories online until I saw something suspicious here where there is a comment mentioning an include.

This is a port of vange-rs on "wasm32-unknown-emscripten" target via wgpu's GLES3 backend. Done by @caiiiycuk (thank you!), and also described in https://habr.com/en/post/594611/ (in Russian language).

P.S. I'm fully using WGSL in vange-rs and baryon