RG3D VS bevy

Fyrox is a production-ready engine with extensive documentation and resources that focuses on 2D and 3D rendering. To use the Fyrox engine, add the following line to your Cargo.toml:

rg3d has recently added web support.

Rg3d, written in Rust: https://rg3d.rs

Maybe bevy plus egui? I have never used wasm or bevy though. rg3d apparently supports wasm, too, and includes its own GUI lib (but it's hard to customize the rg3d gui, as far as I can tell).

some game engines https://github.com/PistonDevelopers https://www.libhunt.com/l/rust/topic/game-engine https://github.com/rg3dengine/rg3d https://medium.com/pragmatic-programmers/game-development-with-rust-31147f7b6096

> I hear a few problems with the audio emulation, (mostly clicks that shouldn't be there)

Almost anything WASM+Audio seems to do that in browsers today, unless you're really really careful about what you're doing and leverage multiple threads. I think the issue is mostly around single-thread contexts, where it has to switch between playing audio and other things.

I hit the very same issue myself with Bevy not too long time ago, and tracking this issue which has some further links if you wanna go down a rabbit-hole: https://github.com/bevyengine/bevy/issues/4078

bevy_math also uses glam, re-exported in the prelude: https://github.com/bevyengine/bevy/blob/cc69fdd0c63ea79fda4f...

Since my project is built with Bevy, understanding its core concepts was very important. Bevy's entity-component-system (ECS) architecture makes game development modular and efficient, allowing for highly decoupled systems.

Not a very impressive example yet, it's mainly there for our CI system[1] to ensure that no one accidentally breaks the meshlet feature, but there is an example you can run to get a basic idea of the feature.

You can download Bevy https://github.com/bevyengine/bevy, and run `cargo run --release --examples meshlet --features meshlet`. After it compiles you'll get prompted to download a bunny.meshlet_mesh file. Click the link to download and create and place it in the appropriate folder, and then run the example again.

There's also this video from the Bevy 0.14 release notes demonstrating it, but performance/quality has improved a _lot_ since then: https://bevyengine.org/news/bevy-0-14/many_bunnies.mp4

[1]: https://thebevyflock.github.io/bevy-example-runner

Here, give it a shot - I'm at work so I can't try again right now, but last I did was use claude+context, chatGPT 4o with just chatting, Copilot in Neovim, and Aider w/ claude + uploading all the files as context.

I even went so far as to grab relevant examples from https://github.com/bevyengine/bevy/tree/latest/examples#exam... , adding relevant ones as I saw fit.

It took a long time to get anything that would compile, way longer than just reading + doing, and it was eventually wrong anyway. This is a recurring issue with Rust, and I'd love a workaround since I spend 60+h/week writing it. Probably a skill issue.

https://gist.github.com/jodavaho/8fb042fab33c1aaa95cd67144da...

I was looking through the source code for Bevy's Screen-Space-Ambient-Occlusion (SSAO) implementation and noticed they are using blue noise as well:

https://github.com/bevyengine/bevy/blob/56d559102858d4ce8a5b...

That link takes you to this shadertoy:

https://www.shadertoy.com/view/3tB3z3