Since last week, I’ve been having a very odd issue. My EQ client locks up but I can move around but can’t cast or attack, the spell bar is grayed out and I will see the message that the command is not available at this time or that I am casting already. It happens at the most inconvenient time, during raids when activity spikes like a raid event starting or lots of adds pop. Initially I thought it had something with GINA so I turned off logs and closed GINA. That didn’t help. So I cleared the logs folder and copied my backup ini files that were working before. That didn’t fix it either. Then I started looking at my computer, made sure that virus scan ignored the logs directory, stopping all the unnecessary apps that startup when windoze starts. I also made sure I have the latest drivers etc. What’s strange is that I use other computers to play eq and all of them are having the same issue all of a sudden. Later it dawned on me that it might be related to the quest overlay window. When NoS was released I had one toon that crashed all the time and I think one of the quests on the overlay windows is bugged or something. After I disabled some quests, it was loading fine again. What’s new is that I just finished the NoS quests and there are no more quests on the quest overlay window. I searched the forums to see if anyone faced this issue but didn’t find any. Anyone having similar client crash issues?
I see this on the "Sky" file in the logs directory. 2023-01-27 19:04:14SkyERROR: Missing section [ColorMap-eviltree-0] 2023-01-27 19:04:14SkyERROR: Missing section [ColorMap-xorb-0] 2023-01-27 19:04:14SkyERROR: Missing section [ColorMap-grelleth-0] 2023-01-27 19:04:14SkyERROR: Missing section [ColorSet-grelleth0]
If it is the task overlay, look at this thread: https://forums.daybreakgames.com/eq...overlay-activelist-cause-client-crash.287661/
I've been having similar issues, just came back on a fresh install haven't played in years, after 20-60 mins my character bugs out and I have to completely close the client and restart. I've since given up on trying to solve the issue, have spent hours trying to find the cause.
I had this happen to two different characters/accounts today on Bristlebane. Once in guild hall after buffing and during (?) a druid port spell (druid cast the spell porting party, but was herself left behind and locked up) and a second time many hours later in NOS Shadeweaver thicket on a mage after about an hour of killing there. I don't recall the last time i had this happen, so it seems it's something new/recent. It happened just as the OP describes. Spell bar lock up, no one else is moving, but you can move around. Probably some disconnect with server issue. I was able to /q but couldn't zone.
Experienced a disconnect and had to log back in. Then went to zone from GGH to Lobby and client completely locked up. Had to end task through windows task manager.
Clearing the taskoverlay on the ini fixed it for a while. Now my client is starting to lock up again. Here is what I see on the dbg file. [Thu Feb 02 20:14:21 2023]00688:Memory: Load: 25, Total Phys: 32560, Avail Phys: 24184, Total Page: 34608, Avail Page: 24284, Total Virtual: 134217727, Avail Virtual: 134211752, FreeBlocks: 132002353,1520152,644508,34894,2753,2047,487,365,244,143 [Thu Feb 02 20:14:21 2023]00689:MaxTextures: 58062k, CurrentTextures: 57881k, HighQualityTextures: 43605k [Thu Feb 02 20:15:35 2023]00209:Lost D3D device. Waiting for reset.
Is your video driver up to date? Did you recently update the driver after which you started experiencing the issue? Roll back to a previous version. Reinstall DX9: https://www.microsoft.com/en-us/download/details.aspx?id=8109 Do you use a Bluetooth audio device or built-in monitor speakers? Make sure it does not shut off/low power/disconnect as EQ does not handle device removals.
I have latest video driver, didn't update until I ran into this issue. I turned off bluetooth. After reinstalling DX9, I see the following errors. Video is not happy it looks like. Code: [Fri Feb 03 16:17:53 2023]00634:Memory: Load: 25, Total Phys: 32560, Avail Phys: 24180, Total Page: 34608, Avail Page: 24576, Total Virtual: 134217727, Avail Virtual: 134211987, FreeBlocks: 131802018,1760126,603201,30917,8610,2047,573,314,206,200 [Fri Feb 03 16:17:53 2023]00635:MaxTextures: 51574k, CurrentTextures: 51574k, HighQualityTextures: 48487k [Fri Feb 03 16:17:54 2023]00200:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:17:54 2023]00201:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:18:02 2023]00202:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:19:03 2023]00636:knockout 3 [Fri Feb 03 16:19:41 2023]00637:knockout 3 [Fri Feb 03 16:20:04 2023]00638:knockout 3 [Fri Feb 03 16:20:25 2023]00203:D3DXCreateTextureFromFileEx() failed to create texture zapmuzn.dds for particle system. [Fri Feb 03 16:20:50 2023]00639:knockout 3 [Fri Feb 03 16:21:19 2023]00640:knockout 3 [Fri Feb 03 16:21:33 2023]00641:knockout 3 [Fri Feb 03 16:21:33 2023]00642:knockout 3 [Fri Feb 03 16:21:43 2023]00204:D3DXCreateTextureFromFileEx() failed to create texture flamed.dds for particle system. [Fri Feb 03 16:21:51 2023]00643:knockout 3 [Fri Feb 03 16:21:55 2023]00644:knockout 3 [Fri Feb 03 16:22:03 2023]00205:D3DXCreateTextureFromFileEx() failed to create texture fire01.dds for particle system. [Fri Feb 03 16:22:04 2023]00206:D3DXCreateTextureFromFileEx() failed to create texture new_flame.dds for particle system. [Fri Feb 03 16:22:04 2023]00645:knockout 3 [Fri Feb 03 16:22:11 2023]00207:D3DXCreateTextureFromFileEx() failed to create texture finedustsp501.dds for particle system. [Fri Feb 03 16:22:11 2023]00208:D3DXCreateTextureFromFileEx() failed to create texture finedustsp501.dds for particle system. [Fri Feb 03 16:22:12 2023]00209:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:22:12 2023]00210:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:22:19 2023]00211:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:22:19 2023]00212:D3DXCreateTextureFromFileEx() failed to create texture acid1.dds for particle system. [Fri Feb 03 16:22:27 2023]00646:knockout 3 [Fri Feb 03 16:22:36 2023]00213:D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system. [Fri Feb 03 16:22:54 2023]00647:knockout 3 [Fri Feb 03 16:23:05 2023]00648:knockout 3 [Fri Feb 03 16:23:36 2023]00649:knockout 3 [Fri Feb 03 16:24:09 2023]00650:knockout 3 [Fri Feb 03 16:24:23 2023]00651:knockout 3 [Fri Feb 03 16:24:37 2023]00652:knockout 3 [Fri Feb 03 16:24:56 2023]00653:knockout 3 [Fri Feb 03 16:25:10 2023]00654:knockout 3 [Fri Feb 03 16:25:18 2023]00655:knockout 3 [Fri Feb 03 16:25:32 2023]00656:knockout 3 [Fri Feb 03 16:25:34 2023]00657:knockout 3 [Fri Feb 03 16:26:00 2023]00658:knockout 3 [Fri Feb 03 16:26:04 2023]00659:knockout 3 [Fri Feb 03 16:27:37 2023]00660:*** DISCONNECTING: Exit command received.
The sky and that log are "normal" handled missing texture errors that have been around forever. My debug file shows everything yours does too and I have no issues. The problem line in your log above was this showing that something EQ was using was disconnected and EQ does not catch and handle a reset which causes a client crash or freeze. Code: [Thu Feb 02 20:15:35 2023]00209:Lost D3D device. Waiting for reset. If it's working fine now, could have been corrupted video driver or corrupted DX9 files. Not sure if disconnected audio device throws the same error but I know EQ does not handle that and the client will lock up. The monitor as an audio device will also cause an issue if the monitor is allowed to sleep/low power mode as that will disconnect the audio device. If it's because you keep getting corrupted task overlay values, will have to wait until the Feb patch to see if it goes away.
I had video card overheating problems recently. Locking up, client crash and sometimes the system would just reboot. Replaced that card with a spiffier one. It's worth looking at even as a dust buildup issue. It took me a bit to accept the reality of the overheating.
I am either unlucky or there’s a client issue. This is happening on four computers with different video cards (nvidia and the embedded intel). It is frustrating as hell. Sure hope this gets fixed on the next update. I’ve been searching around and found this article. Lost Devices (Direct3D 9) - Win32 apps | Microsoft Learn Handle device removed scenarios in Direct3D 11 - UWP applications | Microsoft Learn
Others had recent similar issue and the fix was to update the graphics driver. Sounds to me like some sort of update happened which altered those drivers
Game is broken and you pay premium cash for it.. An I9 13xxx-serie and a 4090 with 64GB RAM should not stutter in PoK.. yet it does. Devs simple does not care.. they want the $$$$$ nothing else is relevant.
Add x6 for box.. then another x64 for raid. =D 1 toon does not get you far at all.. you CAN't solo on 15usd month.. you NEED 6 accounts that costs 15usd EACH! I know a lot of EQ players that thinks as me... game costs to much, simple is that.. should be a dollar month, not more. (Think about you CAN'T! solo the game at all..) Prove that YOU can SOLO NoS =) Please! Show me! No Raid gear! Just regular Tier 1 gear that YOU SOLOED BY YOURSELF! within the latest EXPAC NOS!
Is this still happening? If so please DM me your Logs\dbg.txt file after it happens. It's very hard for DX11 to encounter a device lost error because it virtualizes the display device. It's one of the nicer stability improvements over DX9. Can you tell us more about your display setup? Do you have one display monitor? Do you use windowing software? Do you use a KVM switch?
Generally being able to move around but not take actions means a disconnect between you and the server. If it was a graphics driver or client crash you wouldnt be able to move. Eventually the client will crash but when you can move around it hasnt yet.
