Linkdead

[Pisdov]

Hey guys,

I keep going linkdead when zoning? It happens randomly .... sometimes ill zone just fine.. but it happens at least 70-80% the time im zoning.. its really annoying...

Im playing on windows 8.1 and GTX 970. In windowed mode. (using WinEQ)

The screen goes kinda white and then boom im linked dead. (after trying to relog the server list comes back up empty and ill have to reload the client several times...)

Any idea?

Thanks,
Pisdov

[Casey VII]

are you in the united states

[gildor]

This is happening to me since the hardware failure on the server...very annoying almost unplayable on this glorious 2x exp weekend

[Pisdov]

Yes I'm in the United States ... NYC.

Yea been effecting my glorious double xp weekend as well .. :/

With twink fungi pks in mistmoore on a login timer.. I've been spending more time getting griefed and reloading client all weekend everytime I'm forced to zone. (Cringe to zone)...sigh

[Stormfists]

Been happening to a lot of people since update 32. It's something to do with the servers anti-boxing detection depending on what gfx card maker you have.

I've found a fix, basically when you zone, click your mouse on your eq window, anywhere inside the window, until your eq screen goes grey and you have an egg timer.

If you fail to click the screen within 5 seconds you LD. Very very weird fix but I was LDing every zone in and I do this and I never LD unless I am destructed and do not click fast enough.

[Stormfists]

Note: you won't see this bug acknowledged by designers or any suggested fixes.

[Pisdov]

so click on the header area? so annoying...

[jarshale]

When I do click my window I noticed a higher rate of crashing on zoning. Mysterious.

[Wisteso]

There is already a thread going on about this with more information... (http://www.project1999.com/forums/showthread.php?t=195003)

Clicking the window has nothing to do with it. The problem is that the client fails to connect to the next zone server, and instead of waiting gracefully, the client does whats called "busy waiting" (instead of yielding the process), and that causes the program to become unresponsive to everything else. Then entering input into the game (clicking) causes windows to realize that the program has become unresponsive and you "see" the crash that has already happened.