I’d recommend checking out the Getting Started page. Graphs are what we call navigation ‘areas’. Navmesh is a polygonal mesh to represent a walk able surface.
If you want to simply call scan from your own script you can do something like:
public virtual void OnGameReady()
{
AstarData.active.Scan();
}
hmm, ye fair enough, I don’t have any experience with the spherical tools.
I read back through the posts a little;
You could write a graph modifier that does a custom collision check for each node based on the code linked above. Set the walk ability to false for those nodes that failed the collision test.
That’s tricky since the collider normal will not be the one you want to use for the agent. You’ll have to make some modifications to the AIPathAlignedToSurface component to detect stairs in particular and adjust the normal as appropriate (e.g. make it always use stair.transform.up or something).
Hi. Could you make any spherical beta free? I would buy pro if I had any money, but too bad being a student. Anyways at least AIPathAlignToSurface would be nice to have. I am making a basic game and struggle with AI around a sphere. Many thanks if you could help.
Hi, how can i fix this problem? agents walk through obstacles. In spherical navMesh i cant use meshCut or RVOobstacles. i have created unwalkable zones just by checking intersections of navMesh points and obstacles box colliders boarders. But i still have this problem :C
If you use the AIPath (or AIPathAlignedToSurface) script you should probably check the ‘Constrain To Graph’ checkbox to make sure the agents stay inside the graph. The corresponding RichAI script should do this automatically.
Yes, when “Constrain To Graph” is enabled - i have this strange behavior,
if its disabled - i have normal behavior but sometimes agents run through obstacles.
( You have reached the reply limit for this topic
We’re sorry, but new users are temporarily limited to 3 replies in the same topic.
Instead of adding another reply, please consider editing your previous replies, or visiting other topics.)
That looks like a Unity bug or a bug with some post processing script for assemblies that you are using.
I’m not sure what could be causing that but I’d report it to Unity.
However if you click on the “Something went wrong…” item you might see some more info about what exactly went wrong. The message might be longer than two lines.