Page 1 of 1

crashing and lag from last code update

Posted: Fri Sep 02, 2011 1:55 am
by antihero
just like the last big emu code update, i am noticing lag spikes every time someone zones into the zone i am in. also having a hard time getting into the game from character select. my client is now crashing almost every time i zone. both Titanium and SoF clients have the same issue.

Re: crashing and lag from last code update

Posted: Fri Sep 02, 2011 2:00 am
by Shonnery
Yeah me too bad about every time i zone in less its Hidden or vale it works fine but in other zones i crash when i zone and when i log i get a error message

Re: crashing and lag from last code update

Posted: Fri Sep 02, 2011 2:44 am
by Nerva
I'm experiencing this too. Usually I can get in after the second try, but today it's often taken 3-4 tries, coupled with using the Stuck Character Mover to relocate the character back to the Forest.

I've also noticed a lot of people asking about zone crashes in OOC lately.

Usually, what happens when logging in fails: after getting to the Character Select screen, I click "Enter World" and the game just hangs, instead of going to the loading screen. In addition, my client has been crashing with the "we've detected your client has crashed, send report?" error box when zoning.

I'm currently using the Titanium client, all latest server files, EQEmulator login server.

Re: crashing and lag from last code update

Posted: Thu Nov 03, 2011 10:21 pm
by slurps
having the same problem ><

Re: crashing and lag from last code update

Posted: Fri Nov 04, 2011 1:21 am
by tyranny
have noticed something similar as well.

In my case it involves me getting constant lag spikes on only one char (I usually box 3-5) and then said character will slowly DC after a few minutes of this...

Last time it would be all characters crashing so this is a little different.

Re: crashing and lag from last code update

Posted: Fri Nov 04, 2011 1:40 am
by Lillu
Please don't necro posts, start a new thread if you got an problem and try to provide as much information as possible, specially that this is most probably a client side issue this time.