RG3D VS arewegameyet

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

Why Rust? Because I wanted to use far more concurrency than usually seen in games to overcome the fundamental performance problem in metaverse clients. The graphics stack works well enough to do this.[1] But it needs to get faster and do a few more things. Basically, I need three.js for Rust. I sort of have it, but the Rust crate has been abandoned, has bugs, and now I have to maintain it.

For a while, there was much enthusiasm for Rust game dev.[2] But it kind of ran down.

[1] https://video.hardlimit.com/w/7usCE3v2RrWK6nuoSr4NHJ

[2] https://arewegameyet.rs

arewegameyet

"While the ecosystem is still very young, you can find enough libraries and game engines to sink your teeth into doing some slightly experimental gamedev."

For practical uses of Rust? Whatever you want to program. People use Rust for game development, GUIs, web dev, and more. Anything where abstraction, speed, concurrency, memory safety, etc. are important, Rust will probably be a good fit.

Are we game yet? "Almost. We have the blocks, bring your own glue"

Not seeing anything else that's close to photo realistic. I'm hitting the tough bugs first all too often. More than half my time has been spent on ecosystem problems.

I also know of https://arewegameyet.rs/