Since the latest patch on Wednesday 02/17. When zoning the game seems to freeze completely until I close it out and relaunch. Once i relaunch I will have now zoned into the new zone. My guild has also reported this happening to them too.
This is happening to me as well since the patch. The weird thing is it doesn't happen all the time. And the account that's on my best computer it never happens to. I should say this is on Aradune where it's happening.
We have someone that has been experiencing this on a consistent chronic basis, heck he even just biult a new computer and was still seeing it. We aren't 100% sure if this is why it has stopped for him, but he changed a UI window that was kicking up some errors in the uierrors file, and since then he hasn't experienced a hang on zoning since. It might be worth checking into your ui errors and seeing if you have anything unexpected in there.
I use the default UI and had no issues before this patch. I checked just in case and no errors in any of my UIErrors.txt files.
Super frustrating trying to play since the patch. Having login issues, when I finally get logged in the game hangs when zoning, so I have to kill it and have more login issues. Can't believe more people aren't having these issues? I was perfectly fine before the patch. Getting server is not responding a lot when trying to log in from character select.
A year or maybe two ago, there was a period where a group or two of us were farming old raids, and I'd have super long zone times. I'd eventually zone if I left it there, but it was a very long, abnormal amount of time where I might as well have just restarted the client (and occasionally did), and it didn't happen to the others. It wasn't consistent outside of those times though. I felt like it was only when I had 2-3 clients running at once and was moving to a new instance (might have had old expedition active still during these times, idk). I believe it'd only happen to my main's client. It could have just been a coincidence though. It eventually stopped happening without having done anything different. Although, I also don't run multiple clients very often. Now, I have often seen people hang during guild raid events (or, at least, zoning was taking so long their impatience led them to restarting the client), but that might have just been server lag since it seems to worsen just by having a raid of people exist. I've had a few instances of extra long zone times where I wondered if I'd ever zone on laggy nights as well. But, unfortunately, I personally haven't seen or heard from anyone of anything different with the latest update specifically.
Started happening to me since the patch, too - instead of crash to desktop, it just seems to hang, and need to kill the process from Task Manager.
When zoning and you freeze up like that. In your EQ folder there is a Log directory and in that directory there is a file named dbg.txt. Scroll to the bottom and read the last 20 lines or so. That will usually tell you why it hung. Post those lines here.
So the dbg.log file shows the following: [Fri Feb 19 14:26:38 2021]00744:Networking: Connection Closed [0] with 0 pending bytes. [Fri Feb 19 14:26:38 2021]00745:Stopping world display. [Fri Feb 19 14:26:38 2021]00746:Attempt to send message 28104 on a void connection. [Fri Feb 19 14:26:39 2021]00747:Beginning EnterZone block. [Fri Feb 19 14:26:39 2021]00748:Calling WorldAuthenticate. Countdown is 4 [Fri Feb 19 14:26:39 2021]00749:Networking: using port [60049]. [Fri Feb 19 14:26:39 2021]00750:Networking: Connection Established [1] [Fri Feb 19 14:27:39 2021]00751:*** WorldAuthenticate. Error connecting to eqworld-03.everquest.com:9000 [clientisconnectReasonConnectFail,serverisconnectReasonNone] [Fri Feb 19 14:27:39 2021]00752:Networking: Connection Closed [0] with 0 pending bytes. [Fri Feb 19 14:27:39 2021]00753:*** ERROR: WorldAuthenticate has failed after attempting to connect. [Fri Feb 19 14:27:41 2021]00754:Calling WorldAuthenticate. Countdown is 3 [Fri Feb 19 14:27:41 2021]00755:Networking: using port [56214]. [Fri Feb 19 14:27:41 2021]00756:Networking: Connection Established [1] [Fri Feb 19 14:27:41 2021]00757:WorldAuthenticate: Initiating Login. [Fri Feb 19 14:27:41 2021]00758:WorldAuthenticate. I got a message of type 0x690 (1680). [Fri Feb 19 14:27:41 2021]00759:WorldAuthenticate. I got a message of type 0x6fca (28618). [Fri Feb 19 14:27:41 2021]00760:WorldRPServer message: server name aradune [Fri Feb 19 14:27:41 2021]00761:WorldAuthenticate. I got a message of type 0x64ca (25802). [Fri Feb 19 14:27:41 2021]00762:WorldAuthenticate. I got a message of type 0x694e (26958). [Fri Feb 19 14:27:41 2021]00763:WorldAuthenticate. I got a message of type 0x7f1e (32542). [Fri Feb 19 14:27:41 2021]00764:WorldAuthenticate. I got a message of type 0x2668 (9832). [Fri Feb 19 14:27:41 2021]00765:WorldAuthenticate. I got a message of type 0x25ca (9674). [Fri Feb 19 14:27:42 2021]00766:WorldAuthenticate. I got a message of type 0x2ad7 (10967). [Fri Feb 19 14:27:42 2021]00767:WorldAuthenticate. I got a message of type 0x390e (14606). [Fri Feb 19 14:27:42 2021]00768:WorldAuthenticate. I got a message of type 0x72f (1839). [Fri Feb 19 14:27:42 2021]00769:WorldAuthenticate. I got a message of type 0x322c (12844). [Fri Feb 19 14:27:42 2021]00770:WorldAuthenticate. Access granted. [Fri Feb 19 14:27:42 2021]00771:Check 1x. 0x673d46c3 [Fri Feb 19 14:27:42 2021]00772:Waiting to connect to zone... Character Rabidtiger [Fri Feb 19 14:27:43 2021]00773:Zone Connect -- 0 -- Received MSG_ZONE_ADDRESS [Fri Feb 19 14:27:43 2021]00774:Zone addr [eqzone-60.everquest.com:1445] received... [Fri Feb 19 14:27:44 2021]00775:ZONING [Fri Feb 19 14:27:44 2021]00776:Networking: Connection Closed [0] with 0 pending bytes. [Fri Feb 19 14:27:44 2021]00777:Networking: using port [56215]. [Fri Feb 19 14:27:44 2021]00778:Networking: Connection Established [1] Also additional sleuthing has confirmed that everyone having this issue in my guild lives in Texas and has Frontier as their ISP.
I also live in Texas and have Frontier as my ISP. It has seemed to stop this afternoon. Still having some login issues though.
Port 9000 is the incoming port on DBG server, in the logs the client is outgoing using port 60049, and successful using port 56214. Maybe ISP is blocking ports over 60000.
Im in North Texas with Frontier fiber and im having very slow load up for launch, ill finally make it to server screen to be booted saying no connection error, disconnected from server, sometimes ill make it to the char screen then booted. if im in game if i zone my screen locks up completely and ill have to control alt delete and ill have to reboot the comp from there bc task manager wont work bc eq is froze in the background. it took me close to 30 mins to get my sons mag in game from his comp. this has happened since the 2/17 maintainence patch.
This is the same symptoms I'm having. The work around i have for when EQ is frozen and taskmanager opens behind it.. I hit ctrl-alt-delete then click task manager, then i press the down arrow once, then the delete key once. that will close EQ because it's non-responsive. Then i just relaunch EQ and log back in. Still frustrating.
I'm not having any issues this morning. So, knock on wood, hopefully Frontier has it fixed, whatever the problem was.
As of early early early this morning i'm not having any issues. i checked my logs on all 3 comps and they all showed out going ports under 55000. whatever or whoever did what it seems to be working now. i'm going to test logging in again later today to see what happens.
As of today, the server screen will not allow me to log into FV server, just hangs there and times out. I am able to log into other servers though, its a population issue i believe. Daybreak has downsized on server memory? and this is what we get?
