miniquad VS bevy_webgl2

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.

There was a rust game jam in September 2021 and some games are playable in the browser. In that game jam the most used game engine was the bevy game engine. But most of the games made in bevy were not made playable in the browser, the ones that were playable in the browser used a third-party bevy plugin called bevy_webgl2. However now bevy has been updated to version 0.6 that has new built in WASM support, so there seems to be no need for bevy_webgl2. Targeting WASM with bevy might mean that not all features of the engine are available, so you need to limit the game’s features used to the ones that are compatible with WASM.

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.

Thanks to bevy_webgl2, this is actually very straightforward. I just need to add the plugin WebGL2Plugin and disable the default features of Bevy to only enable the one available on Wasm.

Bevy has bevy_webgl2, which is supposed to enable a way to compile bevy for wasm and consequently run in a browser.