VulkanSceneGraph
webgpu-headers
Our great sponsors
| VulkanSceneGraph | webgpu-headers | |
|---|---|---|
| 7 | 4 | |
| 1,156 | 321 | |
| - | 2.8% | |
| 9.8 | 7.4 | |
| 3 days ago | about 1 month ago | |
| C++ | C | |
| MIT License | BSD 3-clause "New" or "Revised" License |
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.
VulkanSceneGraph
-
Vulkan all the way: Transitioning to a modern low-level graphics API in academia
I have not used this, but heard good things about Vulkan Scene Graph. https://github.com/vsg-dev/VulkanSceneGraph Like Open Scene Graph, it's more than just a scene graph. It provides math and geometry among other abstractions for computer graphics.
- The current state of GPU API's and why I wish V-EZ hadn't died.
- Examples of good Vulkan code organization and abstractions?
webgpu-headers
-
New Vulkan Documentation Website
There's standardized C API which is both implemented by Dawn and wgpu.rs:
https://github.com/webgpu-native/webgpu-headers/blob/main/we...
...and this standardized API would also enable other independent native implementations.
There's even thought put into the API being extensible via 'struct chaining', this is how the native implementations also accept SPIRV shader bytecode instead of just WGSL shader source code.
-
I want to talk about WebGPU
The API definition exists:
https://github.com/webgpu-native/webgpu-headers/blob/main/we...
The next missing piece is a standard window system glue API for WASI though.
-
The current state of GPU API's and why I wish V-EZ hadn't died.
At first it was for only web, but browsers implement it using compiled code (C++/Rust) and you can use the implementation directly. Wgpu is for Firefox, Dawn is for Chrome. There is a C header for them: https://github.com/webgpu-native/webgpu-headers/blob/main/webgpu.h.
-
Learn Wgpu
> Wgpu actually has C bindings to allow you to write C/C++ code with it, as well as use other languages that interface with C. That being said, wgpu is written in Rust, and it has some convenient Rust bindings that don't have to jump through any hoops. On top of that, I've been enjoying writing in Rust.
Why the bloat when this exist? https://github.com/webgpu-native/webgpu-headers
What are some alternatives?
wgpu-native - Native WebGPU implementation based on wgpu-core
The-Forge - The Forge Cross-Platform Rendering Framework PC Windows, Steamdeck (native), Ray Tracing, macOS / iOS, Android, XBOX, PS4, PS5, Switch, Quest 2
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.
ultimatepp - U++ is a C++ cross-platform rapid application development framework focused on programmer's productivity. It includes a set of libraries (GUI, SQL, Network etc.), and integrated development environment (TheIDE).
vulkan-guide - Introductory guide to vulkan.
DiligentEngine - A modern cross-platform low-level graphics library and rendering framework
Lumos - Cross-Platform C++ 2D/3D game engine
wgpu - Cross-platform, safe, pure-rust graphics api.
misc - Clippings
Wolf Engine - The Wolf is a comprehensive set of C/C++ open source libraries for realtime rendering, realtime streaming and game developing