So the player can’t reach those nodes you mean?
In the Seeker script there is a variable called Max Angle, that will define the maximum angle that unit can travel.
maybe i can´t get it right, but the max angle doesn´t seem to work in that way.
the robot just keeps going, crossing every mountain….
excuse my english, i hope you know what i mean!
he doesn´t when i put the robot max slope down, but the path reminds the same, he just cannot walk it.
@joe
The reason can be that the terrain has a much higher resolution than the grid, if so, the terrain might have a bump in the ground but the script wont notice since the nodes was placed on the sides of the bump.
Also, check so the grid shows up in 3d, and not as a flat surface.
You can solve this by either place colliders where you don’t want the player to go, increasing the resolution of the grid or struggle a bit more with the Max Angle and Angle Cost settings to get it good.
grat work and thanx a lot!
one question. i did set up a grid and stuff, and every thing seems to work fine, except one thing. in your examples the caracter keeps walking and never stops, in my case the caracter – a sphere stops for a short time when ever changing the direction, the command also sys stay. i cant figure out how to change that. any idea?
The reason is probably because the dontComeCloserRange is to low, it does only look for a new point every 0.2 seconds or something (hard coded) when it reaches the target it will stop and then wait until the target is recalculated next time, if the dontComeCloserRange is a bit higher it will find the next waypoint before it stops,
so either you set dontComeCloserRange to a higher value or you change the AI code to look for a new point more often.
Hi,
Any reason why the follow terrain option doesn’t show up in the editor? :S
The follow terrain option does only show up if there is a terrain object in the scene.
hi!
is there any way to take nodes out of the grid by the terrain angle?
great stuff by the way!
joe
Hi Joe
So the player can’t reach those nodes you mean?
In the Seeker script there is a variable called Max Angle, that will define the maximum angle that unit can travel.
maybe i can´t get it right, but the max angle doesn´t seem to work in that way.
the robot just keeps going, crossing every mountain….
excuse my english, i hope you know what i mean!
he doesn´t when i put the robot max slope down, but the path reminds the same, he just cannot walk it.
@joe
The reason can be that the terrain has a much higher resolution than the grid, if so, the terrain might have a bump in the ground but the script wont notice since the nodes was placed on the sides of the bump.
Also, check so the grid shows up in 3d, and not as a flat surface.
You can solve this by either place colliders where you don’t want the player to go, increasing the resolution of the grid or struggle a bit more with the Max Angle and Angle Cost settings to get it good.
ok, thank you!
i´ll check that.
i love to play around with it, so i will find out!
regards, joe
i can´t believe i did not see this last night!
everything works just fine.
thanks for sharing!
Hi,
Would you mind explaining what Node links are used for? I can t get it right. Is is to link 2 grids together?
Thanks !
You are correct! That’s what they are used for.
hi,
grat work and thanx a lot!
one question. i did set up a grid and stuff, and every thing seems to work fine, except one thing. in your examples the caracter keeps walking and never stops, in my case the caracter – a sphere stops for a short time when ever changing the direction, the command also sys stay. i cant figure out how to change that. any idea?
Hi Smoky78
The reason is probably because the dontComeCloserRange is to low, it does only look for a new point every 0.2 seconds or something (hard coded) when it reaches the target it will stop and then wait until the target is recalculated next time, if the dontComeCloserRange is a bit higher it will find the next waypoint before it stops,
so either you set dontComeCloserRange to a higher value or you change the AI code to look for a new point more often.
thanx a lot for the fast reply. i just found out about the 0.2 seconds in the AI code. thanx again.