Posted March 11, 2020 I've had this happen a couple of times now. I mostly intend this as a "report from the field" versus a "how do I fix my problem." I will have been playing fine for several sessions, but one session, the client becomes insanely laggy. As a more quantifiable description, today, I stood at a door for a good five minutes waiting for it to open. In another case, I spent two minutes waiting to climb a ladder. Later, I spent another two minutes waiting for a door to open. I had a fight where I called the guards twice before I saw my first swing. Once I swung, four guards sprinted to my location and health bars indicated that the fight had been going on for much of that time. I had quit my toons and logged back on. I rebooted my computer. I forced a Windows update and the subsequent reboot. I switched toons and servers. The last thing I did was to put myself to sleep in a bed on my deed. Before, I had either quit or been on toons who weren't on their deed when they went to bed. This time, as soon as I confirmed that I wanted to log out, the screen went black -- and then logged me back in! It did it twice, maybe three times, before I just chose "Quit." Some additional information: I had briefly logged on two toons on two different servers a few hours earlier and had no problems. Now, a few hours later, I log on my main -- but real life quickly interrupted, and I hit "Quit". When I came back, all the above happened. After the final "Quit", I completely powered down my computer and walked away for 2 - 3 hours. When I booted up, all was well again. My guess is that the server was still trying to talk to the previous session and the current session. They client couldn't make sense of the "double talk" except for brief moments when it could assemble enough of the current packet stream to find coherence. (Maybe it had sent a "resynch" to the first stream and while the server was putting that together, it allowed the "real" packet stream to be coherent. Just a guess.) By powering off the computer, I suspect it stopped the NIC from answering even a basic "are you there" (or from the router doing so on its behalf). Once the server reached its timeout point, it closed both connections. After that, the client could once again run normally,. My thoughts. Feel free to critique them. ~Kohle Share this post Link to post Share on other sites