Asymmetric PathNNConstraints

General
1

Hey there,

if I understand the docs correctly (PathNNConstraint - A* Pathfinding Project), setting constraints via PathNNConstraints always applies to both, the start and end node.

However, I have a use case where I want the constraints the differ for the start and end node.

E.g.: The start node should always have tag 1, while the end node always should have tag 2.

Is this possible or is there another feature to make this work? :slight_smile:

2

Hi

If you inherit from the PathNNConstraint class it will call the SetStart function after the start node has been queried and it is about to query for the end node.

1 Like
3

Thank you for the prompt response :slight_smile:
This gives me a good starting point.