wgpu VS glow

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.

You can absolutely do WebGL. glow is a good place if you want to do the webgl stuff yourself. With wgpu you can as well, though it is mostly targeted to the upcoming WebGPU standard. I have seen many crates that are capable of gltf loading, but I haven't used any yet. Hence I can't reall recommend one. But gltf capability does not really have anything to do with rust. As long as you can read a file and translate it to your engines scene/entity structure, I don't see why it shouldn't be possible to load gltf files.

Most of it is written in Rust and compiles to Wasm with WebGL/OpenGL bindings via glow. The settings panel is written in Elm and the whole project is compiled with Nix. There’s also a very basic native desktop app. I haven’t seen many examples of a complete setup like this, so hopefully this can serve as a template for anyone trying out a similar stack.

If you want to target desktop, mobile and/or web: https://github.com/grovesNL/glow

A/B Street, which comprises a UI library, lots of data import pipelines, and traffic simulation. 100k LoC, the only unafe is to make system calls through glow

https://github.com/grovesNL/glow is used by wgpu for its OpenGL ES / WebGL backend

By the way, nowadays many projects use glow instead of glutin because of.. I think it's because glow works on wasm, in the web (as webgl).

But then you have the only example which is more platform handling than anything else.

But what glow actually does is highlighted on lines 66 to 123. This section is filled with gl.some_function() calls, which is the same on every platform.