Fixed Internally Launcher Play button broken after today's update (June 28th)

One of my accounts is having this issue.

Windows 7 Professional x64
32GB DDR3
i7-2700k (3.50GHz Quad Core)
GeForce RTX 2060 Super 4GB

Yeah all my AMD CPU systems seem fine. Sure it's a coincidence the one Intel processor I have isn't working.

OS Event logs show nothing going on that would indicate a potential issue from the OS/hardware.

Took this from \Daybreak\EQ2\alertlog.txt (I deleted it and let it rebuild as it looks like it's stating it's June 24th when it's the 28th. but it repeats this numbering when relaunching from executable instead of patcher) (I have no discs labeled as G:\)

build="DGCBuild=16796L" version="DGCVersionString=2022/6/24 9:48:16" build_type="USER OPTIMIZED" ls_address="none" zone="exp18_rgn_forlorn" loc="-306.56 15.48 88.70" performance="7" alert="G:\live\eq2\game\Client\src\GameScene.cpp(6025): Loading UI resources timed out after 0 seconds while still had pending examine requests error# 52"

And this is taken from the \Daybreak\EQ2debug.log (which I also deleted and let rebuild when I was repeating the issue)

[0628/160514.577:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

Not sure these help though, as these logs build when bypassing the patcher/launcher.

ABOUT LAUNCHPAD
Copyright © 2009-2022 Daybreak Game Company LLC. All rights reserved.
LaunchPad: 4.1.0.0 (173)
Shell: 6.0.0.16
Installer: 1.0.3.195
Environment: live

File Validation succeeds and then starts the asset preload.

I see the following three process start when launching the launcher/patcher:
Processname [memory][cpu]
launchpad.exe *32 [57,492k][00]
GameLauncherCefChildProcess.exe *32 [16,436k][02]
GameLauncherCefChildProcess.exe *32 [7,884k][00]

All three die when I leave the launcher window open long enough - roughly 2 - 5 minutes.

If you have other logs for me to hunt down and copy paste from I'd be happy to look.

Same issue for me. I have the same graphic card also.

it would really be nice if devs would EVEN acknowledge this is happening... i restarted computer, made multiple attempts, tried file verification, tried logging in from the .exe, etc... nothing is working.

Windows 10
EVGA 3070
64bit
etc...

nothing is working.

Same problem but say game already running. I haven't had it on in a few days so that's not it.

Likewise, launcher launches then disappears.

Got it to Work Ran As Admin on EverQuest2.exe

I tried installer repair 2 times and running as admin on Eq2.exe & LaunchPad.exe and validating files through launcher but after hitting play button nothing happens.

Window 10 with gtx 1070 8gb
Error log

0623/112739.170:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0623/120049.283:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0623/151206.202:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0624/185632.123:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0626/135338.808:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
[0626/135529.790:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0626/192551.685:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
[0626/192742.643:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0627/180002.657:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

I am having the same issue:

Code:

[0117/130232:ERROR:ipc_channel_win.cc(360)] pipe error: 232
[0607/192343.436:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0619/080234.297:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0619/081409.019:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0619/183830.487:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0625/094159.653:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0625/133023.419:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0625/141836.553:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0626/074736.044:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0626/182915.750:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0627/175220.912:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0628/070906.298:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

My graphics card is a NVIDIA GeForce GTX 1650 Ti.

I am running Windows 11 64-bit, 32GB RAM, 2.6GHz i7 processor

Same issue here.
Logged in and played for an hour at 12.30pm EST today after the patch with absolutely no issues but now have been trying to log in this evening for the past hour and the exact same thing happens, no message ,the launcher just closes either before or after I hit play. I have deleted login cache etc and running as administrator and launching direct from EQ2 folder but no difference.

Windows 11 home 64 bit
AMD Ryzen 5 2600 6 core processor
8192MB RAM
DirectX 12
Nvidia Geforce GTX 1660

ok edited to add that just after posting this, I did manage to get in by going straight from the EQ2 client in the game folder again, no idea why it worked this time and not before.

Just started happening to me. Played from about 1:30 central till 3 pm central now having trouble with launcher

AMD Ryzen 5 3600 6-Core Processor 3.59 GHz
RAM 16.0 GB
System type Windows 11 Home 64-bit operating system, x64-based processor
GeForce GTX 1660 Super
Driver v 516.59

Same error:
[0628/133918.789:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[0628/151036.100:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

Update:
Would like to add that the game ran fine Thursday evening (through the launcher) but it just now (roughly 8:45am EST Sat) required me to circumvent the launcher to get in game (i.e. the launcher just closed without running the game, despite being set to run as admin)

It ran just fine yesterday afternoon on my old ASUS RoG laptop running Win10 for whatever that's worth. I don't have the specs handy on that atm.

I just had a successful login using the launcher on problem system.

Same problem as OP. Windows 10 64 bit, GEForce 3090 graphics card, if that's necessary.

No error; the launcher closes, and when I check in Task Manager, EQ2 is not running.

Edit: Going to try rebooting. Sometimes that fixes random things. Nope. Didn't fix it. Ironically, I *can* launch EQ2 on my older computer, but not my more powerful gaming rig.

My mother's having the same issue, and she's on Windows 10. I'm able to get on just fine, however, and I'm on Windows 11. She's having the same error messages in her debug log too.

I'm getting the exact same thing as everyone else. Graphics card and windows doesn't matter.
EQ2 needs to fix this. I was able to log on last night, and as soon as they did the update, everything went haywire!
I get no errors, just a boot back to my desktop. Checked my debug file and it's the same thing that everyone else is getting.

[0101/092248:ERROR:ipc_channel_win.cc(360)] pipe error: 232
[0318/180740:ERROR:ssl_client_socket_nss.cc(1529)] handshake with server eq2.allakhazam.com:443 failed; NSS error code -12190, net_error -107
[0318/180741:ERROR:ssl_client_socket_nss.cc(1529)] handshake with server eq2.allakhazam.com:443 failed; NSS error code -12286, net_error -113
[0412/141747.376:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[0412/141947.113:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

I'd like to know if the Devs are even looking into this and a Possible ETA on fixing it.

I agree; this is pretty major, when players can't even LAUNCH THE GAME.

Possible Fix

Warning! : This will re-download the entire game, as far as I can tell through testing twice.

1) Open the launcher.
2) Select Advanced Tools on the bottom left right above the progress bar.
3) Select "Select Game Version" from the listed tools, then check the "Full Download" box, and finally click "apply".
4) Press Play once finished. An EverQuest II window will open, and the launcher will close after. I assume this is the upgrade. Once it finishes I believe the game auto-launches, otherwise just launch it through the launcher again.

After this, the launcher may or may not close. If it does, reopen it, and it should start re-downloading everything. The next time the game launches it'll prompt you for video settings, and then (hopefully) launch without issue!

Launcher options:


The upgrade window:

I just sent a message to Dreamweaver and just found out that he's gone. :'(
He was the only one that would get things figured out and fixed quickly.
This really is a sucky day today. :'( (in more ways then any of you can imagine.)

It's been over a year since he left.

https://forums.daybreakgames.com/eq2/index.php?threads/one-last-time.599591/

Same problem here.

This seems to be a serious problem. I hope the Devs will look into it soon.

In the meantime, if you just want to play, it's always worth a try to bypass the Launchpad entirely.

If you have the current client version, go to your EQ2 directory on your hard disk and look for the EverQuest2.exe file. You can run this file from the Windows File Manager. You then get a login window where you enter Account name, Password, Character and Server name.

This only works if you do have the current client version. Otherwise, you get an error message which informs you that you need to rerun the patcher.

This also works if you want to access the Test server. However, to go directly to Test, you need to run EverQuest2.exe in your Test directory, which is a different file than for Live Servers.

It seems Test wasn"t patched today. So I could get on Test by the method described above, except that my Overseer Agents and Quest database was unavailable while I visited Test just a few minutes ago.

Switching between EU and US zones via the Launchpad was very unresponsive, to say the least. However, I could access the Game via manual log-ins. The Launchpad disappeared many times, so I had to log in manually.

The very first use of the Launchpad after the update seems to have worked correctly, which is the reason that my Client version has obviously been correctly patched today. Nevertheless, I believe there's something wrong which needs to be fixed.

Have a good night everybody.