DB loosing nav server at same locations..

[satan2004]

DB loosing nav server at same location everytime

What is going on? is the developers working on this? its allways at the same locations


happens in field of slaughter

 

[Anonuzer01]

Happening in Weeping Hollow for me:

[17:15:46.843 D] Generating path to Hollow #25 - <2682.138, 1914.299, 0.1>
[17:15:46.858 D] Waiting for path request to finish...
[17:15:46.903 D] Generating path to Hollow #25 - <2682.138, 1914.299, 0.1>
[17:15:46.922 D] Waiting for path request to finish...
[17:15:47.007 D] Generating path to Hollow #25 - <2682.138, 1914.299, 0.1>
[17:15:47.021 D] Waiting for path request to finish...
[17:15:47.066 D] Generating path to Hollow #25 - <2682.138, 1914.299, 0.1>
[17:15:47.079 D] Waiting for path request to finish..

 

[packetloss]

All their servers are foobar today. The reason you get it in certain spots is DB only uses the NAV server for long paths in profiles. Giles has recommended that all profiles be rewritten with smaller pathing waypoints to avoid using the NAV server altogether. The autentication server issues are another story. Folks have reported getting random invalid sessions throughout the day.

 

[Cyonsiaros]

I think wow panda land profiles should be written to use smaller pathing and stop hogging up the server rack

 

[Tony]

for those with problems

http://www.thebuddyforum.com/demonb...30-reminder-asking-support-reporting-bug.html

closed