Hi @Dain_Torson , I understand the Dynamic Collision Listener only fires (a callback) if there is an obstacle along the calculated path. Just to be clear, (i do not mean to be redundant), when you run the Schedule Path Finding task, are you saying there is not code to remove any previously found path? If not, then how is the cache being managed? Are you saying it just grows and grows for the duration of the level’s existence?
It doesn’t make sense, why in the video, he would state that if the Dynamic Collision Listener fires, you must re-run the Schedule Path Finding task again to get a new path, if that did not clear some cache (previously enumerated path).
-Erol