glium VS learn-wgpu

Which is blocked, waiting for glium to update: https://github.com/glium/glium/pull/2036

https://crates.io/crates/glium (8 months ago - 925 kB)

Hi rustaceans! I glued this prototype together with vtkio and glium. There are more features that are unsupported than supported at this point, but the code is here if you want to check it out: https://github.com/JeffIrwin/skillet

Should i learn glium (https://crates.io/crates/glium)? i have some experience in opengl (C++) and i would like to use the opengl functionality in the Rust ecosystem.

I can recommend https://github.com/glium/glium as a good, safe abstraction. There was a time when I wanted to learn shaders and write complex pipelines with several stages, this library allowed me to learn about the important objects and their responsibilities without having to program the very verbose chunks of code to initialize. I learned the following:

Glium is a Rust-y OpenGL wrapper, and its repository contains a discussion that should give you an idea whether this is what you want to use, as well as some tutorial.

If you don't know C++, don't let that deter you because if you can read Rust, you can read the C++ the author writes in the book. To interact with OpenGL I used glium; translating the C++ code to Rust/glium can be tricky though. The Rust equivalent to the linear algebra library the author uses (GLM) is nalgebra_glm.

Glium and ash provide low level access to different common graphics api's. I'm sure there's a good directx-11/12 bindings as well but I'm unfamiliar with what people use.

I was following the glium tutorials and I thought that I could play around with the code and move most of the logic over into a struct similar to what is done in this wgpu tutorial. However when I try to do that I get an issue saying that a move occurred because my struct didn't implement the copy trait, although neither did the tutorial on wgpu, so I am a bit confused as to why it works in the wgpu code and not in my code.

glium: https://github.com/glium/glium/tree/master/book wgpu: https://sotrh.github.io/learn-wgpu/

A nice introduction (+ a lot more) can be found here: https://sotrh.github.io/learn-wgpu/#what-is-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

And here's the tutorial: https://sotrh.github.io/learn-wgpu/

baryon is a lightweight toy renderer for prototyping 3D applications in Rust. It uses wgpu to render 3D elements, hecs for an ECS system (to make a scene with “entities” like 3D models), and winit for handling cross-platform window management (just like the wgpu tutorial). It also allows for setting different “render passes”, like a Phong (”cartoony”/fast) vs PBR (”realistic”) pass.

I creted this project while learning from this awesome tutorial which I highly recommend. I also took inspiration for the minimal web ui from this repository.

⚠️ This tutorial assumes you’ve followed and completed the “Learn wgpu” tutorial. You could also use my repo here as a starting point - but it will require Rust and Trunk setup in your local dev environment. You can also checkout the final code here for reference.

If you do know Rust and know what to pick from, but want to be at bleeding edge and have the best Rust centric graphics libraries can offer, try wgpu which is an implementation of WebGPU. There's a tutorial on how to get started too.

Hello! So far am I following this guide for WGPU/Rust: sotrh/learn-wgpu. I made it to the depth buffer before I wanted to use what I had learned to make my own project. It has been going pretty well, with no major hiccups, however, I am having issues with resizing.