Creator of Bevy Engine. Gamedev / Programmer / Artist. Previously Senior Software Engineer at Microsoft.
If you've been curious about getting started with #rust or #opensource, I cannot recommend #bevy highly enough, as a friendly, skilled, welcoming space to learn and make something worthwhile. Go read https://bevyengine.org/learn/contribute/introduction/
The Bevy community has fundamentally changed my life: thank you all <3
Here is a followup to my previous "consolidate #Bevy microblogging" post, which includes our final decision:
https://github.com/bevyengine/bevy/discussions/18302
@zkat @LovesTha I would also happily phrase it as "increasing the odds of having wholesome and insightful conversations with people in many walks of life". I promise I'm not some suit trying to maximize profit. Look at my history and my actions. "Reach" and "audience" are just words that many creative people care about (and creative people are our primary audience).
@woozle @zkat I think the technical and social approach employed by Bluesky is more likely to produce the best outcomes for the most people. I do have concerns about the limited federation and their "public benefit corp" model, but I think the solution they have built is fundamentally better. It isn't perfect yet (and never will be), but as a long time member of the fediverse I can say the same is true here.
This is a hard, but important conversation that I think the #bevy community needs to have.
@_ I'm glad it spoke to you! The first message also provides important context. Its not enough to stop worrying about things you cant or wont fix. You also _should_ worry about things that you can and will fix, otherwise evil will win!
@aras No need to engage with this thought if it doesn't serve you, but we're doing exactly that with Bevy (under the umbrella of the Bevy Foundation). We would happily make space for you there. (Godot is also a good choice, but they're certainly already on your radar)
@aras The lessons you learned working on Unity are still with you, and the ideas you conceived are now in the minds of others. These ideas will persist in the public consciousness and manifest in new and interesting forms. If you still have a passion for building on those ideas, there are still ways to do that. And this time you can choose to invest in something that is less likely to be perverted by financial interests.
The Bevy Foundation is now a 501(c)(3) Public Charity!
This is huge news for us. Read our announcement post to understand why!
Haha I'm glad you liked it! Theres still a chance that I'll port it over to Bevy eventually :)
Today is Bevy's fourth birthday! As always, I've used this as a chance to reflect on the past year and outline my hopes and dreams for the next year of @bevy
I've just published my proposal / status update / working group kickoff document for Bevy's Next Generation Scene / UI System. Curious what you all think!
#Bevy 0.14 is out now!
It features Virtual Geometry, Screen Space Reflections, Depth of Field, Motion Blur, Volumetric Lighting, Filmic Color Grading, Anisotropy, Auto Exposure, ECS Observers and Hooks, Animation Graph, Rounded UI Corners, Computed States, and more!
Really enjoying how much more direct everything is with this approach. At some point I'll also start testing my Scene / UI improvements (bsn format + macro).
For this project, I've built a Bevy integration for Vello: a wgpu based (and therefore Bevy-compatible) vector rendering library for the GPU. I added a VelloRender trait, which can be implemented for Components. Whenever the Component is mutated, it will re-render it to a texture:
This is the entire board setup code. Note that there are no Bundles anywhere. Instead, I just insert the Components I care about and the Required Components are inserted automatically for me. No Bundle nesting / indentation. Flat! Clean! Simple! A concept has been eliminated!
If a component is inserted that has Required Components, those components will automatically be initialized using Default (or a custom constructor if one is provided). This is done efficiently and immediately as part of the insertion (no archetype moves for you ECS nerds).
To start, I've ported it to my Required Components Bevy branch, which allows you to define which ECS components a given component needs. This can be recursive. This enables sorely-needed-in-Bevy "dependency inheritance":
I've started building a "chess like" in #Bevy. I have many ideas in the space, but I've started by building out core concepts so I can experiment. Initially this was just for fun, but I've started using it as a proving ground for some of the Bevy UX improvements I'm working on:
