Horlais' Peak Navmesh Errors

[dazusu]

I have:

• [x] searched existing issues (http://github.com/darkstarproject/darkstar/issues/) to see if the issue I am posting has already been addressed or opened by another contributor
• [x] checked the commit log to see if my issue has been resolved since my server was last updated

Client Version (type /ver in game) : 30160203_0

Server Version (type @revision in game) : 1da5803

Source Branch (master/stable) : master

Additional Information (Steps to reproduce/Expected behavior) : This error is spammed when a monster is engaged in Horlais' Peak:

[07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139) [07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139) [07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139) [07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139) [07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139) [07/Mar] [22:30:39][Navmesh Error] CNavMesh::raycastPoint startRef is invalid (0.000000, 0.000000, 0.000000) (139)

[bendangelo]

Looks like a mob is stuck at 0 0 0. Will fix that.

[dazusu]

The mob in question isn't stuck at 0,0,0, it's a mob I've just implemented - it has a position in the database; and popped it infront of me; when engaged, it spams that error.

[teschnei]

sounds more like a problem with your mob than the navmesh

On Mon, Mar 7, 2016 at 5:08 PM, Liam Conlan notifications@github.com wrote:

The mob in question isn't stuck at 0,0,0, it's a mob I've just implemented

• it has a position in the database; and popped it infront of me; when engaged, it spams that error.

— Reply to this email directly or view it on GitHub https://github.com/DarkstarProject/darkstar/issues/2880#issuecomment-193517847 .

[dazusu]

@bendangelo let's discuss this in more detail when you next have some free time to jump on IRC. There's certain situations where pathing fails; and re-attempts are spammed at such a rate that dsp chokes/dies/becomes incredibly laggy and unusable without restarting. I'm talking about situations other than the one discussed in this issue too.

Perhaps some cooldown on attempts to remap a path after a failure; or not attempting to path mobs where there's an obvious issue with the mobs configuration that's going to cause issues.

[bendangelo]

Ok.