Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Modify pathfinding cost - DetourNavMeshQuery subclass


I want to modify the costs of the pathfinding algorithm of UE4. I've been looking at the source code and the costs are calculated in the DetourNavMeshQuery class. However, UE 4 doesn't allow me to create a sublcass of DetourNavMeshQuery from File -> Create new C++ class menu. I don't know why.

My question is, Why it doesn't let me create a subclass of DetourNavMeshQuery? And, Is there any other way to do it? Maybe modifying the original class instead of creating a subclass?


Product Version: UE 4.10
more ▼

asked Dec 26 '15 at 08:04 PM in C++ Programming

avatar image

338 16 24 27

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

First issue, DetourNavMeshQuery isn't a class, it's just the header file that contains many classes for Detour queries. I assume though, that the class you want to subclass is dtQueryFilter - which handles path costs for Detour. The reason why it doesn't show up in the editor, is that none of the Recast/Detour library classes are UObject classes (except for the classes that Epic Provides for UE4).

Solution #3 shows you how to subclass dtQueryFilter, but it's probably not your best solution - unless you're invested into implementing your own Recast/Detour solution for UE4. However, the first two solutions might be of use to you.

Solution 1: UE4 Built-in Path Cost (Easy)

E4 uses Navigation Areas to modify the cost of a path. In this case, you can subclass UNavArea and provide a DefaultCost and FixedAreaEnteringCost. For example (you can also subclass a blueprint from NavArea as well):


