Horde3D

It really is fantastic stuff from Mikko Mononen (one of the AI guys from Crytek/Crisis).

You can find recast (navmesh library) at http://code.google.com/p/recastnavigation/

Ignore the horrible colouring of the navmesh. I've got my renderstates in a mess right now

I always enjoy seeing your progress. Even that simple screenshot looks cool!

looking sweet, have you thought about making a tutorial for this?

_________________
Paul

Hmm, a tutorial is a bit redundant really. Recast comes with a really good demo app that has all the code you need. Plus my implentation is very much built around my engine. I just reimplemented Recasts sample demo grabbing the data out of the Horde mesh, after Nicolas explained how to access the vertex/face data. It really is just about a cut and paste job. My biggest hurdle once I got the mesh stuff working has been integrating the paths in my component system, which wouldnt get you very far.

On the upside, I took a video: http://tinyurl.com/mdcgsx

i understand.

was the navmesh generated before h3d was initialized, or have you found a way to upload custom geometry to the engine?

_________________
Paul

No, unfortunately I cant load the navmesh unless the geometry resource is attached to a node. But I can load it, read the data, then remove it from the scene straight away. So I did that. At some point I might add a method to save out the navmesh once its been generated (takes maybe a second or two to generate a large mesh). My plan is to have dynamic generation though, because I want building placement on the fly.

But hey, I can live with static navmesh for my test environment for the moment. Plus it looks kind of funky

Updated the video with a more complete navpath display (got my GL prims wrong). Added red endpoint for debugging the paths. Now to fix the string pulling!!!

Yep Mikko's work is really going to make open source games allot smarter, not only that but some of the algorithms did not have an open source implementation. It is a big step forward, no doubt.