Recast/Detour VS rust-gpu

RecastNavigation

Detour is open source (zlib) so anyone has access to a proven RVO implementation. I believe Unreal and Unity still use Recast/Detour for navmesh and avoidance, but it looks like Godot cooked up their own.

https://github.com/recastnavigation/recastnavigation There is also a library called Yuka that is web based that can generate navmeshes i think: https://mugen87.github.io/yuka/docs/NavMesh.html

Hi, wanted to post about my rust project. I created Rust Lang bindings to the famous https://github.com/recastnavigation/recastnavigation . My library, Divert, currently provides the resources to interact with the Detour, 3d mesh path finding, capabilities of Recast Navigation. In the future, I hope to implement bindings for the Recast side of RecastNavigation which facilitates generating navigation meshes from input geometry to be used by detour. Most of my hobby work revolves around reverse engineering video games, so I needed the capabilities of Detour for my Rust program to navigate in game geometry. I would characterize myself as quite new to Rust still, so constructive criticism is highly welcome. I imagine, I did some really weird stuff while designing this crate, and I bet someone can let me know here ;)

Recast & Detour for navigation meshes (though Rust does have Detour bindings)

For path finding there is at least https://github.com/recastnavigation/recastnavigation

Recast is used in Unreal and many other games.

https://github.com/recastnavigation/recastnavigation Would be.

Sounds cool, but this requires yet another language to learn[0]. As someone who only has limited knowledge in this space, could someone tell me how comparable is the compute functionality of rust-gpu[1], where I can just write rust?

[0] https://github.com/Hugobros3/shady#language-syntax

[1] https://github.com/EmbarkStudios/rust-gpu

I don't do anything related to data science, but I feel like doing it in Rust would be nice.

You get operator overloading, so you can have ergonomic matrix operations that are typed also. Processing data on the CPU is fast, and crates like https://github.com/EmbarkStudios/rust-gpu make it very ergonomic to leverage the GPU.

I like this library for creating typed coordinate spaces for graphics programming (https://github.com/servo/euclid), I imagine something similar could be done to create refined types for matrices so you don't do matrix multiplication matrices of invalid sizes

Do you mean rust-gpu?

And https://github.com/EmbarkStudios/rust-gpu/tree/main/examples with the wgpu runner (here it runs the compute shader)

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

The examples in the rust-gpu repository are a good place to start

There's another project that's similar that's being used by an actual game company: https://github.com/EmbarkStudios/rust-gpu

They see specific advantages here that would outweigh that negative. It's not my space (I play games, but know next to nothing about graphics programming), but there's at least one argument in the other direction.

Could this approach work for compute shaders (GPGPU) as well? So far, I think https://github.com/EmbarkStudios/rust-gpu is the state of the art in that area, but it adds a specific Rust compiler backend for generating SPIR-V rather than leaving that up to the driver. That seems more complicated than it needs to be... but maybe it has advantages too? Thoughts?

https://github.com/embarkstudios/rust-gpu Allows you to create shaders (kernals) in Rust.

Also Embark Studios (formers DICE people) is doing a lot of work with Rust, all open source like Rust GPU https://github.com/EmbarkStudios/rust-gpu