rust-ecosystem VS wg

It looks like they're still actively maintaining a bunch of rust crates, and they're still developing Wim (their blobby Roblox competitor written in rust).

They have pulled back from the rust ecosystem quite a bit though since repi (their former CTO) left shortly after The Finals released. They stopped all their FOSS sponsorships, and there was [this PR](https://github.com/EmbarkStudios/rust-ecosystem/commit/61f0e...) which definitely doesn't inspire confidence.

Notice the (2021).

Read the change in which Embark's CTO backs off from Rust.[1] They were building their own rendering ecosystem, but seem to have backed off from that.

The mainstream Rust 3D ecosystem just isn't good enough yet. I've brought this up before.

The core crate for 3D is WGPU. This is a layer which tries to cover Vulkan, Metal, OpenGL, DX12, Android, and WebGPU targets. It works, but there are performance compromises to support all those different targets. Supporting web and Android means giving up some parallelism on desktop.

The main alternative to WGPU is Vulkano, and MoltenVK, which is an adapter for Apple's Metal. (Apple just had to Think Different, which is why many games are not ported to MacOS.) It's OK, but it's really just a subset of Vulkan on top. Same parallelism problem, although not for any essential reason.

All those offer a Vulkan-type API, which is rather low level. The caller has to manage GPU memory and scheduling. For that, there's Bevy, which is a whole game engine framework. Good work has been done in Bevy, but it's a framework, so you do it their way or not at all. There's Rend3, which is just a crate to manage memory and scheduling. I use that. It's been abandoned. I may have to take up maintaining that.

Nobody is pushing these towards maximum performance and quality. Nobody has a good modern big-world 3D shooter on these stacks.

All this stuff works fine if you're doing simple scenes. If you're pushing towards, say, the level of a 10 year old AAA title, it's not there. Modern Unreal Engine, not even close.

Not enough money behind it.

[1] https://github.com/EmbarkStudios/rust-ecosystem/commit/61f0e...

These are issues that I'm aware of that are "tracking" the status of Rust on console:

* <https://github.com/rust-gamedev/wg/issues/90>

* <https://github.com/EmbarkStudios/rust-ecosystem/issues/18>

I say scare quote tracking because due to the nature of console NDAs it's unlikely you'll see much if any useful details in an open public forum.

The issues aren't dissimilar to those facing Godot (although it has the benefit it's able to use existing C++ compilers) and the project has previously outlined some of the issues involved:

* <https://docs.godotengine.org/en/4.0/tutorials/platform/conso...>

* <https://godotengine.org/article/godot-consoles-all-you-need-...>

The current "solution" seems to be console-related development activity occurring via the recently established W4 Games (https://w4games.com/2023/02/28/godot-support-for-consoles-is...) but that's obviously never going to be openly developed without console platform approval (same as any other game engine).

Some companies are betting on Rust, like Embark Studio (though I'm not sure their next big game, ARC Raiders, is actually fully based on Rust... but it will come !)

Next generation uses Rust https://github.com/EmbarkStudios/rust-ecosystem

These are issues that I'm aware of that are "tracking" the status of Rust on console:

* <https://github.com/rust-gamedev/wg/issues/90>

* <https://github.com/EmbarkStudios/rust-ecosystem/issues/18>

I say scare quote tracking because due to the nature of console NDAs it's unlikely you'll see much if any useful details in an open public forum.

The issues aren't dissimilar to those facing Godot (although it has the benefit it's able to use existing C++ compilers) and the project has previously outlined some of the issues involved:

* <https://docs.godotengine.org/en/4.0/tutorials/platform/conso...>

* <https://godotengine.org/article/godot-consoles-all-you-need-...>

The current "solution" seems to be console-related development activity occurring via the recently established W4 Games (https://w4games.com/2023/02/28/godot-support-for-consoles-is...) but that's obviously never going to be openly developed without console platform approval (same as any other game engine).

If as me (I am not using Rust to make commercial games yet, though), you accept that you won't be attempting to port itself to a console and let some third-party do it for you, you'll discover that there is already some discussion about it, people already managed to get it working on major consoles, but so far there are no publisher or other company officially doing port of Rust games.

A fast, Rust, JPEG 2000 decoder. Details here. The available options have either performance, cost, or licensing problems. I just need the decode part for classic JPEG 2000 at multi-resolution. Don't need tiles or video.

> Game developers should be investing their time in open tooling without contracts or restrictive licensing

Unfortunately, this is not possible in consoles, because of issues with NDA. Even Bevy can't have an open licensing there: https://github.com/rust-gamedev/wg/issues/90 (Godot also can't: https://docs.godotengine.org/en/stable/tutorials/platform/co...)

I expect that Bevy ports to consoles will take a cut of sales rather than a flat fee :(

rust-game-ports is now officially supported by the Rust GameDev WG. By having this repo on neutral ground, we want to invite the Rust gamedev community to contribute additional game examples to this bundle, so we may collectively expand our comparison-matrix of similar/same games made in different engines. A bit like the realworld app taken one step further.

There is a Github Discussion for this form: https://github.com/rust-gamedev/wg/discussions/121

https://github.com/rust-gamedev/wg/issues/90 ("Rust on Consoles")