Vulkan-Docs
wgsl-cheat-sheet
| Vulkan-Docs | wgsl-cheat-sheet | |
|---|---|---|
| 161 | 1 | |
| 2,663 | 11 | |
| 0.3% | - | |
| 8.4 | 4.2 | |
| 14 days ago | almost 3 years ago | |
| JavaScript | ||
| GNU General Public License v3.0 or later | - |
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.
Vulkan-Docs
-
GPU synchronization in Godot 4.3 is getting a major upgrade
Pipelines (or in general terms PSOs) are the most problematic aspect of Vulkan / DX12 - much more than synchronization! Large parts of the gamedev industry seems to recognize all the performance issues with pipelines and therefore companies are experimenting with newer models like the VK_EXT_shader_object extension ("Vulkan without Pipelines": https://www.khronos.org/blog/you-can-use-vulkan-without-pipe...).
I've written a detailed comment about this before here (https://news.ycombinator.com/item?id=37843946#37845431) but for a much more comprehensive explanation by an engineer from Nintendo read the initial proposal for the VK_EXT_shader_object extension: https://github.com/KhronosGroup/Vulkan-Docs/blob/main/propos...).
There's also Casey Muratori's mail to the Vulkan advisory on 2015 that basically predicts this whole clusterfuck would happen: https://github.com/cmuratori/misc/blob/main/vulkan_dynamic_s...
- Vulkan 1.3.273 spec update
- [Roadmap Feedback] Function Pointers with some limitations
-
New Vulkan Documentation Website
Apple -> MoltenVK is an emulation layer and doesn't give you as much control as using Metal directly.
Nintendo and Sony prefer their own APIs, NVN and LibGNM, and AIUI Vulkan is a second-class API on those platforms which does not offer as much power, it is widely understood studios use NVN and LibGNM to get access to the real hardware on those platforms.
Windows/AMD/NVidia/Intel -> HW manufacturers tend to prototype and release new features with D3D first and then 'backport' them to Vulkan after a while. DirectX 12 for example had mesh shaders for over 2 years before Vulkan got a vendor neutral extension for them[0]
Android and Linux are the only platform where Vulkan is a first-class citizen.
You could maybe argue Nvidia treats Vulkan as a first-class citizen because they tend to have vendor-specific Vulkan extensions for the latest features available before anyone else. But otherwise, no, Vulkan is not a first-class API anywhere except Linux and Android.
Graphics API wars are alive and well.
[0] https://github.com/KhronosGroup/Vulkan-Docs/issues/1423
- Vulkan 1.3.267 spec update
- Vulkan 1.3.266 spec update
- Vulkan 1.3.262 spec update
- Vulkan 1.3.260 spec update
- Vulkan 1.3.257 spec update
- Vulkan 1.3.256 spec update
wgsl-cheat-sheet
-
Porting WebGL Shaders to WebGPU
Good article, I was looking for a resource like this when I was experimenting with WGSL. I ended up writing a short cheat sheet that might be useful to others here: https://github.com/paulgb/wgsl-cheat-sheet
What are some alternatives?
vkd3d-proton - Fork of VKD3D. Development branches for Proton's Direct3D 12 implementation.
naga - Universal shader translation in Rust
webgpu-wgsl-hello-triangle - An example of how to render a triangle with WebGPU using WebGPU Shading Language - the "Hello world!" of computer graphics.
noclip.website - A digital museum of video game levels
Vulkan-Headers - Vulkan header files and API registry
gpuweb - Where the GPU for the Web work happens!
WASI - WebAssembly System Interface
naga-include-poc
Vulkan - Examples and demos for the new Vulkan API
vulkan-gp