bevy_egui VS kajiya

I've heard that bevy_egui is good.

fwiw, I've had a blast using https://github.com/mvlabat/bevy_egui - you might find it easier as well.

Hi! Can't help but post a link to my plugin here: https://github.com/mvlabat/bevy_egui

Afaik, there are no plans to upstream Egui integration to Bevy, but if anyone needs an immediate mode UI, this plugin does the job (and it already supports Bevy 0.9).

It's much more mature than our UI solution (which is bevy_egui exists and is wildly popular). And for things like calculators and todo lists, there's no complex internal logic where you really want the tools that Bevy provides.

Oh, forgot to mention, egui is used for most of the gui features via bevy_egui, it's pretty nice, very easy to use (I've been using other immediate gui before).

For a GUI, you might consider egui which has an integration for bevy.

Bevy engine has also an editor UI plan like godot,but it's just the beginning. There is a Egui integration(bevy_egui) for the Bevy game engine which you can try.

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