December 20, 20187 yr [N] 20:07:13 - [Path-Finding] Path Count: 2 (15,56946y, 11926ms) .... [N] 20:07:18 - [Path-Finding] Path Count: 2 (7,621125y, 30993ms) .... [N] 20:10:08 - [Path-Finding] Path Count: 2 (7,621125y, 30492ms) [N] 20:10:09 - [MovementManager] Waypoint timed out [N] 20:10:09 - [MovementManager] Report navmesh poly to avoid it .... [N] 20:10:40 - [Path-Finding] Path Count: 2 (4759,888y, 30397ms) (resultPartial=True, resultSuccess=False (more info with server log option)) .... [N] 20:11:10 - [Path-Finding] Path Count: 2 (16,86641y, 30390ms) ... [N] 20:12:07 - [Path-Finding] Path Count: 2 (28,92023y, 30394ms) And so on. Is there any global problems or it's just me? My google.com ping is about 14-15ms, ingame ping is about 140-200 ms
December 20, 20187 yr Author Well, seems it's back ? [N] 22:35:00 - [Path-Finding] Path Count: 2 (36,45547y, 30400ms) ..... [N] 22:37:29 - [Path-Finding] Path Count: 5 (112,8389y, 25012ms) If i'm the only one with this this problem, maybe it's at my side.
December 20, 20187 yr Server side all seem good, you request several path a the same time? or no more than usual?
December 20, 20187 yr Author Should be only one. There are cases when it can be more then once (when it's checking for LOS and obstacles to the target), but there was no such cases so far. I will check it on my side. Will try to change all proxies, and will try another pc and another wow realm, maybe vanilla one.
Create an account or sign in to comment