james7132

5 ms·

1.
by james7132 1y ago
Zig has not hit 1.0 yet, and as recently as a few months ago completely reworked how every form of IO is written. AFAIK, this wasn't a syntax change, but it changed the function signature or type definition of every piece of code that
2.
by james7132 1y ago
Once you understand that a crate is the translation unit in Rust, it doesn't feel as bad. Most medium to large Rust project's will separate out their code into separate crates for both organization and compile time. I've defi
3.
by james7132 1y ago
Not cart, but another maintainer of Bevy here. More traditional game engines tend to be a giant tangle of pointers with much more complex lifetimes than what Rust's borrows would allow. For example, the skeleton used to animate your ch
4.
by james7132 2y ago
I'm running a nanode for a few personal projects and their dashboard was showing something close to 8mbps since 05/29/2024. Went almost 2TB over for the month of June. Nearly 4x'ed my bill. It's not a lot, but it se
5.
by james7132 3y ago
Given the fact that foreign values inherently require the use of unsafe due to not being able to verify anything about the value and it's behavior, yes, it's generally not recommended unless you're looking to write your own s
6.
by james7132 3y ago
A scripting language is an explicit non-goal for first-party support, but there have been tools for using the ECS entirely without Rust types which can be exposed via FFI or embedded languages like Lua. Just search "_by_id" in the
7.
by james7132 3y ago
There is still a game loop that runs every tick. The engine wouldn't work so well if we only responded to inputs as they come in, event pub-sub style. As for ECS overhead, I've made it one of my top priorities to eliminate it wher
8.
by james7132 3y ago
The blog post directly mentions efforts towards a GUI-based editor in the "What's next" section. We can definitely deliver on global illumination in some way, as shown with the irradiance volume support added in this release,
9.
by james7132 3y ago
Fyrox definitely has a better end-to-end feature offering right now, but I personally think Bevy has the stronger ecosystem. Animation support is growing rapidly. I'm one of the two SMEs (subject matter experts) focused on this area, a
10.
by james7132 3y ago
I'm one of the maintainers of Bevy. In my opinion, Godot clearly has a significant lead in many fronts, some moreso than others. A clear few that are lagging behind are: Editor: Godot has one, Bevy does not. Animation support: Godot ha
11.
by james7132 4y ago
We explicitly label easy first issues in our issue tracker: https://github.com/bevyengine/bevy/issues?q=is%3Aissue+is%3A... . These should get you up to speed with the contribution process and, at the very minimum,
12.
by james7132 4y ago
I want to step back a bit. All of these require a more involved and production ready asset system, which we've sorely needed for a few releases now. I'm one of the two developers currently behind our longer term animation efforts,
13.
by james7132 4y ago
> Could you point me the right direction on how to learn about Bevy's render pipeline? The best 10,000ft view that doesn't just point you at the code itself is probably https://bevy-cheatbook.github.io/gpu/
14.
by james7132 4y ago
It's turtles all the way down. You can replace the renderer wholesale, or strip out the top, middle, and/or low level abstractions. You choose how much meat you want stripped off from the bones. It's not that well-documented
15.
by james7132 4y ago
On the contrary, about 50% of my time with Rust is spent throwing shit at the wall and seeing if it works. The great thing is that the compiler will probably tell you that what you're doing is garbage and you might want to consider red
16.
by james7132 4y ago
> And Bevy's coded in Rust! Bevy gains all of Rust's safety, ergonomics, speed; yet it avoids pitfalls with some OSS Rust products: it doesn't overuse lifetimes or macros and is relatively easy to follow. Just uhhh... don&
17.
by james7132 4y ago
Entity as a type is an generational ID. We only support up to 2^32 entities in a World, which makes up the bottom 32 bits. The top 32 bits is the generation. Once we destroy an entity, it's ID is reused, but the generation is increased
18.
by james7132 4y ago
Skeletal animation is supported in the renderer, and there is a (very basic) implementation of an animation player available, but more complex animation (blending, state machines, masking, IK, etc.) is currently still in the design phase ri
19.
by james7132 4y ago
wgpu (the implementation, not the WebGPU standard) does have quite a few of those aforementioned escape hatches on native platforms. Bevy currently doesn't use many of them due to aiming for maximum platform compatibility, but their us
20.
by james7132 4y ago
https://en.wikipedia.org/wiki/Data-oriented_design The intent is to layout structures in memory in a way that is conducive to how it's actually accessed in the physical hardware. For video games, this typically me
21.
by james7132 4y ago
I think it's more in terms of the ergonomics and developer UX. Both Bevy and Flask have a very minimal and surprisingly idiomatic "hello world" example, and both rather seamlessly and progressively introduce concepts, which h
22.
by james7132 4y ago
Most ECS implementations realistically are high-performance in-memory columnar databases, where systems use granular mutation patterns. Hell, the main access pattern is literally a called a Query. It's become quite a meme to call bevy_