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

multiple diablos , 1 demonbuddy

you cant, each session of diablo 3 needs to be attached to 1 session of demonbuddy in order to function.
 
then you need to start 3 diablo 3 clients, with 3 demonbuddy clients.

Start D3, login, Start Demonbuddy
Start D3, login, Start Demonbuddy
Start D3, login, Start Demonbuddy.

at that point each demonbuddy client is going to be attached to each diablo 3 client that was started before it.
 
then you need to start 3 diablo 3 clients, with 3 demonbuddy clients.

Start D3, login, Start Demonbuddy
Start D3, login, Start Demonbuddy
Start D3, login, Start Demonbuddy.

at that point each demonbuddy client is going to be attached to each diablo 3 client that was started before it.
i love you
you should paste this or allow me to paste it in one of the threads above. the faq had everything except htis unless i missed it
 
you shouldnt have problems tho cause there is a process selector for more that one processes
 
you shouldnt have problems tho cause there is a process selector for more that one processes
it works the way codename g mentioned

when i load 2 diablos and tryt o run db yeah it lets me pick the process but then i cant run db again for the other d3

it worked tho start d3, db, start d32 , start db


can u upgrade from 1yr to lifetime session? :S
 
this thread just killed any faith in humanity i might have had left.
 
it works the way codename g mentioned

when i load 2 diablos and tryt o run db yeah it lets me pick the process but then i cant run db again for the other d3

it worked tho start d3, db, start d32 , start db


can u upgrade from 1yr to lifetime session? :S

I've been having this problem also with the most recent, post 12/18 patches. Before this, I could load up 2+ D3s, then load up DBs. Now, I load 2 D3's, then I load up DB, the first DB I can select which process to bind to, but when I load up the second DB it says it can't find any running processes.

Opening one D3, then DB, then another D3, then another DB, etc works fine though.
 
I've been having this problem also with the most recent, post 12/18 patches. Before this, I could load up 2+ D3s, then load up DBs. Now, I load 2 D3's, then I load up DB, the first DB I can select which process to bind to, but when I load up the second DB it says it can't find any running processes.

Opening one D3, then DB, then another D3, then another DB, etc works fine though.

I got that, then just closed out of the DB with issues, re-open and it works.

Seems to only happen in one instance of opening DB with multiple D3's open.
 
Back
Top