Bevy 0.16 is out now! It features GPU-Driven Rendering, Procedural Atmospheric Scattering, Decals, Occlusion Culling, Relationships, Better Spawning, Unified Error Handling, `no_std`, Faster Transform Propagation, and more!
bevyengine.org/news/bevy-0-...
Bevy’s great! If you already know Rust or want to learn Rust, it’s a really fun code-first framework to use
Sometimes you spend so long contributing to a game engine that you forget why you chose that game engine in the first place.
Been spending some time playing with #bevy as a user again and wow it's amazing just how fun it is to use.
(ignore my temp assets lol)
#gamedev #bevyengine #programming
Aaaand I’m sick. That’s okay I didn’t want to be productive today 🙃
Remember kids: document your code changes!
Alright, that was pretty straightforward. This is the reason I try to write detailed PR descriptions. I know my memory would not have served me well had I not left good notes for myself 😅
github.com/bevyengine/b...
I still think it's pretty cool I managed to get this working at all
```rust
// Allows adding two `i32`, `u32`, or `f32` numbers
let reflect_add = add::<i32>
.into_function()
.with_overload(add::<u32>)
.with_overload(add::<f32>);
```
This was merged towards the beginning of the 0.16 cycle back in December so I actually forgot about it up until now lol
My son and wife are sick so it's time to write the release notes for my #bevy PR which adds reflection-based function overloading and variadics (things that don't currently exist natively in #rust) before I too succumb to the illness
github.com/bevyengine/b...
The true Ferris the Crab
My felting abomination that aimed to recreate Ferris but ended up looking like a possessed version of him
How’d I do?
#rust #ferris #felting
You ever start a "small" refactoring task only to discover you've been copying and pasting the same one line across hundreds of files but you can't stop because you're already too deep into it and oh my gosh only a few hundred more files to go I can't turn back I ca
Just put up a new #bevy PR! This one deprecates `clone_value` and replaces it with a new `to_dynamic` method in an effort to make its behavior more explicit
github.com/bevyengine/b...
Actually, we can do `clone_value` -> `to_dynamic` and `clone_dynamic` -> `to_dynamic_***`.
This should allow us to properly deprecate all the replaced methods rather than just removing them outright!
So I think I can try renaming the conflicting methods on the reflection subtraits to things like `to_dynamic_struct`.
That's a little unfortunate because I wanted to make this a non-breaking change.
Alternatively, I could try to find a better name for `clone_value`.
With the `reflect_clone` PR merged, I kinda wanna see if we can deprecate `clone_value` in favor of a more explicitly named method (i.e. one that makes it clear we may return a dynamic type).
I'm thinking `clone_dynamic` but that might run into naming conflicts...
Aw man, now that I have a bit more time to work on stuff, I'm suddenly filled with the desire to start a new gamedev project 😭
I think the next thing I'd like to work on is some more minor type data and/or macro improvements since it would at least be nice if those coincided with the `reflect_clone` PR landing in 0.16 as well
github.com/bevyengine/b...
Okay hopefully that does it (accidentally imported `bevy_reflect` instead of `bevy::reflect` in an example).
Normally, I'd wait for all of CI to pass but my son has an early appointment tomorrow. I enjoyed finally having an hour to work on some #bevy code though 😭
Actually, CI is failing. Hold please!
Aaaand we're done! Just goes to show that sometimes a PR looks scarier to rebase than it actually is 😄
Final commits were super easy: first was just adding a compile fail test (only had conflicts due to a change I made in the first commit) and the second was just a tiny bug fix.
First commit down! Mostly just renames that git couldn't handle. But seems there have been quite a few new `FromType` usages added to the repo since almost a year ago, including a dedicated type data example!
My usual checks are passing, so moving on!
I try not to squash as I like to break my commits into manageable parts with a (somewhat) clear timeline. For large PRs this preference can really be a pain.
Thankfully, this PR only has 3 commits :)
This PR should also fix a mild annoyance of mine that `FromType` should really be given a name more apparently related to "type data"
I've been busy with life the past few months, but I'm hoping to get back into #reflection work for the #bevy game engine.
Tonight I think I'll try and rebase my old PR that allows type data to receive parameters!
Haven't really used social media in a long time, but I'm hoping to try and use this space to document more of my work....
.....we'll see how it goes 😅
Hello, world!
