• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Weird and annoying problem

    Discussion in 'Archives' started by Tomz, Feb 16, 2010.

    1. Tomz

      Tomz New Member

      Joined:
      Jan 22, 2010
      Messages:
      21
      Likes Received:
      0
      Trophy Points:
      0
      [23:27:03:609] Target nearest enemy.
      [23:27:04:78] interact: 0x19B2F528
      [23:27:04:109] interact done: 0x19B2F528
      [23:27:07:328] interact: 0x19AFC8A8
      [23:27:07:406] interact done: 0x19AFC8A8
      [23:27:10:578] [GeneratePath (Horde1-60.mesh)]: WARNING: Suitable end node is more than 25 yards away from the destination point (exact distance is 32,83957 yards)! Please append to your mesh if this gives you any problems.
      [23:57:57:500] Error - sync2: ReadUInt at 0x191FD010 failed.

      I dont understand how this keep happening ... I have had only one succesfull night without disconncect, but every other night i found my computer at disconnect this make me so angry ....
       
    2. khurune

      khurune Member

      Joined:
      Jan 15, 2010
      Messages:
      836
      Likes Received:
      4
      Trophy Points:
      18

      Like I've commented on your quote, This seems to be a profile error, Am gonna download and have alook at the profile now see if i can see anything that could be up with it. But you need to supply a little more information as this is a large profile with many subprofiles. Please attach your log.
       
    3. chaser21

      chaser21 Community Developer

      Joined:
      Jan 21, 2010
      Messages:
      43
      Likes Received:
      0
      Trophy Points:
      0
      I get the same issue!!! ive found that if im activly using the computer, not touching wow it runs fine but if im not on the computer it will cause errors and dc from wow. I have attached my log if anyone can tell me whats up that would be great this is rather annoying.

      Sorry the file is 2mb so i compressed it. Any help would be greatly appreciated :)
       

      Attached Files:

    4. khurune

      khurune Member

      Joined:
      Jan 15, 2010
      Messages:
      836
      Likes Received:
      4
      Trophy Points:
      18
      Not sure what happened with yours Chaser, thats a pretty big error spam, aint come across that one personally, Tonys on usally in the next few hours, am sure he'll be able to shed some light on it.
       
    5. chaser21

      chaser21 Community Developer

      Joined:
      Jan 21, 2010
      Messages:
      43
      Likes Received:
      0
      Trophy Points:
      0
      Thanks for looking at it, hopefully someone can point me in the wright direction
       
    6. ski

      ski Well-Known Member

      Joined:
      Feb 12, 2010
      Messages:
      3,720
      Likes Received:
      48
      Trophy Points:
      48
      He's definitely going afk but that hotspot error is only 32 yards away (I'm assuming its using , instead of . because of Euro-ness). Still possible that in that 32 yards the genpath tried to run straight and got stuck on something, impossible to tell but you can try using "Start Mapping" to extend the mesh to wherever this error is occurring.
       
    7. ski

      ski Well-Known Member

      Joined:
      Feb 12, 2010
      Messages:
      3,720
      Likes Received:
      48
      Trophy Points:
      48
      Code:
      [4:44:46 AM:953] [GeneratePath (Alliance Outlands.mesh)]: WARNING: Suitable start node is more than 25 yards away from the start point (exact distance is 29.81954 yards)! Please append to your mesh if this gives you any problems.
      [4:44:47 AM:171] Mounting:Charger
      [5:15:16 AM:671] Error - sync2: ReadInt at 0x11C463FC failed.
      Same issue here, it looks like your mesh doesn't fully extend to one of your hotspots or where your character ended up and it afk'd out.
       
    8. chaser21

      chaser21 Community Developer

      Joined:
      Jan 21, 2010
      Messages:
      43
      Likes Received:
      0
      Trophy Points:
      0
      So what your saying is that somehow the bot wondered outside the mesh range and couldnt get back? Is it because the pull distance is to high? (currently set to 30) or something else? How can I avoid this happening in the future?
       
    9. Tomz

      Tomz New Member

      Joined:
      Jan 22, 2010
      Messages:
      21
      Likes Received:
      0
      Trophy Points:
      0
      Im using Bliiks 1-60 Horde and this has happened for example at barrens and tanaris
       
    10. FortuneCooky

      FortuneCooky New Member

      Joined:
      Feb 2, 2010
      Messages:
      91
      Likes Received:
      0
      Trophy Points:
      0
      got the same problem . happened 5 times already. using 1-60 horde blikk too. its happening in the barrens atm

       
    11. ski

      ski Well-Known Member

      Joined:
      Feb 12, 2010
      Messages:
      3,720
      Likes Received:
      48
      Trophy Points:
      48
      It sounds like the mesh for that profile needs to be extended wherever you're getting stuck. Without knowing where that is, though, its hard to add.
       

    Share This Page