Navigation Precision Issue

[mistahmikey]

When I issue the following:

								CommonBehaviors.MoveAndStop(
									ret => FishSpots.CurrentOrDefault.XYZ,
									0.6f,
									true,
									"Fish Spot"),

the navigation code decides it has reached its destination with a precision that is greater than that requested:

[15:35:53.341 D] Navigation reached current destination. Within 0.7213528.

This is causing a problem with my fishing code at times (when pressing up to a cliff edge, mostly), as the destination proximity precision required for Cast to become enabled is less than what the Navigation software is happy with, so my guy just stands there, forever hoping to move that last little elusive bit.

 

[mastahg]

Current navigator has a precision of .8f, trying to get any closer then that you'll run into issues. What you should do is move the point your trying to get to.

 

[mistahmikey]

Ah, ok, thanks for clearing that up. BTW, you have said you are rewriting the navigator, which in its current form is consistently causing my AFK scripts to hang. Any ETA on when your new and improved version will be available?

 

[mastahg]

Ah, ok, thanks for clearing that up. BTW, you have said you are rewriting the navigator, which in its current form is consistently causing my AFK scripts to hang. Any ETA on when your new and improved version will be available?

If something is hanging then you are doing something wrong. New nav wont be ready for a while.