Weird AI Pathfinding Problem

[wieljer]

Jan 5, 2017 23:47:36 GMT Invector said:

Did you use this fix from another thread? - I experienced some strange behaviour before the fix

Cause > If the character has a Capsule Collider higher then 2, the raycast will not find the ground and he will keep floating.

How to Fix:

Open the v_AIMotor and find the method CheckGroundDistance

replace this line:
if (Physics.Raycast(ray1, out groundHit, 1f, groundLayer))

for this:
if (Physics.Raycast(ray1, out groundHit, _capsuleCollider.height * 0.75f, groundLayer))

Awesome this fixed an issue for me. 

[wieljer]

By default he should stop at distance '1' in the editor see Chase Stop Distance on AI, unless you modified him to not stop when lose target?
Also can you increase field of view in editor?
is SphereSensor on Layer 'Triggers' and tag 'Weapon'?
maybe your physics matrix changed?

my values for Sensors
Max Detect Distance 4.5
Min Detect Distance 2
Distance To Lost Target 5
Chase Stop Distance 1

[thegreatest95]

Turning Distance To Lost Target down makes him do the bug more often and easier, turning it up no matter how high doesn't stop the bug.

Other than that same settings.

And yes, you can increase field of view in editor, goes up to 180 (as mine is set too) so they can see everything around them including behind.

[Chronicman]

Field of view works like this if any one is wondering, it takes 180 from the transform forward right side and left, This gives you a total of 360.

[Invector]

try drag and drop one of the enemy prefab of the default melee scene and see if they behave correctly, them just compare the variables

[thegreatest95]

I'm really confused. Your prefabs don't have the bug but mine do. Even if they have the exact same variables.

[thegreatest95]

I have figured out the issue... and it's an integration issue unfortunately.

Whenever I attached Chronos (Time controlling asset) to your prefabs, it causes the bug to happen in them as well.

Most likely reason? Because Chronos wants me to use a different version of controling NavMeshAgent.speed, but I can't figure out how to integrate it with Invector's VERY large NavMeshing system...

[Invector]

We use the default navmesh from Unity... there is no really mystery there

what version chronos needs?

[thegreatest95]

Jan 7, 2017 2:12:45 GMT Invector said:

We use the default navmesh from Unity... there is no really mystery there

what version chronos needs?

Chronos uses it's own NavMeshAgentTimeline (Which I believe is just some script overriding of NavMeshAgent to work with their Timeline component).

Which doesn't change much... it still uses the normal NavMeshAgent on the object (I think...) 

This is the only documentation they give about it 



So it's a bit hard to figure out how to do the changes needed... 

[Deleted]

Would it be possible to code that navmesh timeline code in that Chronos has?

[thegreatest95]

Jan 7, 2017 4:04:00 GMT @zeldalink33 said:

Would it be possible to code that navmesh timeline code in that Chronos has?

I'm sure there is some possible way... but at the moment I haven't figured it out. 

It's not as simple as changing Invector's agent.speed to Timeline.agent.speed unfortunately. 

[Invector]

Did you try change every line that contains NavMesh. to Timeline.navMeshAgent on the AI?

[thegreatest95]

Jan 7, 2017 12:46:38 GMT Invector said:

Did you try change every line that contains NavMesh. to Timeline.navMeshAgent on the AI?

Yea I did try that. And it doesn't seem to work. (On Timeline's end, not yours)

Think I'll need to create a separate new protected variable and then go through and switch out all the agents with timelineAgent on the ones needed and then hope it works?