wgpu VS bgfx

When I started the project, the existing deno_webgpu crate didn't expose enough to make rendering directly to windows possible. An initial version of that support was added to mainline deno_webgpu recently (see https://github.com/gfx-rs/wgpu/pull/3265), but by then, my own denog_webgpu fork had more features. Hopefully I can at least start using mainline deno_webgpu one day.

There's raw bindings, once upon a time people worked on a safe wrapper but figures that kind of thing needs to be opinionated to a degree that you can just as well write an engine, or go right ahead and implement WebGPU and have something that also runs on DirectX, Metal, etc. It's what bevy uses as backend for its default renderer.

If you are just getting into graphics, also consider checking out wgpu https://github.com/gfx-rs/wgpu the Rust implementation of the WebGPU standard.

Conceptually it's the same as Vulkan it's just a lot less pain in the ass to work with.

Hello everyone, wasn't sure if this is a bug or if I am missing something here but for some reason the following buffer (that worked in wgpu 0.13.1): let some_buffer = device.create_buffer(&wgpu::BufferDescriptor { label: Some("Some Label"), size: (std::mem::size_of::()) as u64, usage: wgpu::BufferUsages::STORAGE | wgpu::BufferUsages::MAP_READ | wgpu::BufferUsages::COPY_DST, mapped_at_creation: false, }); no longer works after upgrading to wgpu 0.14.2 and the error message I receive is: Caused by: In Device::create_buffer note: label = `Some Label` `MAP` usage can only be combined with the opposite `COPY`, requested MAP_READ | COPY_DST | STORAGE This doesn't make sense, since MAP_READ is the opposite of COPY_DST (right?). Also, I saw that this error message is not a new addition in 0.14.2 (in this issue, where it made sense). What am I missing?

I created an issue about this, the solution (and explanation) for the problem can be found there.

https://wgpu.rs seems like the way to go

If all you're looking for is low-level rendering, I'd recommend using wgpu.

the "p5.js" of rust is definetelly nannou. but i wouldn't recommend it for something that is graphics heavy, nannou is great for visualizations, effects, animations and stuff, but for proper 3d rendering and stuff you should go to wgpu (which has a great walkthrough: https://sotrh.github.io/learn-wgpu/), or some opengl binding which there are many of: https://crates.io/keywords/opengl

There is wgpu, which is just graphics.

If you want juste a renderer, you can use BGFX, there is a zig binding that is not a third party.

Take a look at BGFX, sounds like its what you want. Its a cross platform graphics API that is low level like metal or opengl, however it treats opengl, metal, vulkan, etc as backends that u can compile to so you can write your code once and then compile to macos using metal as the backend, compile to web using webgl as the backend, compile for windows using directx as the backend etc etc. Its written in C++ but it has officially supported C bindings so you can use it with C no problem.

bgfx:https://github.com/bkaradzic/bgfx

BGFX

You can have a look at https://github.com/bkaradzic/bgfx

There are still things like BGFX in active development and use. I think the bigger issue is that folks can never really agree on how things should be abstracted for a higher level API.

u/LtJax already mentioned the Sokol library, another somewhat popular cross-platform rendering library is bgfx.

Maybe this

BGFX - Wrapper around low level rendering libraries