I have some problems with the path finding, and cant see why it doesn't work as it should according to the manual if I understood it correct.
There are 2 objects that are told to go somewhere near the X. Both have path finding and set to custom Obstacle, the tilemap doesn't have solid behaviour, not that it makes any difference.
From the manual:
If Solids, the behavior will automatically mark cells touching objects with the Solid behavior as being obstacles. If Custom, you must define which objects are obstacles by using the Add obstacle action on startup.
So I tell Object 1 to add the tilemap as obstacle and clear all obstacles for object 2, which shouldn't be needed in the first place.
If the Obstacles property is Custom, add an object to mark as an obstacle in the pathfinding grid. If this is done during the game (after Start of layout), you must also use Regenerate obstacle map for it to take effect.
Since this is done at start of layout Regenerating the obstacle map for Object 1 doesn't need to be there. I was just testing.
Remove all obstacle objects added with Add obstacle. You must also use Regenerate obstacle map for this to take effect.
So in desperation I added Regenerate obstacle map for both objects which again shouldn't be needed.
However when I run the program, regardless of adding all the actions that shouldn't have to be there or removing them.
The objects behave like this:
The red object behaves as it should, however the green object insist of also seeing the tilemap as an obstacle. And I cant figure out why it does that. As it clearly state in the first quote:
[quote:1qs6f342]If Custom, you must define which objects are obstacles by using the Add obstacle action on startup
None of the objects are part of a family or anything they are 2 separate objects.
Anyone know why the green object behaves like that?