StationIapetus VS wgpu-rs

Check Station Iapetus, "commercial project that will eventually be released in Steam".

Besides being clear and easy to use, one of its popular features is the scene editor, which provides a scene preview as demonstrated in this example:

StationIapetus is also big enough.

Thanks! I do have two pretty big games written with the engine - https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rusty-shooter . I've started writing them because it is impossible to get right feature set, without a game that uses it.

Thanks! Huge breaking changes in the API are rare, I'm trying to design the API to be good from the first try. I have three dependent projects, so every breaking change forces me to fix all of those. Usually I need an hour or so to make it compile again, even on large projects like this.

Hello! I've been working on this project for almost 3 months already and it has some decent progress I want to share with the community. The game is about task-force agent sent to the space station to investigate why connection with the station was lost. The plot is incomplete, it is a bit early for writing it entirely, because I'm just "whiteboxing" everything for now, and working on mechanics of the game. Here are the project links: https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rg3d .

Station Iapetus - https://github.com/mrDIMAS/StationIapetus

You could start with one of examples from wgpu and tinker with it to see if that's your thing. Ie. copy hello-triangle and add more triangles / make them move, etc.

wgpu-rs (https://github.com/gfx-rs/wgpu-rs) is probably closer to what you're looking for, it's a "high level wrapper" over wgpu-core (Which implements "WebGPU", an upcoming browser API for graphics using gfx-rs, and AIUI "implements" means this is what a browser might use to actually call a graphics API when javascript uses webGPU, although if you're compiling for wasm it could just call the browser APIs). It can run natively, ignore the fact it has "Web" in the name

rust-gpu) is used for compiling a compute shader written in Rust to SPIR-V. wgpu-rs is used natively for running the GPU computation.

For web assembly there is the unofficial bevy_webgl2 plugin. Official bevy web assembly support would probably use the wgpu webgl backend, which still needs some work, and is currently untested in bevy.

We let wgpu https://github.com/gfx-rs/wgpu-rs handle our graphics backend abstraction, so our OpenGL support will come whenever they implement and release it. Currently, it seems to be a WIP.

It's the same thing, the Rust implementation is just called[wgpu](https://wgpu.rs/)

Same as with GLSL, isn't it? What we do in wgpu-rs examples, and that's something I expect to see more widely, is having an integration test that just parses all the WGSL in the project and reports errors. Ideally though, we'd have a set of IDE plugins to do the parsing and report errors right where you type the code. We'd appreciate any help to get these started!

Also you could use an existing cross-platform graphics library, e.g. wgpu-rs. It supports Vulkan, Metal, DirectX, OpenGL and WebGPU. Oh and it seems to allow switching backends at compile-time via the WGPU_BACKEND environment variable, so maybe check out how they're doing it.