Recast/Detour VS specs

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.

The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion

Instead, I'm using now the specs Library. It's a pure ECS library and much less powerful, without any visualization capabilities, but its works for me :)

writing an ECS is defined a challenging project, no matter the language or if you're a beginner. although it is entirely possible to write one in Rust, check out specs and bevy_ecs for examples.

specs

The official 3d rendering client uses a custom engine called Voxygen. They use Specs for logic.

Rust has a delightful ECS library, specs, that I absolutely love. It has safe multi-threaded execution built right in, which is fantastic for the pretty parallelizable work I was doing. Concurrency in C++ is nasty business on the best of days, and I've run into so many nasty bugs with the custom system I've had to build out to fit the web's weird threading model.

Man, this Specs [0] library is so strange to me, coming from a Unity background. Is there some sort of comparison as to why one way is better than the other?

[0] https://specs.amethyst.rs/

Hi everyone - I just picked up one of my long-unfinished side project built with Rust and would like to show it to you here. It's a clone of the famous(?) Winterbells game. It's written entirely in Rust and uses OpenGL and an entity-component-system architecture ([the `specs` crate](https://crates.io/crates/specs)) (still learning), no game engine.

Wait did the person at your company write specs or something else because they weren't pleased with it? I don't know much about amethyst and vaguely know about entity component systems but I watched a talk on someone making a game with amethyst and was pretty impressed -- it looked thoroughly approachable and I do not doubt the performance is there (since the whole reason you do ECS is performance).