The A* gameObject is a child under the “searchers” gameObject.

I have the Terrain Scene open, and I am trying to go through the get started guide you wrote here. It might just be me, but I cannot find the A* game object in my project view at all. I can find the A* Instructions in the Hierarchy but I don’t suppose that is what I am looking for. I have been looking through all the folders in the Project but I must be a bit blinded :S

Hmm, seams like I have to dig a bit deeper with this problem.
Do you think you can send me a simplified project that I can take a look at? (me email is aron[dot]g[at]me[dot]com)

Second, you can find the StartPath call syntax on a page in the docs.

Third, this is only possible with the Grids mode, don’t make two instances of the AstarPath script, the script is a singleton class (maybe I should write a warning about that somewhere), you simply click the Add Grid button in the static settings under ‘Grids’ and then you can adjust it to any position you want.
The grid highest up in the list has the highest priority (it will be chosen if two grids are overlapping).

I’m having the same problem as Willem. Obstacles are getting in the way. The blue debug line goes through them, the character doesn’t stay on the grid waypoints. I made the grid of small squares, so the blue line is about as long as 6 grid squares. I’m trying to track down a variable to tweak, without much luck. It looked like maybe pickNextWaypointDistance or maxStop but I reduced both with no change. Any help would be appreciated on how to make the character stay closer to the grid.

That’s my main struggle right now. I need to pass targets to the script without using the mouse click method, but I think I can track that down.

One other thing that would be nice to know is how to implement multiple grids like you were talking about. Your example was to use one for an interior space and another one for terrain. My question is how to do that. Each A* object with the Astar Path script attached?

Just to mention that I use two parameters from your method : AstarPath.active.Scan(true, 0); // default parameters ?

And if I call it from an “Awake”, AstarPath won’t be initialised, so you need to call it from at less “Start”.

Again, thanks a lot Aron

I don’t own Unity Pro so I don’t have so much experience with Asset Bundles, however I don’t think it would work since a grid requires very much memory, for example a 100*100 grid would require about 1.9 mb of memory, and that is just the most important stuff.
I am working on a serializer which could (maybe) cut down the file size a bit though.
If you want to trigger the scanning in a later point in the game you can set Calculate On Startup to false (at the bottom in the Static Settings) and then call AstarPath.active.Scan () whenever you want, this will cause some lag though.

But I was wondering if it would be possible to include this sytem in an AssetBundle, and load it after the main scene (which would include the terrain, the mesh or… whatever !) ?

There can be several reasons, here’s what I think.
1. The script you use to move the zombies searches for the nearest waypoint (all) instead of when the next waypoint is near enough. When they walk past a wall, the waypoints on the other side of the wall are closer than the ones on this side of the wall, the zombie would then try to walk through the wall.
Do you see that the generated path is actually going through the walls? (turn Debug Path on the Seeker script to true).

2. You should use the Character Controller to move the zombies, and your look-towards-the-next-waypoint script should set the y property of the look direction to zero before applying it. Look in the AIFollow script in the RotateTowards function for some example code.

Thanks for reporting this.
I have updated the webplayer to work, and I have also updated the project to work in unity 2.6.
The script cannot paint on terrains directly, I made an example script which shows all the options and sends the paint calls, you can write a script which paints on the terrain too, basically all you need to do is to transform the coordinates from world space to texture space.

Also I have the nodes all generated, walkable and unwalkable. In one place I have a house, with 4 walls. There are some doors, and the unwalkable nodes surround the walls, but the pathfinding keeps trying to go through them anyway. The zombies move up to the wall and just stop, pressing endlessly against it. Sometimes they can make it through the door, but not too often. Any ideas?