bevy_game_template VS kajiya

Thanks also to bevy_game_template, without which Foxtrot would not be possible in the first place :) And thanks to /u/PhaestusFox, who made a video about the template

Seems like you are right - it really is a build.rs problem. I'm using the build.rs from this template, which only sets the icon, and when I remove it it really know not to rebuild when I touch a non-source file, but apparently even if I replace it with a build.rs that only containers an empty main function it still rebuilds when I touch the assets.

Should starting from bevy_game_template and not adding any weird dependencies be enough to ensure that?

From my own experience, I've walked through the Bevy tutorial a few times without getting a ton of traction. On this iteration I'm working harder to explore the examples, of which there are many. I'm playing with this bevy game template to learn more about how a full project might be implemented. I'm learning to approach gamedev with ECS entities as a first-class citizen, which is a concept I haven't really explored before.

Have you seen NiklasEi's template? It's more focused on the assorted project setup (like CI), but it may help you still <3

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