com.unity.multiplayer.docs VS bevy

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

Ah yeah pipeline compilation is a very non-trivial problem[1]. Unreal is also struggling with this a lot. I hear you that it's an issue.

The Bevy issue you want to follow is https://github.com/bevyengine/bevy/issues/10871.

[1]: https://therealmjp.github.io/posts/shader-permutations-part1 + https://therealmjp.github.io/posts/shader-permutations-part2

It's partly because WebGPU has very conservative default texture limits so that they can support old mobile devices, and partly it's a problem for engines that may have a bunch of different bindings and have increasingly hacky workarounds to compile different variants with only the enabled features so that you don't blow past texture limits.

For an idea of bevy's default view and PBR material bidnings, see:

* https://github.com/bevyengine/bevy/blob/main/crates/bevy_pbr...

* https://github.com/bevyengine/bevy/blob/main/crates/bevy_pbr...

Switched to Bevy engine

4. Bevy Bevy is a data-driven game engine built in Rust. If you’re curious about game development, Bevy is a great way to explore how Rust can be used for building games. It’s still in the early stages of development.

> Isn't this obviously true?

To an extent sure, but we’re talking about low level micro-optimizations. Games don’t animate individual pixels. I don’t think animating 1000 things per frame gonna saturate a CPU core doing these computations, which means the code doing that is not actually performance critical.

> Got a bit lost here: games?

I searched the internets for “Bevy Engine” and found this web site https://bevyengine.org/ which says “game engine”. I wonder is there another Bevy unrelated to games?

> 3.84 GB/second

In modern games none of that bandwidth is processed on CPU. Games use GPU for that, which don’t run Rust.

> there's a weak claim that all performant data structures in Rust must use unsafe code

Weak claim? Look at the source code of data structures implemented by Rust standard library. You will find unsafe code everywhere. When you need custom data structures instead of merely using the standard ones you will have to do the same, because safe Rust is fundamentally limited in that regard.

It's been mentioned a couple of times in this thread, but Bevy also has an implementation of Nanite's ideas (sometimes called Virtual Geometry). I'm the author of that, happy to answer questions :)

As for this project, Scthe did a great job! I've been talking with them about several parts of the process, culminating in some improvements to Bevy's code (https://github.com/bevyengine/bevy/pull/15023). Always happy to see more people working on this, Nanite has a ton of cool ideas.

My recent experiences with Rust and Bevy convinced me to write this blog article to share my newfound learnings of game development.

Not at this time, no. You can read more here: https://github.com/bevyengine/bevy/issues/11969