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

"Network Disconnect" "The game connection has been lost; your client has been disconn

P

pimpampum

Member
Joined
Nov 29, 2012
Messages
769
Reaction score
23
Full log attached.


I'm unable to identify the reason this is happening, it happens to other users too. It could be on blizzard's side too.

Plugins used:

Trinity .2.13
SimpleFollow (Last Version Available)
YAR.


Whenever this happens, something is avoiding yar to close D3 and Db due to inactivity. It will just stay with the error window till it is manually closed.

I could be wrong, but ain't there something to avoid this issue ? It wasn't happening previously, yet disconnects have always happened.
 

Attachments

also you should use the release build
 
Thanks for the answers. I'll try to use Release Build and a fresh install.

Already use R-Yar; forgot to write the R :)
 
disable SimpleFollow and R-Yar and let me now
 
Tony said:
disable SimpleFollow and R-Yar and let me now
Click to expand...

Can't do that Tony. Was expecting you to ask me to though!

If I disable Simplefollow I would have to change every trinity setting to normal values. And that would take a lot of time. Not to mention disabling yar would mean having to manually run both 10 d3 and 10 db, without the option of resizing the windows to see what is going on on each bot. No thanks!
 
pimpampum said:
Can't do that Tony. Was expecting you to ask me to though!

If I disable Simplefollow I would have to change every trinity setting to normal values. And that would take a lot of time. Not to mention disabling yar would mean having to manually run both 10 d3 and 10 db, without the option of resizing the windows to see what is going on on each bot. No thanks!
Click to expand...

We're asking you to temporarily disable it then individually add it in again so we can see what's causing the problems. :/
 
iCKR said:
We're asking you to temporarily disable it then individually add it in again so we can see what's causing the problems. :/
Click to expand...

I totally understand it! Reduce the variables to identify the problem. I've done that before.

But, as you probably know Ickr, every plugin normally asks for a quite specific configuration to run. As in, in order to run simplefollow I have to change attack radius on Db for the follower bots to minimal in order to avoid them going on their own. Setting them back to normal requires changing that, among other things like bot builds, monster power, loot settings or profile used they all change. That's the main reason I refuse to do it.

Here is a log without simplefollow. I set two bots without it, and "luckyly" one of them had the disconnect. So, I guess simplefollow can be taken out of the equation.
 

Attachments

try disabling Yar now,or make a second installation without Yar
 
Lootjunkie said:
Care to share the solution?
Click to expand...

If only I knew....I spent the whole sunday evening doing this:

1) Format SSD drive (system drive). Install the over 300 updates. How many are necesary for them to determine a fucking service pack should help? Also reinstall and update all drivers from peripherals.
2) Disable MOBO autoinstalled LAN drivers from the Bios.
2) Reinstall D3 from scratch. ( If you don't wanna go through the format, I'd advise you to delete hidden dirs Battle.net and Blizzard on programData before reinstalling D3.)
3) Redownload DB and all plugins/profiles. Set an independent installation for each dB. (Yar is common).
4) Reinstall dependencies (Visual c and .net framework) Update them.
5) Send Avast AV to hell.
6) Create exceptions on firewall for all DB's. (Were already there on the last install, but sometimes the system does ignore exceptions, not sure why)
7) Block agent.exe and updater.exe and errorreporters from outgoing connections on firewalls.
8) Open router ports for Db (there's a post around where a port is recommended). Also opened Simplefollow used ports, just in case.
9) Disable manual overclock and set MOBO automatic OC.



I did 3) because sometimes I saw this weird Db error " could not open complied assemblies X file cause another program is already using it. " It didn't happen again, yet the "Could not read bytes from X " is still everywhere on the logs.
I also did a memcheck and a burn test and memory is fine.

On 9) I have no fucking clue why, but having lost over .500 Mhz on this "underclock", CPU usage is lower now, and I'm not reaching 100% usage ever, while before I was often on 100%. This could also be the reason some programs were misbehaving, the comp starts working really wrong when 100% cpu is reached.
So far so good. I assume some files got corrupted and were causing the often crashes, which ones? I don't know.

I'm probably missing some stuff. All in all, I've been two days without the network disconnect issue and without the demonbudy crashing ---yar not restarting issue. If I had to make a guess, I'd say 2-4-6-9 are the most likely to have helped, but honestly, I'm not sure.
 
Last edited:
i have a lot of DCs with rixx yar

but whan i roll back to the old non-rixx yar - everything become fine
 
You must log in or register to reply here.
Back
Top