kajiya VS rapier

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

Ok, so this uses https://rapier.rs/ which is very cool

Rapier, alongside https://nalgebra.org/ (which it uses underneath) has seriously good documentation and some advanced features like cross-platform determinism (something made hard by the way floating point differs between platforms)

Code examples: see examples2d, examples3d-f64 and examples3d directories

What are the pros and cons compared to something like Rapier? When should one use Bevy XPBD instead of Rapier, or vice versa?

Still using Rust in a browser-based multiplayer party game I'm working on! I'm using Actix Web for the backend and rapier2d to handle my game's physics. I'm looking to make some more connections amongst the developer / gaming community through my game down the line.

I have noticed that Rapier 0.17 contains a RopeJoint struct, which constrains maximum distance between two dynamic bodies. It doesn't seem to have found its way into bevy_rapier3d yet so I haven't understood whether it supports (half of) my use case, and looking at the code (https://github.com/dimforge/rapier/blob/master/src/dynamics/joint/rope_joint.rs) I really cannot see how it is actually implemented and how I could extend it to also set a minimum distance, but this may be a place to start.

I was also frustrated with the kcc, so I opened a PR that fixes most of my issues: https://github.com/dimforge/rapier/pull/446

Likewise, see the js bindings of Rapier.

Maybe check out how Rapier does it. Rapier is likely the most advanced physics engine in Rust. (Though Embark Studios is doing some crazy stuff with ML physics.)

rapier