What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Release] Demonbuddy - Sunny Monday build (#227)

Status
Not open for further replies.
I am telling you guys they busying sleeping in prep for GW2 mega session!
 
I had the same problems all you did and today I upgraded to Giles new plugins and Ive been running 6 copies for the last 5 or so hours with zero crashes. It looked like it was the plugins crashing the game and not DB. Giles updated 2 plugins today. Try them and see how it goes for you guys.
 
maaan just give us a old version of DB patched for 1.04 and take away all the changes in 220.... then when u find what is causing the crashes bring 220 back with an undate
 
gopensgo said:
maaan just give us a old version of DB patched for 1.04 and take away all the changes in 220.... then when u find what is causing the crashes bring 220 back with an undate
Click to expand...

Since the patch of today everything is working fine,
Must be the less intellectual that are having problems.
 
Nyvelle said:
Since the patch of today everything is working fine,
Must be the less intellectual that are having problems.
Click to expand...

Yep everything is the users fault. They must be dumb. It is not like I have 4 virtual machines, all with the exact same config running the exact same plugins, bot version and everything. Care to explain to me why 2 get constant crashes and the other 2 never crash? Since you are so smart and all. /endsarcasm
 
un stuck handler need to be fixed

[02:13:39.490 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:39.520 D] Navigator.Clear
[02:13:41.090 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:41.090 D] Raycast path generated.
[02:13:41.090 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:43.140 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:43.160 D] Navigator.Clear
[02:13:44.710 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:44.710 D] Raycast path generated.
[02:13:44.710 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:46.760 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:46.790 D] Navigator.Clear
[02:13:48.340 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:48.340 D] Raycast path generated.
[02:13:48.340 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:50.380 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:50.410 D] Navigator.Clear
[02:13:51.960 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:51.960 D] Raycast path generated.
[02:13:51.960 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:53.990 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:54.010 D] Navigator.Clear
[02:13:55.580 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:55.580 D] Raycast path generated.
 
MonsterMMORPG said:
un stuck handler need to be fixed

[02:13:39.490 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:39.520 D] Navigator.Clear
[02:13:41.090 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:41.090 D] Raycast path generated.
[02:13:41.090 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:43.140 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:43.160 D] Navigator.Clear
[02:13:44.710 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:44.710 D] Raycast path generated.
[02:13:44.710 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:46.760 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:46.790 D] Navigator.Clear
[02:13:48.340 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:48.340 D] Raycast path generated.
[02:13:48.340 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:50.380 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:50.410 D] Navigator.Clear
[02:13:51.960 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:51.960 D] Raycast path generated.
[02:13:51.960 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[02:13:53.990 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[02:13:54.010 D] Navigator.Clear
[02:13:55.580 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[02:13:55.580 D] Raycast path generated.
Click to expand...

looks like a profile issue. it happens when you are trying to move to a waypoint that doesnt exist (random maps can cause this)
 
swolbyn said:
looks like a profile issue. it happens when you are trying to move to a waypoint that doesnt exist (random maps can cause this)
Click to expand...

Man that sucks my own FOS prof is about as useless as the bot needing human intervention... GG
 
After updating all plugins and everything again, i get less crashes, but it still crashes too much for even just overnight botting.
 
Btw, each latest DB version takes up abt 10% of my cpu usage.....it's so consuming of my cpu which is not supposed to be so cpu heavy....plz fix it ^_^''
 
from my experience its a hardware issue
DB works fine on my i7 quad core but crashes to shit on an older phenom II
by 'fine' i mean its crashed just once in 2 days of straight farming post 104 patch
guys with these sorts of problems its not an easy fix...if it was a static error everyone received well any coder could smash that out in a day or two
id expect the db team to be awhile seeing as the problem is bigger
 
which leads me to say we all paid for this but get over yourselves, its bugger all cash really for what your getting in return plus the dev team arent a bunch of wanks who go afk for days and dont update the status - they are working on it!
 
so giles updated his plugins and since updating his plugins I went 8 hours straight no crashes. He did some things to act differently to account for the errors db was throwing up. My understanding is there is still issues with db but giles fixed his plugins cope with that. Plus if you use Radonics plugin he updated that as well. Maybe coincidence but I am staying up without crashes now. (Also blizzard did a patch to fix some crap they had going on and I did the work around they put up for the stuttering, disabling the windows file checking)
 
fuimusbruce said:
so giles updated his plugins and since updating his plugins I went 8 hours straight no crashes. He did some things to act differently to account for the errors db was throwing up. My understanding is there is still issues with db but giles fixed his plugins cope with that. Plus if you use Radonics plugin he updated that as well. Maybe coincidence but I am staying up without crashes now. (Also blizzard did a patch to fix some crap they had going on and I did the work around they put up for the stuttering, disabling the windows file checking)
Click to expand...

any idea on fixing this error:[00:46:50.527 N] ========== Grid segmentation resetting!!! ============
[00:46:58.335 N] ========== Grid segmentation resetting!!! ============?

Even I restarted the bot, the bot still afk at town doing nothing at all =(......
 
fuimusbruce said:
so giles updated his plugins and since updating his plugins I went 8 hours straight no crashes. He did some things to act differently to account for the errors db was throwing up. My understanding is there is still issues with db but giles fixed his plugins cope with that. Plus if you use Radonics plugin he updated that as well. Maybe coincidence but I am staying up without crashes now. (Also blizzard did a patch to fix some crap they had going on and I did the work around they put up for the stuttering, disabling the windows file checking)
Click to expand...

I reupdated everything, still crashed in under 1hour. Better than before when it took 5 minutes on average to crash, but still unusable for botting. I thought the devs found the issue, maybe they're all playing gw2 :D Only option is to wait.
 
Status
Not open for further replies.
Back
Top