The Nav is really getting bad

laria · Aug 13, 2010

The download can 'complete' however, it can contain corrupted data. (A few bytes being misaligned, or backwards)

Isn't this the moment when you use md5 and sha1 hashes to check for the integrity of a file?

Apoc · Aug 13, 2010

laria said:
Isn't this the moment when you use md5 and sha1 hashes to check for the integrity of a file?

Probably a good idea

LiquidAtoR · Aug 13, 2010

As I wrote in the example is one occurence of corruption.
While downloading a meshfile stop the bot, and start it again.

Log example where I made first stop and instant start (the mesh corrupted):

Code:

[17:14:39:564]  De thread is afgebroken. - From: mscorlib   bij System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
   bij System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
   bij ..ReportStuck()
   bij Tripper.Navigation.PathFollowing.TripperNav.MoveTowards(Vector3 point)
   bij Styx.Logic.Pathing.Navigator.MoveTo(WoWPoint destination)
   bij Levelbot.LevelBot.Š(Object )
   bij TreeSharp.Action.RunAction(Object context)
   bij TreeSharp.Action..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.Decorator..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.Decorator..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.PrioritySelector..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.PrioritySelector..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij Styx.Logic.BehaviorTree.TreeRoot.()SmartExceptionsCore.UnhandledException @ 1818, offset:601
[17:14:39:570] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:14:58:332] Loading D:\Bots\HonorBuddy 2.0 Meshes (Shared)\loc1.xml.
[17:15:35:33] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:15:36.0139] [Navigator] Generated path from <-3442,404, 2629,83, 60,48686> to <-3162,443, 2757,384, 75,05252> in 546 ms (0,55 seconds)
[17:16:03:187] It appears that 'D:\Bots\HonorBuddy 2.0 NavMesh\Expansion01\Expansion01_29_40.trimesh' is corrupt.  If the bot doesn't move in the next few minutes, exit Honorbuddy, delete your meshes folder and try again.

After the corruption it was killing around a bit so it moved from it's current place to targets in the vincinity.

I stopped the bot, closed it and restarted the bot on the same place:

Code:

[17:17:38:949] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:17:40.4889] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.5989] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.7039] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.8099] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.9169] [Navigator] Could not generate path from {X:-3317,337 Y:2664,674 Z:102,3316} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:41.0269] [Navigator] Could not generate path from {X:-3319,833 Y:2663,555 Z:102,7258} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:41.1339] [Navigator] Could not generate path from {X:-3322 Y:2662,585 Z:102,0294} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:44:642] Activity: Downloading mesh.
[17:17:45.3279] [Navigator] Downloaded Expansion01_29_40.trimesh
[17:17:47:737] Stop and dismount...
[17:17:47:815] Dismount to get unstuck.
[17:17:48:154] Mounting: Swift Frostsaber
[17:18:08:439] Mounting: Swift Frostsaber
[17:18:25:724] Mounting: Swift Frostsaber
[17:19:05:513] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:19:06.6209] [Navigator] Generated path from <-3564,636, 2534,649, 72,14778> to <-3162,443, 2757,384, 75,05252> in 577 ms (0,58 seconds)

As you can see in this case it corrected itself, so I didn't see the point in reporting it, as it corrected it on my PC every time this happened.

Apoc · Aug 13, 2010

LiquidAtoR said:

As I wrote in the example is one occurence of corruption.
While downloading a meshfile stop the bot, and start it again.

Log example where I made first stop and instant start (the mesh corrupted):

Code:

[17:14:39:564]  De thread is afgebroken. - From: mscorlib   bij System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
   bij System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
   bij ..ReportStuck()
   bij Tripper.Navigation.PathFollowing.TripperNav.MoveTowards(Vector3 point)
   bij Styx.Logic.Pathing.Navigator.MoveTo(WoWPoint destination)
   bij Levelbot.LevelBot.Š(Object )
   bij TreeSharp.Action.RunAction(Object context)
   bij TreeSharp.Action..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.Decorator..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.Decorator..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.PrioritySelector..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij TreeSharp.PrioritySelector..MoveNext()
   bij (Object )
   bij TreeSharp.Composite.Tick(Object context)
   bij Styx.Logic.BehaviorTree.TreeRoot.()SmartExceptionsCore.UnhandledException @ 1818, offset:601
[17:14:39:570] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:14:58:332] Loading D:\Bots\HonorBuddy 2.0 Meshes (Shared)\loc1.xml.
[17:15:35:33] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:15:36.0139] [Navigator] Generated path from <-3442,404, 2629,83, 60,48686> to <-3162,443, 2757,384, 75,05252> in 546 ms (0,55 seconds)
[17:16:03:187] It appears that 'D:\Bots\HonorBuddy 2.0 NavMesh\Expansion01\Expansion01_29_40.trimesh' is corrupt.  If the bot doesn't move in the next few minutes, exit Honorbuddy, delete your meshes folder and try again.

After the corruption it was killing around a bit so it moved from it's current place to targets in the vincinity.

I stopped the bot, closed it and restarted the bot on the same place:

Code:

