Two objects with Pathfinding not working correctly. Bug?

Ashley, Thanks for the quick answer. Then why is it working in C2?

And what should I do if I need two pathfinding objects with different obstacles?

PS: Sorry, I logged a bug before I saw your answer here.

Ashley, It definitely works in C2. I made that project in C2, tested to make sure it works, then opened it in C3.

Is there any workaround to use two obstacles maps? Clear and re-add obstacles between each "Find path" call?

By the way, do I need to execute "regenerate obstacle map" after "Add obstacle" action?

EDIT: What if I add two Pathfinding behaviors to the same sprite? They still will be using the same one map?

EDIT2: This is a very odd limitation. Say, you are making a top-down game with many enemy types. Some enemies can't open doors, others can walk through doors, flying enemy can fly across water, ghost enemies can fly through almost everything.. How do you manage all their pathfinding needs with just one obstacle map?

C3 uses the same runtime as C2 did when you import a C2 project, which has largely unaltered code, so any differences would be unusual. Can you share projects demonstrating the difference?

Ashley Well, I was about to face this problem then because this is a really common feature in any rpg game, or in any game at all. Got goosebumps right now =[. So when we have an enemy that must have different obstacle map what would we do? Edit: The only thing I can think of is to re-add obstacles and wait for the next tick to find the path for this object. The problem is that it has a good probability to create glitches as others could use the wrong obstacle map.

Ashley

I spent several hours yesterday trying to figure out the problem, so I don't remember exactly what I did to capx file in C3, but at one point it stopped working.

I tried it again just now -

capx file in C2 works fine.

capx file in C3 works fine.

If I create a new c3p project and copy everything over from capx file - it still works fine.

But when I re-create the same file in C3 from scratch - it doesn't work.

So there are definitely inconsistent results...

Here are two files, they look identical, but if you open both in C3, one works and the other one doesn't:

dropbox.com/s/7t7fncjm4b9efay/PF_bug_C2.capx

dropbox.com/s/jvwwadefdy5525x/PF_Bug_C3_fromscratch.c3p

It seems to work if both objects have different values for "Cell border" in Pathfind properties. With the same values for both objects it does not work, no matter in which project. Looks strange to me.

So it seems like there is one obstacle map per each "cell size+cell border" combination. (not per "cell size+cell border+obstacles type" as logic would dictate). And it actually works the same way in both C2 and C3.

Anyway, setting different values makes it possible to use separate maps for different objects, which is good. Even if this is a bug, fixing it will cause incompatibility issues for many existing projects, so better leave it as it is.