Crashing to login screen
 

AMD7600
AMD7900xtx
Windows 11
Tried use legacy console mode in options (no compatibility mode avail as on option)
tried wineq2
tried dgvoodoo
nothings working
tried changing my resolution to 1080p down from 4k.
tried as low as 720p, also set the game to run just off of the CPU instead of gpu.
none of these options has worked.
please help!

technical support links for 4 and 5 do not work 404 not found error.

Windows 11 has a compatibility mode under properties. set eqgame.exe to run under windows XP SP2 or 3 and run as administrator.

hth

already tried that.
 

Doesnt work.
I followed all technical support stuff before posting.
i found 3 different youtube videos on trouble shooting followed all using the account data i've used for years on windows 10 doesnt work.
I also started from scratch doesnt work.
I've tried Wired and wireless. w/o vpn from same network i used on my last pc.
I've also created a windows 10 virtual machine, did all this same stuff doesn't work.
same saved files on external HD work on old pc.

Where exactly are you crashing to login? When camping in-game, or when trying to get to char select, or entering world, when zoning?

As a suggestion - all the resolutions you listed as trying aren't 4:3 aspect ratios.

-Mcoy

What exactly is occurring when the client "crashes"? Assuming that you are attempting to connect, hang, then get kicked back to the login screen you are most likely timing out. If that is the case try to flush your DNS and/or power cycle (reset) your network devices then try to connect again.

about 1 second
 

its pretty fast from clicking login at server select to crashing back to enter password. maybe 1 second.

You can't even get to char select ok... You said the same files work on another PC. Have you tried deleting or renaming eqclient.ini (the one you're actually using - if you installed in program files you'll need to look in appdata) so eqgame will generate a default one on next launch?

-Mcoy

same results =/.
 

i followed those instructions, no luck, also tried fresh install. same results

Just curious... how fast is your proc, this type of issue would happen to me if I was over the 4.xGHz limit