Client locked up me 4 times today in Castle Vacrul: Haunting Presence [raid] and had to be restarted. Never had crashes like that before. It was also affecting other people in the raid with multiple crashes. Please investigate these stability issues. Thanks.
Same thing for us tonight in Castle Vacrul: Haunting Presence [Raid], 7+ "crashes waves" : usually it was 1 player but sometimes 2 or 3 at the exact same time. Crashed myself 3 times ( white screen ) never had raid crashes before 64 bits client. Please fix this issues. Thanks.
There should be some performance fixes included in tomorrow's update (July 12th) Let me know if its still happening after that. Please make sure to include general time it crashed, server/char name, custom UIs used, etc. So we can check crash logs for that specific crash.
We've noticed it still happening after the update on the 12th. Please make sure to point people to this thread to collect info about how and when folks are crashing. We will have the code folks watching this thread.
I've had some odd disconnects during raids before and after the update. The game acts like I am still playing. I can move around and press buttons, but everyone else is standing still or running into walls. The server seems to receive my actions, as I am told that people can see me casting/auto attacking. I don't get kicked to character select, but if I try to camp the client crashes. This happened on Bingulon (Varsoon) Crypt of Vox at around 6:30 PM PST and Miragul's Menagerie: Ar'ticae's Lair at 7:00 PM PST. I usually get these disconnects 2 to 3 times a night. I use DarqUI. I did some digging on the forums/reddit and I found others reporting the same type of disconnect. It seems to be related to the CAX30 or CAX80 Netgear Nighthawk routers. I personally have the CAX30. People said that a VPN fixes the issue for some reason. I set one up and noticed much better ping and have not crashed yet.
Tonight crashs ( white screen ) if that can help. Server : Thurgadin Zone : Castle Vacrul: Haunting Presence [Raid] Date -- Time -- Player Name -- UI 17/07 -- 20:19 UTC -- Sossis -- ProfitUI 17/07 -- 20:22 UTC -- Gaptia -- DarqUI 17/07 -- 20:27 UTC -- Annyta -- DarqUI 17/07 -- 20:29 UTC -- Agarth -- ProfitUI 17/07 -- 20:49 UTC -- Amyrion -- Default
Make sure those people you listed have updated their custom UIs..especially DarqUI, although I understand Darq is also updating Profit. There were known issues involving custom UIs, DarqUI particularly, that needed to be patched. I experienced some of the same issues. They disappeared when I went back and updated DarqUI. Not saying there aren't ancillary issues with game platform, but start there first.
Crashing too in this zone. Alertlog : Code: build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeMeshGeometryNode.cpp(261): VeMeshGeometryNode resource 'cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l1.draw' failed to load" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeMeshGeometryNode.cpp(4570): Error loading VeMeshGeometryNode lod 1 resources. You should never see this error. RenderMesh: cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l1.draw" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(1033): VeAnimMeshGeometryNode resource 'parent vemeshgeometrynode lod' failed to load" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(1006): VeAnimMeshGeometryNode resource 'cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l1.draw' unloaded unexpectedly" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(10916): Error loading VeMeshGeometryNode lod 1 resources. You should never see this error. RenderMesh: cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l1.draw" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeMeshGeometryNode.cpp(1846): Error loading VeMeshGeometryNode resources. You should never see this error. RenderMesh: cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l0.draw" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(1033): VeAnimMeshGeometryNode resource 'parent vemeshgeometrynode' failed to load" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(1006): VeAnimMeshGeometryNode resource 'cooked/characters/ec/pc/kerramale/scenes/optimize/kerramale_lod0.skeleton' unloaded unexpectedly" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -57.93 449.18" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAnimMeshGeometryNode.cpp(4839): Error loading VeAnimMeshGeometryNode resources. RenderMesh: cooked/characters/accessories/wearable_items/profession_hats/assassin/assassin_01/scenes/vahshir_male/head_l0.draw" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc="-25.11 -56.43 444.18" performance="3" alert="G:\live\eq2\game\Client\src\GameScene.cpp(6025): Loading UI resources timed out after 10 seconds while still had pending examine requests error# 32" build="DGCBuild=16822L" version="DGCVersionString=2022/7/8 12:44:44" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_dun_vacrul_raid_02" loc=" 34.49 -43.91 473.43" performance="3" alert="G:\live\eq2\framework\scenegraph\VeAppearance.cpp(8154): ERROR - Can not link appearance multiple times." Debuglog : Code: [0415/013402.529:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/025753.309:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/025753.992:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/132755.501:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/132755.886:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/135613.853:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/135614.571:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/174936.682:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/174937.377:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/193042.746:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/202650.398:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/202651.473:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/204029.147:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/204712.215:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/204712.963:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0415/235437:ERROR:cookie_monster.cc(1569)] Found 1 duplicate cookies for host='daybreakgames.com', with {name='_gat', domain='.daybreakgames.com', path='/'} [0415/235656.412:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0416/154513.729:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [0416/154515.040:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
New raid, more crashes ( white screen ) : Server : Thurgadin Zone : Castle Vacrul: Haunting Presence [Raid] Date -- Time -- Player Name -- UI 19/07 -- ~20:05 UTC -- Gaptia -- DarqUI 19/07 -- ~20:33 UTC -- Krorr -- ProfitUI 19/07 -- ~20:47 UTC -- Bheru -- ProfitUI 19/07 -- ~20:50 UTC -- Drakke -- DarqUI 19/07 -- ~21:03 UTC -- Ceikolit -- DarqUI 19/07 -- ~21:30 UTC -- Bheru -- ProfitUI <= 19/07 -- ~21:30 UTC -- Darkzero -- DarqUI <= 3 players crashed at the exact same time. 19/07 -- ~21:30 UTC -- Ceikolit -- DarqUI <= P.S : all UIs are up to date.
BTW Gaptia is using ProfitUI with part of DarkUI (darqui_custom_iconbar.xml, darqui_custom_harvesting.xml, darqui_custom_gearbuff.xml, darqui_custom_transport.xml, eq2ui_custom_ToggleBuffing.xml) and DrumUI (DrumsUI_TargetCasting.xml)
We're still looking into this. Since the client isn't crashing, we don't have an immediate client dmp to look at. From what I'm seeing from feedback, the client is getting in a state where it times out communicating with our server and gets in a "linkdead" state. Does this happen in other raid zones?
Happened once while killing trash in den solo... We get people having white screen in others zones too, but not causing problem with boss script
Yes we got the crashes in other raids zones too ( for exemple yesterday we did Castle Vacrul: Thirst for Power [Raid] to get access for some returning players : 5-6 white screen crashes during the zone, different players ) In Heroic zone, i remember some random white screen crashes during The Merchant's Den [Heroic II] Challenge but not in every zone clear, seem way less frequent than in raid zones.
Are you using the streaming client (you will see the loading dragon icon occasionally while playing, uses assetcache folder) or full client (uses PAK files) when this happens?
Not sure if anyone else noticed it tonight when they were locked up, but during the Mayong fight when he put up his purple ward after a script fail, I noticed massive lag and my window locked up. Had no issues before that point with lag and no issues after the ward had passed. This was Scrappz, on Maj'Dul around 10:30-ish pm eastern time with ProfitUI
Here's a thought, how about get your raiding ppl to stop using custom uis for a while. Not just a few minutes but for a couple of weeks delete all of them, darq profit, eq2 maps (thats a ui in and of itself), also a.c.t. and that no-no raiding program, think its called ogre? Try going without and see if you still crash. Every time I use /browser to look up something on wiki i crash within a few minutes, no ui involved. Remember when Daybreak cut off all custom uis to test a server problem but nothing ever came from it. Why make them do that again? The game can be played without all the extra.
This is the closest thing I can find to a thread about the Mayong fight being plagued with crashes, so I'll post here. Our raid alliance is working on Mayong, and we were on schedule to win this fight today. Everyone was doing a great job, we had the rhythm and mechanics worked out and we had plenty of time to get it done. Then we had two people go link dead. We managed to recover...but then the main tank and main tank healer went linkdead and the fight auto-wiped us due to script failures related to those crashes. We had done the rest of the zone with nobody crashing. It seems this fight is crashing people, and it's very frustrating. We should have had this mob down today...and the raid deserved this win. They did a fantastic job, and they recovered well the first round of crashes. Please fix Mayong. And for the person talking about UI...at least two of the people in my raid that crashed today use Default UI, so I don't think it's that.
I am not convinced yet that custom UI is to blame. Anything you guys see that might be a commonality would be great. It is not producing a crash log on our end but it might in your logs folder in a file called "client_log 6-30-2022 16.17.23.txt" or something similar. You might be able to get some info in the last few entries into those files.
