Walkabout Navigation Toolkit help thread

#181 Hmm, did you compile in debug mode? I've never run into RTTI problems before. Can you follow the code execution and see which return statement happens? I.e. whether it takes the success branch or the failure branch?

#182 I did compile it to debug to check it out and I really dont know if rtti is causing it or not, my skills are very limited in c++... Im gonna do more testing to see what I can for ya and hope I can assist!! rtti was the one thing that did show when stepping thru it and when I looked it up on microsoft it said that You usually need the /GR option when your code uses dynamic_cast Operator or typeid. I made sure it was enabled in the options but it the prob is I dont have the rtti.cpp file its looking for, so i dont know if its my prob or not?? The game runs great pathfinding and all just cant get the coverpoint to return the size like we talked about, but i will keep looking.....

#183 Hey dan, i did get this error in the following line:

getContainer()->findObjects(box, MarkerObjectType, findCoverCallback, &s);

error:

mSize = CXX0030: Error: expression cannot be evaluated

same for mQuality, mPeekLeft, mPeekRight, mPeekOver, mOccupied..... again dont know if it helps....

in struct CoverSearch......CoverPoint *point; and point = NULL; same errors!!

I dont think its the rtti file but I also dont know enough either...

#184 Ok Dan, step it thru to this, in aiplayer.h

/// Get cover we are moving to.
   CoverPoint *getCover() { return mCoverData.cover; }

mCoverData.cover is giving this error;

mObject = CXX0030: Error: expression cannot be evaluated
mRefCount = CXX0030: Error: expression cannot be evaluated

#185 @Daniel: How do you get Teleporter Link Modes to work?

My teleporters work fine, but when I add a link and rebuild the navmesh it never turns black to my Bots never use it.

Is there a trick ... I have attached a screenshot of what I am trying to do. The green Teleporter is an Entrance and the Red is the exit for that one.

respawn.gobbogamessa.com/screenshots/Teleporter_Link_Mode.png

Maybe I am doing something wrong. 8-{

#186 Donnie: I've never seen that before. When I get time (hopefully tomorrow) I'll double check and see if I can repro your error.

Quinton: Odd. I'll check tomorrow night and make sure they work for me. Your setup seems fine.

#187 @Daniel: Thanks ... they also seem to be ignoring my jump links as well. 8-{

#188 Donnie: I found the error. I hadn't realised that the reference to the found cover point won't survive outside the call to findCover. I'm just testing new code at the moment, and I'll post up a patch to Walkabout tonight. With water :).

EDIT: Quinton: jump and teleport links still seem to work fine for me. No console errors on your end, while building the mesh or otherwise? Do other kinds of links (i.e. drop) work?

#189 Dan: Outstanding, cant wait..... thank you so much!!!

#190 Check your email ;).

#191 @Daniel: I will run some more tests this weekend, I am not seeing any errors on my side. I will double check everything now that I know it is all working as expected.

Thanks

#192 Hey Dan, recompiled.... got 52 errors half are like this;

Error	85	error LNK2005: "public: virtual void __thiscall duDebugDrawTorque::depthMask(bool)" (?depthMask@duDebugDrawTorque@@UAEX_N@Z) already defined in duDebugDrawTorque.obj	C:\SatansFall\Torque3D\My Projects\SatansFall\buildFiles\VisualStudio 2010\projects\navMeshDraw.obj

and half like this;

Error	103	error LNK2005: "public: __thiscall dtQueryFilter::dtQueryFilter(void)" (??0dtQueryFilter@@QAE@XZ) already defined in DetourNavMeshQuery.obj	C:\SatansFall\Torque3D\My Projects\SatansFall\buildFiles\VisualStudio 2010\projects\librecast.lib(DetourNavMeshQuery.obj)

thanks for any help....

#193 looks like duDebugDrawTorque.cpp and navMeshDraw.cpp are the same file?? only diff is this;

inside duDebugDrawTorque.cpp

#include "torqueRecast.h"
#include "duDebugDrawTorque.h"

inside navMeshDraw.cpp

#include "navMeshDraw.h"

header files are the same too, but diff includes... so question;

do i need duDebugDrawTorque.cpp , duDebugDrawTorque.h, and torqueRecast.h or just get rid of navMeshDraw.cpp, navMeshDraw.h, and nav.h??

Ok dan, im gonna remove nav.h and both navMeshDraw from my build, looks like those werent included in the patch......

also getting this;

Error	85	error LNK2005: "public: __thiscall dtQueryFilter::dtQueryFilter(void)" (??0dtQueryFilter@@QAE@XZ) already defined in DetourNavMeshQuery.obj	C:\SatansFall\Torque3D\My Projects\SatansFall\buildFiles\VisualStudio 2010\projects\librecast.lib(DetourNavMeshQuery.obj)

which i think is because the last patch had recast in the walkabout dir.. now its a engine lib if im right??

#194 Compiled no errors... all I did was remove recast directory from the walkabout engine directory and excluded it from my build and removed nav.h and both navMeshDraw from my build and the walkabout engine directory.... now to test!!!

#195 Yep, sorry about that Donnie - those files were removed some time ago in favour of putting the Recast files in Engine/lib. I should make it clearer in patch instructions that some files may need to be removed, rather than just copy/pasting the patch over the existing installation!

#196 Ya thats ok Dan, This is a great addon and thank you for letting me bug you so much.... Plus its great learning for me anyways!!

#197 @Daniel: I think I found the problem. My bots were running at double the speed of the normal player datablock and this seemed to make them run off the platforms.

I had them flying off the walkways in the Factory map ... slowed them down and the Suicide rate has dropped dramatically. 8-}

#198 Right. The current ledge code is fairly dumb - it raycasts downwards in front of the AIPlayer and assumes that if it doesn't find a anything, then it's hanging over a ledge. Obviously if your characters move fast enough, they'll be all the way off the ledge before they think of jumping. Kind of like Wile E. Coyote. If your characters are going really fast you may want to think about modifying that ledge detection code in aiPlayer.cpp.

#199 I have a quick question for you Danny (I hope). I have a pretty large map I'm working with, in addition to several smaller ones. For the larger map I was interested in using more than one NavMesh, and using a simple .setMoveDestination() to navigate between the areas that use a NavMesh. The problem I'm having is I'd like to use the NavMesh class as a $Typemask so that when I cast a ray onMouseDown() I can determine whether or not a 'hit' landed on a NavMesh or not. Given this information, I believe I'd be equipped to handle the rest of the logic :)

Just wondering how I'd go about determining whether or not my mouse click hit a NavMesh or not. It also just dawned on me that without a collision mesh perhaps there is nothing for the raycast to hit. Anyhow, any way of gathering the data could be helpful. Thanks in advance for any help of course.

#200 Hey Jesse. How large is this large map? Unfortunately Walkabout doesn't support pathfinding across different navmeshes. The multiple mesh support is mainly intended to let different character classes navigate differently - you may need to use different navmesh parameters to generate appropriate navigation for large characters, for example, or vehicles.

How large is your large map? With Walkabout's support for tiling navmeshes you should be able to at least try covering the whole map with one mesh.

As for your specific question of raycasting against a mesh - Recast/Detour doesn't provide a way to do this so I haven't implemented it yet. However I'll definitely add it to my to-do list. It would just require a bit of effort on my part. But I do want to have that ability!