[SOLVED] No Errors but too frequent Disconnection to Login Screen while fighting

EDIT: Disabled lockstep seems to solve the problem

I came back to PoE since a couple of years away. Downloaded the new client, installed and got in.
Left town to begin slaying monsters, but after 10-60 seconds: bang, back to login screen, no error message at all. Never happened before.

Searched for a solution, someone said instance could be bugged, had to reset. So I did it and really helped, now I could play around 5 minutes. But too good to be true, after that time I was back to login screen again.

Importante to note that nothing happens if I stand still in a town OR in a instance, ONLY happens while I'm fighting.

Windows 10 fully updated.
Graphic card driver updated.
No problem with a single other game ever.
I am in the same city as São Paulo gateway.


WinMTR to br.login.pathofexile.com (São Paulo), run for 5 minutes or so:


Spoiler
"
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| MyRouter.Home - 0 | 503 | 503 | 0 | 0 | 10 | 0 |
| 175.251.40.189.isp.timbrasil.com.br - 0 | 503 | 503 | 6 | 10 | 74 | 7 |
| 10.216.250.105 - 1 | 495 | 493 | 8 | 10 | 44 | 11 |
| 10.216.250.21 - 0 | 503 | 503 | 8 | 13 | 50 | 10 |
| 10.223.255.113 - 0 | 503 | 503 | 8 | 13 | 49 | 16 |
| 10.223.238.85 - 0 | 503 | 503 | 8 | 11 | 50 | 9 |
| as36351.sp.ix.br - 0 | 503 | 503 | 9 | 10 | 47 | 9 |
| ae5.dar02.sao01.networklayer.com - 0 | 503 | 503 | 10 | 11 | 47 | 10 |
| po2.fcr01b.sao01.networklayer.com - 0 | 503 | 503 | 10 | 11 | 46 | 10 |
| 36.84.39a9.ip4.static.sl-reverse.com - 0 | 503 | 503 | 10 | 11 | 50 | 10 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider




Last edited by arkiluz on Apr 22, 2016, 7:09:36 PM
Last bumped on Apr 22, 2016, 7:09:08 PM
Ok, disabling lockstep seems to have solved.

Report Forum Post

Report Account:

Report Type

Additional Info