Hello,
When i interact with a hotspot i am running an action script that does the following:
The expected behaviour is:
What actually happens:
Navmesh stopping distance is set to 0.
The issue only occurs when trying to play a custom animation after the player reaches the marker.
If the actions script only instruct the player to reach the target, then the player will stop exactly over the marker.
Any thoughts?
Thanks!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
What are your AC and Unity versions, and is this a 2D or a 3D game?
What do you mean by "Navmesh stopping distance"? Is this from a NavMeshAgent component attached to the character? If so, do you have the NavMeshAgentIntegration component attached?
What of your Settings Manager's Destination accuracy slider? The accuracy may need to be raised if you've reduced the Agent's stopping distance to zero.
Does your Player rely on Root Motion, or a Rigidbody, for movement?
Please share screens of your Player's Inspector, the Settings Manager, and the scene itself so we can understand the exact situation.
Hello Chris,
Thanks for your answer.
What i don't understand is why the player starts playing the custom animation before reaching the spot if i have selected "wait until finish".
Even adding a Character / Move Along Path / Stop Character won't help.
Action script:
https://drive.google.com/open?id=1n-o7UYvnlDbsWBOstdpjYmKk4MaOQR-3
Movement settings:
https://drive.google.com/open?id=1Rs2MfKTSDhWTIoqon3UJWJKjF1jf3ilM
Player:
https://drive.google.com/open?id=1q-LGu2bx6ot9-D0gpbymF5oJ6A57WKbr
Hope this helps and sorry for not sharing all these details in my original message.
I can't recreate this to any noticeable degree. Exactly how far away from the Marker does the Player start animating prematurely?
Your AC version is quite old. Even if it's just in a test duplicate project, please upgrade to the latest release and try there.
Precision movement is a complex topic, but the Manual chapter of the same name covers the basics. However, part of AC's internal workings when you rely instead on a NavMeshAgent for movement. Try unchecking Attempt to be super-accurate?.
It may be that this creates a conflict - do things work more correctly if you remove both the NavMeshAgent and NavMeshAgentIntegration components?