I tried constructing the navmesh like it’s done in that test, but when I enter my scenegraph into the file and then build the RecastConfigbuilder and all that stuff (like it is done in the Test file linked above), then the type system gives me the finger, because for example the GeometryProviderBuilder needs a Geometry, not a Spatial.
(I am not sure I can post code since this is my thesis project. Otherwise I would. But it looks almost completely like the RecastTest,java (which I obviously cite), so I think that can be taken as a refefrence)
At the moment, I do not quite understand how to give the objects of the correct datatype to the classes and methods used in the RecastTest example.
Thats why I wanted to use jme3-recast4j, because I figured it would be easier. If anyone can tell me what mistake I am making in using recast4j, it would be distinctly appreciated AND would allow me to go on without the jme3-recast4j thingy.
Recast4j has its own binary exporter where you can write mesh data or polymesh to disk quickly and efficiently. That test does just that.
I won’t go into how to use the library since it’s not been released by mefisto.
I could show you how to use recast4j or even release a tutorial for it (already wrote one for jme-recast4j) but Id rather give mefisto time to finish his project at his own pace and release it when or if he wants to.
You can implement recast4j by using the test cases that are found inside each topic on the recast4j site. I just don’t have the time or desire to go thorough it because its a very complicated library.