Like the title says, AGAIN I'm getting disconnected, teleported all over the place, rubberbanding, basically crap that's making the game unplayable despite my connection being perfectly fine. Sometimes I can sit in Haven for like 2 hours just chilling and have 3 bars all the time, but as soon as I decide to do LD, I drop to 1 bar and the game becomes completely unplayable, with a kick from the server only mere seconds later with no reason given. No "You have been disconnected from the server." No "Either there is a temporary network outage blah blah blah so on and so on." Just the title screen as it would look if I logged off from the game on my own.
Here we go again with the lag despite having a perfectly fine internet connection.
Sat, 03/23/2013 - 00:48
Sun, 03/31/2013 - 16:28
#2
Ugh. Yup.
I'm having this exact same problem. Randomly, my game will drop to one red bar when it's normally at four. I rubberband around, and die. Once in a while I disconnect.
This isn't in lockdown, it's in PvE. Only occurs when I'm playing with other players. Solo, I almost NEVER get this issue.
My internet is fine. I monitor my connection, signal strength, ping, etc. and it's fine. I play four other MMOs and don't have this problem. The only time I've experienced anything like this is when attempting to play an MMO on an overseas server
So @Helios, if you're still here, I've got a question on submitting a bug report. I can only assume you mean in-game, correct? And that takes a diagnostic snapshot? Is that snapshot taken when you press F5 (or whatever button you press in Spiral, I forget offhand) or not until you submit it? Because, for me, at least, it only lasts maybe 5 to 10 seconds. Not enough to type out an explanation as to what's going on.
Sun, 03/31/2013 - 18:54
#3
Yes, I mean filing an in-game
Yes, I mean filing an in-game bug report. When the report is made both a snapshot of the current game state and a historical view of the current client session is logged. It's often necessary to see the game's behavior leading up to an issue, so the historical information is very useful. Another useful tactic is, if you can anticipate a problem, to keep the message ready for a quick paste from the computer's clipboard. You can fire a report off very quickly just by pressing F2, Ctrl+V, Enter.
Sun, 03/31/2013 - 19:28
#4
Awesome.
Thanks Helios.
Just as one last pester, should we send one every time this happens or is once enough?
I know this may be hard to pull off during Lockdown, but could you please try submitting a bug report when the connection problem hits? This way we can have a look and see if there is any funny business going on in the client when you wind up with the disconnection message.