[17:17:38:949] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:17:40.4889] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.5989] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.7039] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.8099] [Navigator] Could not generate path from {X:-3316,925 Y:2664,857 Z:101,8802} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:40.9169] [Navigator] Could not generate path from {X:-3317,337 Y:2664,674 Z:102,3316} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:41.0269] [Navigator] Could not generate path from {X:-3319,833 Y:2663,555 Z:102,7258} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:41.1339] [Navigator] Could not generate path from {X:-3322 Y:2662,585 Z:102,0294} to {X:-3164,036 Y:2803,783 Z:86,14595}!
[17:17:44:642] Activity: Downloading mesh.
[17:17:45.3279] [Navigator] Downloaded Expansion01_29_40.trimesh
[17:17:47:737] Stop and dismount...
[17:17:47:815] Dismount to get unstuck.
[17:17:48:154] Mounting: Swift Frostsaber
[17:18:08:439] Mounting: Swift Frostsaber
[17:18:25:724] Mounting: Swift Frostsaber
[17:19:05:513] Changed POI to: Type: None, Loc: <0, 0, 0>
[17:19:06.6209] [Navigator] Generated path from <-3564,636, 2534,649, 72,14778> to <-3162,443, 2757,384, 75,05252> in 577 ms (0,58 seconds)

As you can see in this case it corrected itself, so I didn't see the point in reporting it, as it corrected it on my PC every time this happened.

That 'error' message happens when the bot can't decompress the mesh data. Again; it has little bearing on whether or not the decompressed data is corrupt.

Mordd · Aug 13, 2010

But what about a safeguard? IF it has this problem, try to redownload the mesh, or logout and log back in, or restart HB. ANYTHING that will keep it from locking up in place. Its so random that you cant blackspot it. If fact last night it happened while it was on its way to a vendor. A path its used hundreds of times that suddenly goes bad. There must be a way for HB to detect and correct itself.

tozededao · Aug 13, 2010

Mordd said:
But what about a safeguard? IF it has this problem, try to redownload the mesh, or logout and log back in, or restart HB. ANYTHING that will keep it from locking up in place. Its so random that you cant blackspot it. If fact last night it happened while it was on its way to a vendor. A path its used hundreds of times that suddenly goes bad. There must be a way for HB to detect and correct itself.

Tony answer: Questing is still on beta

My answer: HB should get some more "security" not just a warden protection, but something that detects if the bot is stuck, restarting it, if it gets stuck again disconnect, etc, we all know that the bot isn't detected but common, walking against a wall makes everyone report you, therefore, ban.

Odd · Aug 13, 2010

laria said:
Isn't this the moment when you use md5 and sha1 hashes to check for the integrity of a file?

Quoting for possible solution.
Also, tag.

Tony · Aug 13, 2010

tozededao said:
Tony answer: Questing is still on beta

thx for being my transponder but i dont need it atm
if i want to reply on a thread i will do it

Mordd · Aug 13, 2010

Tony said:
thx for being my transponder but i dont need it atm
if i want to reply on a thread i will do it

Seems like Tony is getting the Slam left and right now. He didnt even laugh and my poking him a few days ago.

tozededao · Aug 13, 2010

where's your sense of humour

lightingthunder · Aug 13, 2010

a little respect for the customers wouldn't hurt to be honest

MaiN · Aug 13, 2010

Code:

[10:03:20.5232] [Navigator] Could not generate path from {X:-7186.242  Y:-2236.068 Z:288.9766} to {X:-7172.119 Y:-2231.945 Z:298.4415}!

Is what happens when the navigator receives a start/endpoint that is not found on the mesh.
In that case, it can not even begin generating a path. This is usually because of a 'wrong' destination point - but when it's because of the characters placement (the start point), there really is not much HB can do.

Mordd · Aug 13, 2010

The fact that its made hundreds of runs with no issue and then just stopps tells me there is somthing wrong. HB should be able to correct it self someway. Sometimes restarting HB fixes it. Maybe it could run back a few feet and start over. Sometimes when I move the bot manually it will correct itself. Initiate a move forward command for 2 seconds then try again.

Mess1337 · Aug 13, 2010

Like Apoc said, delete the maps/mesh folder and try again.

Tony · Aug 13, 2010

tozededao said:
where's your sense of humour

lost it yesterday

Tony · Aug 13, 2010

lightingthunder said:
a little respect for the customers wouldn't hurt to be honest

ofc i always do that
expecting the same from users too

but
lets stay on topic

theholyone · Aug 13, 2010

this past week all people have been doing is bitching about a beta staged bot... i know nav has been out for a while but i mean honestly, if you see a problem its not hard to click blackspot and place it into your profile

I know most people leave their bots unattented but who cares? when you attend it again take 30 seconds and fix the profile then fire it up again

silverjax · Aug 13, 2010

Yep, first releases of HB it was like "Wow" and the releases they are releasing are going from good to bad -worse... *sigh*

Mordd · Aug 13, 2010

To those of you that say "Make a blackspot" "Delete your mesh"

Its easy for you to say that but not everyone bots in front of their computer. The entire point to the post was that this happens at random. So botting afk is more risky than it was earlier. HB needs to correct itself or the ban rate will go up big time.

_Hausi · Aug 13, 2010

/sign /sign /sign
I?m telling such things for weeks now...here and in the tracker section....

http://www.buddyforum.de/showthread...9.5.5-QuestOrder&p=99503&viewfull=1#post99503

Please scroll down!
Thank you

The Nav is really getting bad

Well-Known Member

Well-Known Member

Community Developer

Well-Known Member

New Member

Community Developer

New Member

"The Bee"

New Member

Community Developer

New Member

Well-Known Member

New Member

Active Member

"The Bee"

"The Bee"

New Member

New Member

New Member

New Member