kajiya VS rfcs

There's also Kajiya, though it's very new and works on a limited range of GPUs.

I don't know how major they are considered, but Embark Studios is doing quite a bit of Rust in the open source space, most notably (IMO) rust-gpu and kajiya

I'm also aware of https://github.com/EmbarkStudios/kajiya/, which has a pretty neat documentation:

> You can't even achieve PS2-era graphics with Rust right now

That's just straight up false:

https://github.com/EmbarkStudios/kajiya

There you go

What do you think of the Kajiya renderer from Embark Studios. Is there a desire from the core developers to improve the plugin and maybe use as a default renderer?

A good example of what you can do with rust-gpu is kajiya from rust-gpu's creators. You'll notice that every shaders are not using complex enum, traits or even vector (no_std) from Rust.

I know nothing about game engines/programming/design, but I have recently read about https://github.com/EmbarkStudios/kajiya and wondered if bevy could benefit from it?

This release constitutes a massive rendering API rework. You can think of it more as a foundation that makes it easier to implement better rendering features in the future.

If you check the release notes[0], you'll see HDR/Bloom support was dropped at the last minute, and several other major rendering features are still pending implementation.

The great part about Bevy is that it's modular, so you can swap out the renderer if you like. There's already several people using Bevy with Embark's kajiya renderer[1].

[0] https://bevyengine.org/news/bevy-0-6/#what-s-next-for-bevy

[1] https://github.com/EmbarkStudios/kajiya

For some good real-world use cases, check out this thread: https://github.com/bevyengine/rfcs/pull/39

I'm the author of the draft Many Worlds RFC. Current plan is to get scheduling sorted out, then pick that work up again.

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.

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.

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.

Cool! Looks like a nice complement to the RFC about keyboard navigation!

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".

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!

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 :)