awesome-bevy
rfcs
Our great sponsors
awesome-bevy | rfcs | |
---|---|---|
30 | 16 | |
931 | 106 | |
2.5% | 6.6% | |
8.6 | 1.5 | |
3 days ago | 6 days ago | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-bevy
-
Bevy 0.12
Among Bevy contributors (including myself) there is a general hesitance to invest too much time in official learning material that will be obsolete by the next release. Bevy's APIs are beginning to stabilize ... and the appetite (both from users and from Bevy devs) for official material is increasing. The time is coming (soon)!
While you wait, there are a sizeable number of tutorials on YouTube, and we have learning material linked in https://bevyengine.org/assets/#learning as well.
-
Which project do you think is the best at showing what Bevy is capable of?
User code is the same as engine code. It's all Rust. Consequently, Bevy already has a surprisingly rich ecosystem
-
Bevy 0.10
I've summarized a lot of my thoughts in this blog post, but in short: * "The Developer's Engine": most engines are built using multiple languages, with significant abstraction between "user code" and "engine code". Bevy is built with a consistent stack and data model (see the blog post I linked to for details). If you "go to definition" on a Bevy app symbol in your IDE, the underlying engine code will look the same as your app code. You can also swap out basically everything. We have a vibrant plugin ecosystem as a result. These blurred lines also make it way easier for "Bevy app developers" to make direct contributions to the engine. Bevy App developers are Bevy Engine developers, they just don't know it yet. The new Bevy renderer (in 0.6) was also built with this principle in mind. It exposes low, mid, and high level renderer apis in a way that makes it easy to "insert yourself" into the engine. * Fully embraces ECS: No popular engines are currently all-in on ECS (either they have no official support ... or they are half-in half-out). I reflect on some of the benefits we've enjoyed thanks to Bevy ECS in the blog post I linked to. Note that there is a lot of pro and anti ECS hype. Don't just blindly follow dogma and hype trains. ECS isn't one thing and Bevy ECS intentionally blurs the lines between paradigms. * Fully Free and Open Source With No Contracts: Of the popular engines, only Godot is a competitor in this space.
- Katharos tech?!
-
I'm switching from a 2D engine to a 3D one, what should I expect from Bevy?
I would recommend going to bevy's blog post(https://bevyengine.org/news/) since the update lists are the only convenient way I know it find out what features bevy actually has implemented directly. then go over to bevy assets(https://bevyengine.org/assets/) and you can see the community-made plugins to get an idea of the sorts of things people are making available to you. and finally, as a bit of self-promo, I have a youtube series called bevy basics where I got over how bevy does things, like the ECS and systems, moving into more direct use thing like getting user input you can fine it all here www.youtube.com/playlist?list=PL6uRoaCCw7GN_lJxpKS3j-KXuThRiSXc6
-
Bevy 0.9: data oriented game engine built in Rust
I've summarized a lot of my thoughts in this blog post: https://bevyengine.org/news/bevys-first-birthday/#things-i-m...
But in short (slight copy-paste of my generic Bevy pitch):
The Developer's Engine: most engines are built using multiple languages, with significant abstraction between "user code" and "engine code". Bevy is built with a consistent stack and data model (see the blog post I linked to for details). If you "go to definition" on a Bevy app symbol in your IDE, the underlying engine code will look the same as your app code. You can also swap out basically everything. We have a vibrant plugin ecosystem (https://bevyengine.org/assets) as a result. These blurred lines also make it _way_ easier for "Bevy app developers" to make direct contributions to the engine. Bevy App developers _are_ Bevy Engine developers, they just don't know it yet. The new Bevy renderer (in 0.6) was also built with this principle in mind. It exposes low, mid, and high level renderer apis in a way that makes it easy to "insert yourself" into the engine.
Fully embraces ECS: No popular engines are currently all-in on ECS (either they have no official support ... or they are half-in half-out). I reflect on some of the benefits we've enjoyed thanks to Bevy ECS in the blog post I linked to. Note that there is _a lot_ of pro _and_ anti ECS hype. Don't just blindly follow dogma and hype trains. ECS isn't one thing and Bevy ECS intentionally blurs the lines between paradigms.
We can't currently compete with the "big engines" on features, but we are adding features at a rapid (and growing) pace. Bevy was released about a year and a half ago. Most popular engines have been in development for almost 20 years (Godot since 2007, Unity since 2005, Unreal since 1998), so we have plenty of "time" from my perspective.
I'm a huge fan of Godot and used it to build my game High Hat over the course of about 4 years. I also contributed to it every once and awhile. When I was initially building Bevy, Godot's design decisions were always at the top of my mind (and they still are to this day). I love they way they do scenes (and our system draws inspiration from it). We also plan on borrowing their "dogfooding" approach to editor building (the Bevy Editor will be a normal Bevy App).
Bevy still has functionality gaps in most areas. And we still warn developers about stability and missing features in our learning material. But many people are successfully making games with Bevy at this point. Some companies are already successfully building on Bevy for commercial projects. Our modular "everything is a Rust plugin" approach means that most gaps can be filled with 3rd party plugins, and we already have a large ecosystem of people doing that: https://bevyengine.org/assets/.
-
Godot 4 Beta 1
One of the benefits of 4.0 is also the modularity of it with GDExtension. The major parts of the engine (including the physics) can be swapped with replacements without the need to recompile the entire engine. I'd usually say that is a long shot for community run projects, but even Bevy engine has community made extensions for separate physics engines.
https://bevyengine.org/assets/#physics
Forgetting about extensions, though, I see your point and almost agree, but Godot has shown that they will put in the work to improve their project, even if that means removing features like they did with visual scripting. Their physics engine will definitely be rough at first, but based on their past work, I believe they are willing and able to maintain it.
-
Bevy 0.8
Lots of good community-developed networking plugins over in Bevy Assets
-
3D Chess Tutorial from Bevy 0.4.0 to 0.7.0
Hi all! In the Assets tab from the Bevy official website, there is a "Making a Chess Clone in 3D" tutorial to learn Bevy written by guimcaballero. Unfortunately it was written in Bevy 0.4.0 and using bevy_mod_picking 0.3.1.
rfcs
-
I made a fast and ergonomic crate for trait queries. Now, you can easily query for `dyn Trait`!
For some good real-world use cases, check out this thread: https://github.com/bevyengine/rfcs/pull/39
-
Bevy 0.8
I'm the author of the draft Many Worlds RFC. Current plan is to get scheduling sorted out, then pick that work up again.
- Programming a Rogue-Like with Rust
-
Improving upon Entity Component Systems, introducing DG-ECM!
Yep, we do this, it works great! We stole it from hecs and Amethyst before us. There's a nice write-up of the theory in the scheduler rework the team has been working on for the past few months.
-
Bevy 0.7: data oriented game engine built in Rust
I can tell you right now that there’s an entire channel in the Bevy discord server dedicated to making an out of the box api for multiplayer. If you want the current state of it, check out this RFC. https://github.com/bevyengine/rfcs/pull/19 I’m really excited for it when it eventually comes out.
-
Bevy 0.7
I think making it easier for systems to observe the effects of Commands from other systems is a critical missing piece of the Bevy ECS puzzle. "Stageless" is a solid, holistic solution to the problem and we're seeing the community slowly establish consensus on that design. There is already a draft implementation in the works. And I think "stageless" is most likely the solution we will land on.
-
Announcing bevy-egui-kbgp - an improved keyboard and gamepad story for egui in Bevy
Cool! Looks like a nice complement to the RFC about keyboard navigation!
-
Bevy 0.6
This should be fairly feasible: although you'll probably want to wait on (or implement) the dynamic components RFC. The comments above are more to the effect of "writing Rust is easier and more convenient than you might expect".
-
Bevy’s First Birthday: a year of open source Rust game engine development
You will be happy to know that better/updated documentation is planned. It was briefly mentioned as "the new Bevy Book effort" in this paragraph of the blog post and there are a ton more details in this RFC. Your participation would be more than welcome!
-
Placating the borrow checker for systems that depend on a component plus the same component on another entity?
So, several of us have been working on a relations feature for Bevy: first-class support for those sort of "target another entity with a component" patterns that keep cropping up. There's a lot to be done, and it's at a point where it can be chunked out, so if you're interested in helping out come say hi on Discord :)
What are some alternatives?
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
bevy - A refreshingly simple data-driven game engine built in Rust
wgpu-rs - Rust bindings to wgpu native library
morphorm - A UI layout engine written in Rust
kajiya - 💡 Experimental real-time global illumination renderer 🦀
bevy-kajiya - A plugin to use the kajiya renderer with bevy
bevy_ecs_tilemap - A tilemap rendering crate for bevy which is more ECS friendly.
bevy-cheatbook - Unofficial Reference Book for the Bevy Game Engine
bevy_ggrs - Bevy plugin for the GGRS P2P rollback networking library.
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
docs.rs - crates.io documentation generator