UCLASS() class MYPROJECT_API UNavArea_Example : public UNavArea_Default { GENERATED_BODY()

     UNavArea_Example(const FObjectInitializer& ObjectInitializer);


UNavArea_Example::UNavArea_Example(const FObjectInitializer& ObjectInitializer) : Super(ObjectInitializer) { DefaultCost = 2.f; FixedAreaEnteringCost = 10.f; } After this, you can then place a Nav Modifier Volume in the level where you desire and set the Area Class.

Solution 2: Modifying DefaultQueryFilter (Moderate)

dd the Navmesh module as a public dependency in your MyProject.build.cs - this will link in any of the Recast/Detour libraries to your project. Subclass ARecastNavMesh in C++ and declare the constructor. Within DefaultEngine.ini, add a section (as shown below), to tell the engine to use our Navmesh Implementation. Create a second class below that, which subclasses FRecastQueryFilter (you can use INavigationQueryFilterInterface, but if you're extending from RecastNavmesh, there's a lot of assumptions in the existing code that will mean a crash, i.e. casting, etc). In this second class, you can override any virtual functions to allow changes in the cost of a path. Next, declare a variable of our second class type, and define the AMyRecastNavMesh constructor. We will then set the filter implementation for the DefaultQueryFilter shared pointer in our constructor. You can see this in the following few classes:


 using UnrealBuildTool;
 public class MyProject : ModuleRules
     public MyProject(TargetInfo Target)
             new string[] {
         PrivateDependencyModuleNames.AddRange(new string[] {  });




 #pragma once
 #include "AI/Navigation/PImplRecastNavMesh.h"
 #include "AI/Navigation/RecastNavMesh.h"
 #include "MyRecastNavMesh.generated.h"
 class MYPROJECT_API FNavFilter_Example : public FRecastQueryFilter
     // Override any functions from INavigationQueryFilterInterface/FRecastQueryFilter here
 class MYPROJECT_API AMyRecastNavMesh : public ARecastNavMesh
     AMyRecastNavMesh(const FObjectInitializer& ObjectInitializer);
     FNavFilter_Example DefaultNavFilter;


 #include "MyProject.h"
 #include "MyRecastNavMesh.h"
 AMyRecastNavMesh::AMyRecastNavMesh(const FObjectInitializer& ObjectInitializer)
     : Super(ObjectInitializer)
     if (DefaultQueryFilter.IsValid())
         DefaultQueryFilter->SetFilterImplementation(dynamic_cast<const INavigationQueryFilterInterface*>(&DefaultNavFilter));

This will mean that every path finding query by default will use this solution - unless a QueryFilter has been chosen on PathFind. If you want to define a query filter, you can take a look at URecastFilter_UseDefaultArea. For example, the Move To node in Behavior Trees allow you to specify a move filter, if none is specified it will use the default (the one we've defined above).

Solution 3: Extending dtQueryFilter (Hard)

f you're looking to make your own solution, you're going to have to put on some pretty high boots. The default NavMesh path finding costs utilise the FRecastQueryFilter class (as mentioned above), which implements INavigationQueryFilterInterface and subclasses dtQueryFilter. As mentioned before, if you're extending from ARecastNavmesh, your filtering will have to extend from FRecastQueryFilter - doing a search of the entire solution for this class will show you why (C style casts galore on INavigationQueryFilterInterface objects to get as a dtQueryFilter).

If you're going to subclass dtQueryFilter, you will have to link the Navmesh module (as shown for our MyProject.build.cs above) to be able to subclass it and make sure to have that class implement INavigationQueryFilterInterface. To create the class, you can just make a new Header file and CPP file, then regenerate the project files.

Unfortuantely, you would then have to throw out ARecastNavmesh, and start implementing your own subclass of ANavigationData in the same fashion that ARecastNavmesh does - hence why this is the hardest option.

Hopefully these solutions are at least insightful or will be of some help! :)

more ▼

answered Dec 29 '15 at 03:53 AM

avatar image

186 4 5 10

avatar image mtrebi Dec 29 '15 at 11:46 AM

Hey, Great answer! Solution #1 really fit my needs. My goal is to create a sort of influence map. I will fill the scene with a grid of small Nav Modifier Volumes and I will update them on runtime. However, I don't know if a lot of Nav Modifier Volumes can be an important downgrade in efficiency. Do you know it?

For this reason I am checking Solution #2. But, which virtual functions can I override to change pathfinding costs? I only see functions to add costs to Nav Areas (like SetAreaCost(uint8 AreaType, float Cost) or SetFixedAreaEnteringCost(uint8 AreaType, float Cost)). Is this nearly the same of what we are doing in Solution #1, isn't it?

Thank you!

avatar image MilkyEngineer Jan 05 '16 at 01:45 AM

Sorry about the late reply! The Nav Modifier volumes should essentially 'bake' the specified Area Class (via Area IDs) into the polys. However, I also expect that the volume will force extra polys to be made to clearly distinguish areas with different area classes (may need clarification on this, but it seems like a sane assumption). This would definitely have an effect on performance as there are more polys to search through, but I envision it wouldn't be too bad - you can profile it by using the stat Navigation command in console and compare the baseline with the added volumes.

Yes, they're similar solutions, just that Solution #2 allows you to write your own algorithm on path building. SetAreaCost is for the duration of the area and SetFixedAreaEnteringCost is for the initial cost of entering the area... imagine if those two are added, you have your total cost of traversing that area. If you're wanting to modify path costs dynamically, you will have to write your own FindPath algorithm that queries the Detour system (like how you've started in your other question).

avatar image mtrebi Apr 21 '16 at 11:10 AM

In my opinion, third approach is the best one. I've successfully implemented it in less than a day. Thanks @MilkyEngineer

avatar image MilkyEngineer Apr 21 '16 at 11:25 PM

Awesome, great work man! Glad to help! :D

avatar image PasteDog Jul 25 '16 at 08:16 AM

Hey, I am trying to achieve the same thing, but I can't get it to work and what I am doing feels wrong ^^

When I make my own ARecastNavmesh, I need to make so many new classes just to use the custom ARecastNavmesh. I don't really want to change the engine code and right now my code is just a mess to work with... Did you change the engine to get it to work or did you use some special casting technique I am not aware off?

Could you please explain a bit how you got it to work? ^^

Thanks in advance,


avatar image mtrebi Jul 25 '16 at 09:37 AM

No, I didn't change the engine code. I have just overridden some classes (yes, there are many...) and of course I had to use some castings. Here is a gist with my navmesh code:

https://gist.github.com/mtrebi/24b7d35a6f90681a7b4209651b06469c --> cpp file https://gist.github.com/mtrebi/9fcda04146b580fb7063f5f948645daa --> header file

Take a look and tell me if you have any doubt. Most of the methods are equal to the unreal source code except a few like getVirtualCost.


avatar image PasteDog Jul 25 '16 at 03:53 PM

I got it to work with your code and help!

I was searching to far I think, thank you very much! :)

avatar image MartinSE Sep 20 '16 at 02:07 PM

Hey mtrebi,

thanks for sharing the source but it seems not to work. The constructor of AMyRecastNavMesh gets called by UClass::CreateDefaultObject(). But the dtQueryFilter_Example::getVirtualCost() function gets never called when searching a path.

I'm using Unreal 4.12

avatar image itzjac Oct 20 '17 at 09:00 AM

Hi mtrebi,

We have working our own version of dtQueryFilter, but we noticed that when setting the SetFilterImplementation in our ARecastNavMesh, the nav modifiers like NavArea_Obstacle (or any other custom implementation) are ignored, seems like the cost is always bypassed to be Default one. Still those marked as NavArea_Null work.

We only care about overriding the getVirtualCost, the rest of dtQueryFilter methods haven't been modified.

Any recommendations where to debug or what other method could be missing in the implementation? Have you previously tested this case before?

Thank you.

avatar image mtrebi Oct 20 '17 at 09:05 AM

Hi Itzjac,

I am sorry but I haven't worked on this for almost two years so I am not able to help you. You have probably already try it but I suggest you to look the source code and debug step by step the construction and execution of the NavMesh and Pathfinding methods.

My apologies and good luck!

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question