Search results

Same here. Hope there is a fix coming cause I need mats!! :)

Diablo crashes out with the window that tells me to send in the error report, but only when I am running DB. I can manually play D3 and not get any crashes. Its just when I am botting that D3 crashes like that and I dont want to send in the report just in case...haha Ill try to get a print...

Fresh W10 install and DB install.

Again crashed about 2min after I hit start. Odd sometimes it crashes within a couple minutes (few times in a row even) and sometimes it runs for hours and then crashes.

All these errors I get were with running necros full time. Going to run some other characters and see if that helps. So far two WD's have been running 6+ hours...cross fingers.

Another log if it helps. Had to zip it cause it was too big.

So after I started the bot back up AFTER I rebooted from what Tony did on my pc the bot crashed with that log. THEN I restarted the bot again and it's been running for hours...lol. Also my 2nd bot does a lot better with its runs without crashing (only every few hours). I'll post it's log when...

No luck...still crashing.

Here is another log right after it crashed. Sometimes it will run for hours before it crashes. This time it was right after I hit the start button and it was getting ready to start the run.

I am not seeing any of those in my programs list. Sometimes it will run for hours and sometimes it errors before it starts the first rift (regular or greater). So far I don't notice any pattern to it.

Right before the character enters the rift portal D3 shuts down and then DB gives a 20 second countdown and also shuts down. Only plugin I have is trinity.

Thats one option I wish was still there...

I don't know if this is a demonbuddy problem or Trinity problem, but the bot will enter a game and just stand there and DB has to be closed using task manager. Usually restarting DB fixes this, but its annoying to wait because it thinks the key is still attached.

Yep if you log out and let it update its a no go until we get an updated DB. If you don't log out it just gives you a warning before starting a new game...lol

Exiting Fraps seems to have done the trick. Is there that much of a difference between running fraps on windows 7 vs 10? I always had fraps on when running DB on 7.

I read a couple threads saying DB wasn't supported by windows 10 yet, but those were from last year and I wasn't sure if it was supported yet. No errors when DB is attaching, but when I try to config Adventure or Trinity plugins. This was after I updated to windows 10 AND reinstalled DB...

There used to be an option to tell the bot to either sell OR salvage, but now all I see is the sell/salvage option. Right now it is salvaging trash items, but where do I change that to sell them instead of salvage?

Exactly what NoLongerAwayBoss said. My WD used to be able to do Grift 64+ with no problems, but now she has trouble with just Grift 60 because of all the standing around and even stopping to the point the gold/hour exp/hour goes to 0. If I nudge her forward a few steps manually she gets going...

Anything we can do to fix this? I just now noticed it with the latest update. Just sits there and dances even when there is nothing around. Also I keep getting the error [Trinity 2.14.44][Behavior] Fatal Error: Couldn't find a valid attack ability. Not enough resource for any abilities or...

Only thing that helped slightly with mine was to turn off the auto skill equip, but it still stops on its own every now and then. Before I unchecked that option it would start flashing the skills button and then dc from the game entirely.