miniquad VS gdnative

You also have Miniquad which is a very cool minimal graphics project. It has almost zero dependencies (only system ones), and compiles under 2 seconds to give you a window with OpenGL on all platforms including mobile very easily. It has a wrapper graphics API but it doesn't try to be modeled after OpenGL at all (after all it might support Metal in the future), so it's gonna be quite different doing your project in it, but it's still the same kind of low level graphics.

Theirs also https://github.com/asny/three-d or https://github.com/not-fl3/miniquad. Or lower level ones like WGPU or GLOW.

In that same rust game jam the second most used engine was macroquad, which was used by 3 games, two of which are playable in the browser. Macroquad is a cross-platform game library inspired by raylib. Macroquad is built on top of miniquad. I think macroquad is a bit more approachable than bevy since macroquad doesn't impose an ECS and tries to be minimal with its features so they are available in all of the platforms it targets.

(miniquad is a lower level lib https://github.com/not-fl3/miniquad - both miniquad and good-web-game is built on top of it)

Nice! Would love to see the same thing done with miniquad though.

Looks like it won't work out of the box, unfortunately, since {macro,mini}quad doesn't support a custom X11 parent window :-(

But I've opened an issue upstream to track functionality in the renderer that would allow this[1].

[1]: https://github.com/not-fl3/miniquad/issues/250

Single command deploy for both WASM and Android build instructions

Hi, I am using macroquad. There is an issue with `window_reizable` property. In my archlinux, this property doesn't work when set to `false`. Then I saw here that it is used only for windows. If I am correct, could you let me know the reason for this? Thanks

If you want to write your own shaders: miniquad.

It's a little less standard use, but Godot has been used to build application guis, which could be paired with rust bindings to implement app logic. I can't speak to reproducibility/scalability, but Godot's ui is extremely solid, and I'd probably choose that over Bevy until Bevy's ui progress matures.

Adding onto this, I successfully written a game in Godot using gdnative / gdext. I started with a split approach using gdscript and rust for CPU intensive but found that the API layer was slow at transferring large amounts of data (serialization?). I ended up rewriting it in all rust and it worked like a charm. I was able to target native and web assembly, the web assembly was much slower but worked on the browser.

Check this: https://github.com/tomuxmon/bevy_roguelike if you are still into bevy. Scheduling is a bit bork and I have not found time to port it to latest bevy. But most of the systems should work fine(if used on latest bevy). But again. If you want faster result go with something like Godot. In fact, just go with Godot. It is mature, easy to start, no lock in(free and MIT license), a lot of learning material. Also with Godot you can also use Rust https://godot-rust.github.io/. Ditch Unity (do not have time to explain 😅). Have fun!

Bevy Godot-Rust

> Same for Godot.

While likely true that it's "Unlikely to ever be as supported" as the 4 officially supported languages[0] ("GDScript, C#, and, via its GDExtension technology, C and C++."), Godot's GDExtension technology is specifically intended for use in adding support for other languages.

The most relevant tracking issue for Rust is presumably:

* <https://github.com/godot-rust/gdnative/issues/824>

Which links to:

* <https://github.com/godot-rust/gdextension>

[0] https://docs.godotengine.org/en/4.0/getting_started/step_by_...

...Godot v3.x has Rust support via godot-rust and Godot v4.0 is released as of this month?

I was curious, and looked it up. Nothing built in, but there's an interesting project that works with godot: https://godot-rust.github.io/

There's people working on it: https://godot-rust.github.io/