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

Keep getting this ANNOYING error with latest db

Status
Not open for further replies.
A

ajc82388

New Member
Joined
Sep 11, 2012
Messages
311
Reaction score
0
[14:39:33.400 N] DemonbuddyBETA v1.0.1288.140 started
[14:39:34.444 N] Logging in...
[14:39:35.216 N] Was not able to attach to any running Diablo III process, are you running the bot already?


wtf
 
Tony said:
is your D3 exe renamed?
Click to expand...
no.

i have to literally, run demonbuddy, and close it about 20 times before it catches the window.
i have about 10 bots

thats 200 times i have to open/close db before it attaches to all of my windows.
pretty annoying
 
restart your D3 and try again then
 
Tony said:
restart your D3 and try again then
Click to expand...

so basically, if i am running 10 bots, and ONE of them happens to crash..
I'm gonna have to close ALL of my clients and restart them ALL one by one?
so that the bot can attach itself to "new d3 processes"?
Because if d3 processes are already running, it doesn't seem to want to attach itself to a new one for whatever reason.
 
no, you just have to keep waiting for each D3 istance your tryign to attach to. So it's pretty much a waiting game.
 
ryan12345 said:
no, you just have to keep waiting for each D3 istance your tryign to attach to. So it's pretty much a waiting game.
Click to expand...
i guess my point is that, it never used to be that way.

so somebody broke something.
 
This bug is in every of the latest builds and happen when:

You start the FIRST d3. You can attach DB whenever you want to this copy.
You start the second or third or... (every number 2+) d3 and DONT attach DB directly to it. If you start another d3-copy or copies and if you then try to attach DB, you will get this error. Its anoying... Only solution: You have to start d3 AND THEN directly DB, d3 and DB, and so on.
 
derico5 said:
This bug is in every of the latest builds and happen when:

You start the FIRST d3. You can attach DB whenever you want to this copy.
You start the second or third or... (every number 2+) d3 and DONT attach DB directly to it. If you start another d3-copy or copies and if you then try to attach DB, you will get this error. Its anoying... Only solution: You have to start d3 AND THEN directly DB, d3 and DB, and so on.
Click to expand...

Bzzz.. Wrong. Why do you post as fact when you don't even try other solutions?

All you have to do when you get the error, is close the DB with the error and re-open DB. It works then.

I open all my D3's at once, first DB works, open #2 DB it errors, close #2, reopen DB and it works. Rinse, repeat.

You only have to open DB one extra time for each D3, big deal.
 
Exact same issue here. I open all my diablo copies and log them in. Open first db connects and attaches fine. Once its all set and I hit start the second won't find a diablo to attach to and its either until I wait so long or toggle between windows that it'll attach properly.

On a similar note is there a way I can designate demonbuddy to attach to a specific diablo without having to select it from the list upon connecting? I noticed YAR is able to link them without apparently having to go into that menu and I would like to be able to do the same.
 
@smurg. Yep, never tested to start it twice. Good to know hehe. But fact is, this bug hit DB when the last major update was. 190 or 191, or even before. Cant remember, but was a major update.
 
Last edited:
for those with problems,use support issues section plz

closed
 
Status
Not open for further replies.
Back
Top