Debugging Disconnects

[Tin]

the fps has nothing to do with disconnect (well unless your fps drops below 10 I guess)

How do you know ? - for some this was the fix.

- only thing I know is if I launch my AH toon with Isboxer I some times disconnect, but it never happens if I use the blizzard launcher. Where the global config.wtf file has FPS set to 60/30

and other change is global config.wtf use D3D12 and Isboxer D3D11_Legacy

[JohnGabriel]

For me it does not happen solo only when logging in all at once. It disconnects two windows, always two, but always seemingly random windows.

I think all this started about two weeks ago when blizzard updated the UI.

[Tin]

about a month ago for me now - just after a small weekend update/patch from Blizzard.

[Moorea]

How do you know ? - for some this was the fix.

like who ? the only place were I ever heard about this was that spam nonsense link you posted in my thread

if the fps had anything to do with it there would be credible source for it and/or it'd be mentioned in blizzard's note about the issue which it isn't (not to mention it doesn't make any sense when you think about what a DC is, or even that it happens on the character selection screen, idle)

[bgarisn]

What region? EU, US, etc.
Do you guys all have an authenticator attached? (phone or fob)
Do you have SMS Protect enabled?
Are your accounts all on the same battle.net account or across multiple emails?
Are you playing through a proxy? (wtfast counts as a proxy)
Are you using wireless, native ethernet, or USB-to-ethernet adapter?
What ISP and type (cable/dsl/fiber/LAN) are you using?
What OS are you running?
Any antivirus apps installed (aside from Windows Defender if you're Win10)?

Probably more but the above are usually the most relevant in showing some clustering of data points. I'd ask about datacenter/routing but I'm not sure how to figure that out anymore as it's been years since I've had any of those issues.

Region: US-Dalaran
Authenticator: Yes - dongle
Bnet: All 5x accounts are on same bnet
Proxy: None
Network: Wired ethernet
ISP: WoW (cable)
OS: Win10
AV: Norton

I'm still trying to figure it out. and I'll try to implement what Tin suggested.

Appreciate the insight!

[MiRai]

If it is WOW51900319 Error Code you all getting - I have that too - https://eu.battle.net/support/en/article/112213

Some have there Max background FPS set to 30 and Max Forground FPS set to 60 - and that fix the problem for them.

Isboxer do overrite this setteings and set them back to 0 in your .WTF file if you let Isboxer control your FPS on swap.

SET maxfps "0"
SET maxfpsbk "0"

(Are they new as they are last in my .WTF file and never seen them before ?)

Using only the in-game limiters, I am still seeing a disconnect from time to time.

[Tin]

Using only the in-game limiters, I am still seeing a disconnect from time to time.

Can only tell you that my experience is that after I changed to 60/30 FPS. I have no disconnect for over a week now, when I`m playing single player using the Blizzard launcher. But getting random disconnect when I`m using inner space as a launcher.

[Ellay]

Have not made any changes but last 3-4 days have not had any disconnects.

[Pocahuntess]

I am definitely still getting these. 1 or 2 random disconnects on login. Thought it was just my system specs.

[MiRai]

Can only tell you that my experience is that after I changed to 60/30 FPS. I have no disconnect for over a week now, when I`m playing single player using the Blizzard launcher. But getting random disconnect when I`m using inner space as a launcher.

I understand, but there was also a period of 1-2 weeks where I didn't see any disconnects, and then, boom, they're back after 8.2 was released. I also only begin to receive the disconnects in the late afternoon, as people are coming home and logging in, further populating the servers. For example, today alone I've logged in 3-4 times as I level a new set of characters, and I haven't been disconnected yet, but I imagine when I log on later tonight, I will, once again, begin to receive disconnects upon logging in.

So, it's probably safe to say that it's simply an issue with Blizzard's servers and some authentication change they made recently.