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

DB Attaching to one client only.

N

ninjatuna

New Member
Joined
Jun 12, 2012
Messages
97
Reaction score
0
Hello,

After 291 was released I've encounter an issue where DB won't attach to a the 2nd/3rd and so on clients that I open only to the first one, I'll be posting the log but there isnt much in it but mostlikely will make sense to you than what it does to me.

So far I open one client as Administrator (diablo3) then I run a DB client as Administrator as well, it attaches perfectly fine and it works flawlessly.

When I open a 2nd client it doesn't attach at all and it gets stuck with both 291 and newest beta version.

Code: 
[18:19:30.241 N] DemonbuddyBETA v1.0.1219.110 started
[18:19:31.377 N] Logging in...
[18:19:32.235 N] Attached to Diablo III with pid: 3268
[18:19:32.257 N] Flashing window

Code: 
[02:16:39.020 N] Demonbuddy v1.0.1219.291 started
[02:16:41.059 N] Logging in...
[02:16:45.288 N] Attached to Diablo III with pid: 3264
[02:16:45.351 N] Flashing window

Please see attachments and let me know if there is something I can try besides clean DB installs, d3 install and running as Administrator cause Ive already done this.
 

Attachments

Does the second D3 fully load? Meaning log in and start a quest
 
use the latest beta build and let me know
 
i cant see the same error tho or thats not the correct log
 
Tony said:
i cant see the same error tho or thats not the correct log
Click to expand...

It's the same error, it just doesnt have the following line because I never closed demonbuddy I just let it run to see if it would attach but it didn't.

[02:19:06.679 D] Cannot stop a bot when it is not running.
[02:19:06.680 D] Forcing closed all current windows.

--
I've attached the log after closing DB, same error message.
 

Attachments

remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable

restart your pc,
download the DB installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart

download a clean install of DB
run diablo3 and demonbuddy as administrator.
 
I had the same exact problem. Run it how you would normally. Start the first bot and wait until it's actually in-game, then start your second bot. Fixed it for me but it wouldn't detect other instances of d3 unless the prior bot was already in-game and running.
 
Tony said:
remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable

restart your pc,
download the DB installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart

download a clean install of DB
run diablo3 and demonbuddy as administrator.
Click to expand...

Same exact issue,
 
This didn't work for me, I let first bot be in game then tried but it fails to attach it.
 
Interesting indeed.
Care to let me try via Teamviewer?
 
I have the same problem, but if i wait 2 min after each demonbuddy login it works
 
interesting, ill speak to a dev and see if its something that can be helped.
 
yeah, I usually have to wait about 30 seconds to a minute. before that time it just tells me DB cannot find any D3 to attach to. "are you already running the bot?" message
 
odd, like i said ill talk to a dev, no ones on at the moment however.
 
pm me your teamviewer info

io will be around for the next hours
 
You must log in or register to reply here.
Back
Top