Pathfinding seems to not be able to locate paths outside of the top screen. It's very arbitrary behavior and I'm at a loss as to how to describe it. Depending on the position of the Pathfinding object, and the object being pathfound to, either the object cannot find a path (despite no collision in the scene) or the object "can" find a path, but the path is not correct and stops halfway down the screen.
Attach a Capx
https://dl.dropboxusercontent.com/u/987 ... ngBug.capx
Description of Capx
Keyboard commands spawn an object with the Pathfinding behavior, and cue the object to find a path to a different object.
Steps to Reproduce Bug
- Run Layout 2
- Press A to spawn the Pathfinder object (spawns on blue object called PathfindTo)
- Press S to find path to PathfindFrom object (green)
Object finds a path, travels along the path, and stops before it reaches its real destination - it stops in the middle of the screen.
Moving the blue and green PathfindTo and PathfindFrom objects into different configurations creates different results. Sometimes a path is able to be found, like the configuration on Layout 1
Object finds a path, and travels along the path to its destination.
Operating System and Service Pack
Windows 10 Home
Construct 2 Version ID
R229 (also was not working in R227)