The SSSE form of the eqgame.exe error and cause

[zuperzip]

If any of the information below is not solid please let me know what criteria needs to be met to make the information concrete and useful. I would be happy to answer any questions or perform further testing. Contact me by PM or admins may use email.

The eqgame.exe error has been visited many times on this and other forums. For many players of EQEmu there is a certain cause for this error at a certain stage of the login process that can block logins for an hour or more at a time, off and on throughout the day.

I'm going to call this error "SSSE" for Server Select Screen error. There are a number of causes for the eqgame.exe error message and it is necessary to focus on when it occurs on order to define the SSSE.


--- When the SSSE strikes ---
The SSSE occurs when the "LOGIN" or "QUICK CONNECT" button is pressed either with mouse button or tab/enter keys. If you use the "LOGIN" button the SSSE strikes immediately so you never get to press the "PLAY EVERQUEST!" button on the server select screen. Players find themselves trying to get to the "PLAY EVERQUEST!" button as quickly as they can by mouse or tab/enter but fail. A slowed mouse pointer is a symptom that the eqgame.exe error is about to pop up. Often players conclude it is a mouse driver problem until they try using the tab/enter keys but fail. It is also true that if the error does not strike immediately, sitting at the server select screen and doing nothing may eventually result in the SSSE. If the "QUICK CONNECT" button is used the SSSE will strike without displaying the server select screen. Once loading begins for the character select screen the SSSE will not occur.

The above is followed by the generic eqgame.exe error message which reads "eqgame.exe has encountered a problem and needs to close. We are sorry for the inconvenience." In the same window there's also the standard Microsoft message with options to "Send Error Report" or "Don't Send". This is on Windows XP.


--- The SSSE cause ---
Recently I performed a series of packet captures and analyzed them. Searching the forums shows "neville" also did some packet captures. I'm not sure if anything further was done with his results.

http://www.eqemulator.net/forums/showpost.php?p=124685&postcount=21
http://www.eqemulator.net/forums/showpost.php?p=124686&postcount=22

What the results show connects a specific packet to the SSSE. That packet contains the survey information for the client. You may recognize this survey since occasionally it pops up during login, "Is this thing on?......... 1) Yes, 2) No, 3) What thing?, 4) Stop wasting my time!". This will be referred to as the survey packet.

Though the survey rarely displays during login the survey packet is always sent with one exception I'll mention later*. In my captures a survey packet arrives as either the 3rd or 4th packet from the server and never causes a problem. This survey packet arrives before the server list is sent for the server select screen. Anytime a second survey packet is sent to the client an SSSE occurs immediately.

A second survey packet can be sent at the tail end of the login process following the list of servers. This makes it impossible to log into your selected server even using the "Quick Connect" button. Generally repeated tries will eventually get through but may take 20 minutes and 40 login attempts or more.

A second Survey packet may also be sent at some point after the initial login while sitting at the server select screen. This survey packet also arrives at the tail end of the list of servers, but in this case it's the server list update. The delay between login and when this second survey packet is sent may vary from a few seconds to hours. When I was running tests on March 20th a second survey packet arrived with delays between 2.5 minutes and 34 minutes over five captures.


What follows is one of the second survey packets as it appears in the capture. It is always 233 bytes in size:

0000 00 0b 6a 58 fb f5 00 30 ab 07 79 7d 08 00 45 00 ..jX...0..y}..E.
0010 00 db 00 00 40 00 34 11 64 c2 0c a4 14 02 c0 a8 ....@.4.d.......
0020 00 02 17 6e 04 30 00 c7 47 b2 00 09 00 17 29 00 ...n.0..G.....).
0030 00 00 00 00 00 00 00 00 00 00 01 00 55 53 00 45 ............US.E
0040 4e 00 01 00 00 00 49 73 20 74 68 69 73 20 74 68 N.....Is this th
0050 69 6e 67 20 6f 6e 3f 00 04 00 00 00 01 00 00 00 ing on?.........
0060 00 00 00 00 01 00 00 00 00 01 00 00 00 01 00 00 ................
0070 00 00 00 00 00 59 65 73 00 02 00 00 00 00 00 00 .....Yes........
0080 00 01 00 00 00 00 01 00 00 00 02 00 00 00 00 00 ................
0090 00 00 4e 6f 00 03 00 00 00 00 00 00 00 01 00 00 ..No............
00a0 00 00 01 00 00 00 03 00 00 00 00 00 00 00 57 68 ..............Wh
00b0 61 74 20 74 68 69 6e 67 3f 00 04 00 00 00 00 00 at thing?.......
00c0 00 00 01 00 00 00 00 01 00 00 00 04 00 00 00 00 ................
00d0 00 00 00 53 74 6f 70 20 77 61 73 74 69 6e 67 20 ...Stop wasting
00e0 6d 79 20 74 69 6d 65 21 00 my time!.


For comparison a harmless first survey packet shown below is 241 bytes in size.

0000 00 0b 6a 58 fb f5 00 30 ab 07 79 7d 08 00 45 00 ..jX...0..y}..E.
0010 00 e3 00 00 40 00 34 11 64 ba 0c a4 14 02 c0 a8 ....@.4.d.......
0020 00 02 17 6e 04 30 00 cf 2b f6 00 03 04 00 15 00 ...n.0..+.......
0030 01 bf 00 09 00 01 29 00 00 00 00 00 00 00 00 00 ......).........
0040 00 00 02 00 55 53 00 45 4e 00 01 00 00 00 49 73 ....US.EN.....Is
0050 20 74 68 69 73 20 74 68 69 6e 67 20 6f 6e 3f 00 this thing on?.
0060 04 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 ................
0070 00 01 00 00 00 01 00 00 00 00 00 00 00 59 65 73 .............Yes
0080 00 02 00 00 00 00 00 00 00 01 00 00 00 00 01 00 ................
0090 00 00 02 00 00 00 00 00 00 00 4e 6f 00 03 00 00 ..........No....
00a0 00 00 00 00 00 01 00 00 00 00 01 00 00 00 03 00 ................
00b0 00 00 00 00 00 00 57 68 61 74 20 74 68 69 6e 67 ......What thing
00c0 3f 00 04 00 00 00 00 00 00 00 01 00 00 00 00 01 ?...............
00d0 00 00 00 04 00 00 00 00 00 00 00 53 74 6f 70 20 ...........Stop
00e0 77 61 73 74 69 6e 67 20 6d 79 20 74 69 6d 65 21 wasting my time!
00f0 00 .


* The one exception is some accounts are never sent survey packets. These accounts do not receive the survey packet near the beginning of the login process or at anytime after and so never experience the SSSE. Currently I know of three such accounts, one I have tested myself but do not own. The other two are owned by someone who experiences SSSEs on his other accounts. Both owners would be interested in helping rid the EQEmu community of the SSSE.

I believe firewall settings may somehow help prevent or allow this problem to occur but right now this is nothing more than a hunch. I do not have packet captures showing differences between different firewalls and their settings.


Below is older information that I gathered over the past months and may be extraneous now. I'm including it in case it may be of some value.

--- Gathered information about the SSSE ---
1) Many hours may go by with no accounts/players experiencing SSSEs or at least the frequency of the SSSE is very low.

2) When there is a high frequency of SSSEs all accounts/players that can be affected by the SSSE will have great difficulty logging in. Repeated login attempts will eventually get past the SSSE.

3) While sitting at the Server Select screen an SSSE may occur immediately when there is an update in the server list.

4) Some accounts are completely immune to the SSSE. This is true even when an immune account is used on different computers in different global locations where the SSSE does occur and when it is occurring with a high frequency.

5) Some players never experience the SSSE.

6) For two weeks this past February I visited a different location 140km away using a different DSL modem and ISP. I took one of my EQEmu computer boxes with me but all other equipment used was from the other location. I often loaded up 4 EQEmu accounts and switched accounts to play different characters. For that two weeks I never experienced an SSSE even though other players often mentioned in game how harsh the SSSE was being to them. A couple days before I left home and the day after I returned home I experienced the SSSE on that computer box.


--- What I think ---
SSSEs are not related to drivers or settings on the client system. It is caused by data sent by the login server or server select server to the EQ Titanium client. The the frequency with which the data is sent raises and lowers in an irregular pattern. For some accounts this data is never sent at anytime. Some firewalls filter out this data preventing client crashes.

[zuperzip]

I have found that responding to the survey stops the login server from sending you the survey packet. The survey shows itself very rarely so when it does come up and asks, "Is this thing on?" you need to select "Yes" and click "Submit". I did this and now that one account is no longer sent the survey packet and so no longer gets the SSSE.

[Vastlee]

Any follow up on this?

This exact thing you described, as opposed to the random eqgame.exe crash that others seem to get mixed up with this, has been happening to me for over a year now. I have 6 accounts. 2 of them are as you stated, "Immune" to it.

One night I actually counted 36 retries before it let me through, and retries seem to be the only thing that actually gets you through. Not rebooting, not logging other accounts in, nothing. And the # of retries seems to be 100% random.

This is the first post I've seen on the subject that identifies the problem specifically. The unfortunate part is that there are several things that cause eqgame.exe to crash that when someone asks about it on the boards 10 other people pop up with another "Oh yeah mine too" story... only it isn't the same thing.

I really hope that someone at least takes notice of this. Running the game 20 times really really sucks nuts.

P.S. The error I'm talking about is 100% exactly as described above. I implore anyone who does not have the exact same symptoms to please not post. I agree with the above that it is something that is being sent from the login server that is causing the problem, which means if we can't get those who maintain that to take notice then nothing will ever get done. So PLEASE

P.S.S. Is there some way to force the survey thing to come up? If clicking YES to it is all I have to do I'd be happy to. I just never see it come up.

[EmanonCow]

Figure out where the "I have been bugged about the survey" is stored in the config files, and change it?

[Erich]

I don't think the "I have been bugged about the survey" flag is client side. If it was then it wouldn't be an account that is immune but rather a entire computer. I'm willing to bet that anyone with an account that is immune will tell you that it's immune on any computer that they use while an account that is not immune will not be immune on any computer.

I'm betting that the "I have been bugged about the survey" flag is server side and if it can be turned on for all accounts this problem will go away.

[Vastlee]

Agreed, I have 5 machines. The accounts that are "immune" are so on all machines.

[Trance]

is there anyways to manualy bring up the survay ? i accidently clicked no when it came up... and now it keeps sending me the error.

ive tryed about 40 times now to connect to the server list it either comes up blank or errors me when it comes up with stuff.

[leslamarch]

I was trying to figure out if it was me or not, so i did a complete system format and brand new install of titanium and i'm still getting that error. I never recall getting a survey, but could have i guess. I hope this little bet of info helps

[So_1337]

I recently got the survey to display on my SK's account, and haven't seen the error since. Now I only have to deal with it on my cleric =\ Both of my accounts are running on the same computer and with the 6.2 client, which contradicts what I've heard in the past about 6.2 clients being immune.

I think the real key to fixing all these problems will be to find the check for whether or not a survey has already been completed for an account and marking them all as "yes".

[Darkonig]

I was getting on just fine for months and then one of my characters had the survey show up. I responded as suggested above and now periodically have the crashes on several characters. If a character is having the problem on one of my machines and I try to log him in on a different machine the account still has problems even tho other accounts on the same computers work fine. It is definitely something the login server is doing. I have never had the problem from the minilogin server.

I grabbed a couple packet dumps from when the one account was crashing excessively (more than 20 times in a row and on multiple computers), but haven't had a chance to review it yet.

[Darkonig]

Ok, just went thru the dumps and found like expressed above. On the ones that crashed, there was a survey packet of size 241 was received, then the server list, then 1 or more additional survey packets of size 233.

Even using quick connect, there was a survey packet size 241 sent, then the server list, then additional servey packets of size 233. They are received regardless of whether the client choses to display them.

On the characters that got in fine, there were no survey packets at all.
So, we either need to get the login code changed to quit sending survey packets, or build a filter to remove them from the stream when sent.

I am going to try the latter approach and see if it resolves the problem. I will have it notify me of any filtered survey packets to verify if it makes a difference. I would assume that altering the data stream to remove those packets would not be any more of a legal issue than using a different login server to begin with.

[Vastlee]

If you succeed Dark, it would be greatly appreciated if you share your success. I'm on my 12th today...

[indigoblue]

This error is driving me crazy..I've got my fingers crossed you can figure out what's going on!!

[Gopdar]

I think that I may have found a solution. Ever since I made the following modification to my eqlsPlayerData file I have yet to receive the error. Here is the contents of the file:

[MISC]
LastServerID=28
LastServerName=[0.7.0] [PEQ]The Grand Creation [legit-luclin]
HasReadSWarning=true
HasViewedWebOrder12864=true
HasViewedWebOrder297546304=true
WebOrderViews297546304=0
HasViewedWebOrder339489344=true
WebOrderViews339489344=0

[UI]
XMLFilename=EQLSUI.xml

[CHAT_OPTIONS]
PlayerNameColor=-1
PlayerChatColor=-6768006
GuideNameColor=-7021579
GuideChatColor=-7691265
AdminNameColor=-569803
AdminChatColor=-1807589
TellColor=-16715776
CommandColor=-16527105
SystemMessageColor=-1
FontSize=3

[PLAYER]
Username=
[NEWS]
LastViewed=-1709800869

All that I modified were the parts in the [MISC] section that said anything about WebOrder to true. Hopefully this works for others.

[Dralanna]

That did not work for me... still getting the error.

This error is definitely on the server, not on your machine.

Note previously in the thread


Agreed, I have 5 machines. The accounts that are "immune" are so on all machines.

[indigoblue]

I tried the fix also, no luck. Although I'm happy it fixed yours for you!! ;)

[zuperzip]

There is a work around that a player by the name of Blasticus on PEQ recently discovered and told us about. At one point I thought accessing a webpage while simultanously logging in would prevent an SSSE but couldn't get it to work the majority of the time. Blasticus tried using a speed test and found it worked very well and so have I. Here is what works for me, open the EQ client and type in your username and password in windowed mode so it is ready to go. Now find any speed test website with your webbrowser (I've been using performance.toast.com or infospeed.verizon.net) and get ready to start the speed test. Start the speed test then switch to the EQ client and quickly log in.

What's important is you 1) start the EQEmu authentication process and 2) get past the server select screen _while_ the speed test is downloading its sample.

It also apparently works if you do the speed test on another system that uses the same router as your EQEmu system.

Hair brained? It sure is... but it works so well for me during a meteor shower of SSSEs that it's more than just dumb luck. I suppose if I want to figure out why it works I'll need to put my nose back into packet sniffing.

[Chewbenator]

Speedtest fix doesn't work for me, but deleting the client files does, very tedious to reset my key sets and resolution though.

[Goggin]

First of all I'm sort of a newb, so this probably doesnt mean anything...

But I noticed after I deleted my client data (as described above) and tried to log in, it gives me a VERY brief error message before crashing. The only reason I was able to see it is by doing a print screen:

"Sorry %3, you already have the maximum number of active tasks"

Any ideas?

*P.S. Almost positive that this has something to do with me deleting the wrong file, but I thought I'd post it anyway just in case. Going to reinstall EQ and see if I get the same thing.

[Vastlee]

Uggh... and it begins. As I mentioned before in this thread please do not post if your symptoms do not match the original post 100%. Already the other crash type posts are starting.

Are there any devs that happen to be reading this thread? I'd very much like to hear their input on the survey packets being sent theory.

[Dralanna]

I'm guessing that people are having luck with the speed test trick because it uses a lot of bandwidth and is probably delaying the survey packet long enough for you to login.

Did anyone trying this also do a packet capture?

[Ashurek]

i cannot belive that speed test worked for me... had about 20 SSSE, and then tried with speed test, and worked at first shot, you need only to log just when test is runing.

... Its fairly a solution, but worth a try when you need more ... more ... more ... more ... you know :O

I think packet collecting isnt useful enough on this problem... as you can't packet collect the loggin server itself, and no idea if it is possible.

maybe the ISP... dunno.

[Dralanna]

as you can't packet collect the loggin server itself


I'm not sure what you mean by this... packet collecting what the login server is sending is how this problem was diagnosed in the first place (see the first post in the thread)

[Ashurek]

i already did, but if it isnt posible finding the corrupt opcode by using this packet collector, then maybe isnt a tracing error, SSSE came up after loggin moved... host maybe corrupt... no idea...

im a fool in all of this, the post you queued was intended for letting know that speed test works, the next text i added was just a think... someting from a person that has not much knowledge with how trackers/hosts work, but lived long time with the monitor on my nose ^^ and breathing eqemu...

Sry my interruption... please devs, programmers, You Rock !! its time to destroy that SSSE !!

you are our last hope ...

[sonicintuition]

Does this so called survey packet refer to that pop up in the character select screen from sony asking if they can gather anonymous data? If it is, I may have a fix..

Once in game, hit alt-o for options and look where it says "Allow sysinfo send" and turn that on. Let me know if that works.

If this is not what the survey packet is, than I'm not sure I've ever seen it before while logging in....

Regards,
Sonic

[Dralanna]

Not sure if anything has changed recently, but yesterday 3 of my accounts got the "is this thing on?" survey... to which I (obviously) said yes. Now those accounts no longer crash. The remaining accounts continue to crash at the server select screen.

[John Adams]

Does this so called survey packet refer to that pop up in the character select screen from sony asking if they can gather anonymous data?
No, Sonic. This is not the data collection option in the client. Occasionally during login (before the server select screen) SOE would dish out news bulletins or mini surveys (very rarely) to users to select before arriving at the server selects.

This thread is brilliant. Excellent detective work.

[Darkonig]

4 of my accounts yesterday got a successful survey. The survey pack contains the question Is this thing on? and 4 possible answers. With responses of submit and skip. So, when I stated before that you always got a survey packet of one size, then list of servers, then 1 or more additional survey packets I was incorrect. The actual transmission is a survey packet, then the list of servers, then zero or more additional survey packets less an 8 byte custom udp header. If no bogus survey packets follow then you get the survey displayed, if 1 or more bogus ones arrive then you crash.

I answered all 4 the same way, as above. One of them crashed again several hours later when I went to log it back in. So, answering the survey does not guarantee the login server will not ask again.

As to the other poster about cannot packet sniff the login server, all of the survey packets are identified as coming from the login server IP and Port with appropriate sequence numbers to suggest they really did.

[Vast]

Not sure if anything has changed recently, but yesterday 3 of my accounts got the "is this thing on?" survey... to which I (obviously) said yes. Now those accounts no longer crash. The remaining accounts continue to crash at the server select screen.

Of all my accounts (9 active now) only 1 got prompted with the survey. (Is this thing on) and I answered "Yes" too. The account still drops though.

I hope that the surveys were sent out as an attempted response by the devs to this thread. I'd be happy just to know someone is aware and looking into it, even if the first attempt didn't work. If the survey pops up again I might try answering something else and see what happens.

Good work to all the non-dev people for providing useful information.

[KileSmith]

after altering the eqlsPlayerData file to be exactly the same as Gopdar, it didn't stop the error from occuring. However, it doesn't do it nearly as often, and i can generally get in after 2 or 3 tries...

[Topgun1969]

Hope there will be a break on this soon. Sometimes could never get in because of the eqgame.exe crash. I went and made me a batch file that loaded the program 5 times. Just so i wouldn't have to keep loading in from desktop. Just put in the password crash and then next screen. lol. Been getting me in on at least 2 or 3 times now. When i finally get in i just mini screen and close what's left. So at least i can deal with that. *peace everyone*

[Dralanna]

Huh, so those of you that answered the survey and still get the crash... have you done any packet captures? I'd be curious to see if you're still getting the survey packet sent. My accounts no longer get that packet. (At least not that I've seen)

[Topgun1969]

I have not been getting any survey.

[Vast]

I had the same thought as you Dralanna, but the 2 accounts I have that never crash have never seen the Survey pop up, and the 1 I got the other day still crashes. I'm still fairly sure it has something to do with the survey but I'm not sure that answering it solves the problem (Or has any effect). I also considered the thought that maybe it is the answer that makes or breaks you. I answered "Yes" to it this time. If it ever comes up again I'll try skipping it and see if that changes anything.

Although, it seems the easiest answer would be for the login server to simply stop sending the packet that causes the crash.

[rewired]

Sometimes could never get in because of the eqgame.exe crash. I went and made me a batch file that loaded the program 5 times. Just so i wouldn't have to keep loading in from desktop. Just put in the password crash and then next screen.

Or you could craft a batch file that automagically reloads eqgame.exe. psudo example posted as follows:

@echo off
cls
echo Starting EQ
:2
start /wait "c:\path\to\eqgame.exe"
goto 2

To halt the loop of EQ auto restarting, you will have to hit 'ctrl-C' in the batch file window and say yes to the prompt.


Windows users essentially use the same batch file to automate a relaunch of world.exe zone.exe upon crash.

the key to this working properly is the following flag:
/WAIT Start application and wait for it to terminate


Cheers

[So_1337]

Or you could craft a batch file that automagically reloads eqgame.exe.
I don't know if that was intended or not, but it was a happy accident if it was a true typo. Having a batch file that does that would be quite magical, thanks for the idea =)

[sonicintuition]

No, Sonic. This is not the data collection option in the client. Occasionally during login (before the server select screen) SOE would dish out news bulletins or mini surveys (very rarely) to users to select before arriving at the server selects.

Duh - I knew that, really, I did. ....I've never seen a "survey" per say, however, the closest thing to it is a news popup with an "ok" button, and the ONLY time I ever saw that was after a patch or on a fresh install, and since I'm not patching my titanium client, only on a fresh install. But I know exactly what you mean now, I remember those surveys popping up occasionally when I used to play eqlive.

Regards,
Sonic

[Budaworm]

I have found out what is causing the game crashes at server list! Or well at least I think I've found the cause, it is when the server list exceeds 40 servers. I'm guessing that the login server is sending too much information to the client which can only show up to 40 servers thus causing the crash.

How did I figure this out? Well I was trying to connect to my server but kept crashing, so I turned off my server and tried logging in and I didn't crash. So I loaded my server back up and tried logging in again and crashed, did this a few times and realized it must be the number of servers causing the crash. So I then counted the # of servers on the list it was 40. I was thinking maybe its just me, so I tried my brothers computer, he would crash when the list was over 40 as well and didn't crash when there was no more then 40 servers.

It would be great if any devs can test to see if this is the cause.

[sfisque]

oh man, i had a chuckle at this. i know its a serious matter... but...

to think that eqemu has been having issues because "of its success", is mildly amusing in a good way. to think that we have reached a point where we have too many servers for the client to handle is a good thing, in some respect.

on a serious footing, lets hope the LS devs can find a way around this issue, or in the worse case, we can always segment LS services between a "full time" LS and a "hobbyist" LS or something comparable/acceptable.

== sfisque

[Budaworm]

Well its not the number of servers on the list or well at least not a static number. I've seen the list go up to 42 servers today so that leaves me wondering what the problem is. Its odd though because last night when I would load my server I would crash every time at server list because there was always 40 servers listed. So I could'nt test to see if I wouldn't crash with less then 40 servers. But for some reason now I can see more then 40 servers and I'm no longer crashing with my server loaded. So I'm thinking maybe there must be something else going on.

Its easy to replicate if you run a server, in that once you start getting non stop game crashes you can try shutting down your server and then logging in and see if you crash. If you don't crash that leads me to believe it has something to do with the number of servers or something related to that.

[sfisque]

is it possible that servers with names that contain "questionable" characters, like hi-bit ascii or similar could be the culprit? since the majority of servers come and go, this would be a possible source of "intermittent" connectivity issues.

== sfisque

[Darkonig]

is it possible that servers with names that contain "questionable" characters, like hi-bit ascii or similar could be the culprit?
That would not explain why 2 different accounts logging in at the same time from the same computer to play on the same server one crashes, one gets in.
And the fact that when packet sniffing a crashing account the packet sniffs between a successful login and a crashed login differ by only one packet, a survey packet that is only 191 bytes long sent by the server at the end of the crashed attempt.

While it is conceivable that there may be more than one cause of crashing, if it were server names in the list then I would expect everyone to crash, not just a few at random.

[Vast]

Darkonig is 100% correct. Accounts that are immune are so because something has been turned on/off for that account on the login server side. This has nothing to do with the number of servers or names of the servers. Again, I ask anyone who is not having the exact same symptoms as the original poster to please not post. If the devs never look at this thread, and then they do and there are 400 different people talking about the many many various things that can cause an eqgame.exe crash they will ignore it as with the other threads.

[Angelox]

Darkonig is 100% correct. Accounts that are immune are so because something has been turned on/off for that account on the login server side. This has nothing to do with the number of servers or names of the servers. Again, I ask anyone who is not having the exact same symptoms as the original poster to please not post. If the devs never look at this thread, and then they do and there are 400 different people talking about the many many various things that can cause an eqgame.exe crash they will ignore it as with the other threads.
This is a General Support Forum - Members can post here on related matters, and the mods/members try and help out. If you think you have a bug to report, then you should do so in the the related forum. In fact, some of the Devs only read the Bug-Report forums.
EqEmu is still in Alpha and the source gets changed all the time. There are a whole lot of reasons and possibilitys for your client not to work properly, including .exe crashes. I can't remember how many times I thought I found a bug, only to realize it was something I had wrong on my side.

[Dralanna]

With all due respect, Angelox.... I am convinced this is a bug with the login server. I have several accounts, when I captured packets every single one got the packet listed in the first post at one time or another. When I got that packet, I crashed. When I didn't get that packet I didn't crash. When the survey finally popped up on 3 of my accounts and I answered correctly those 3 accounts never got that packet again, and subsequently have not once crashed at the server select screen. Now, to rule out the possibility of a client or computer issue, I've logged my accounts (both the bugged and the unbugged) on using multiple machines, OSs, Connection types.... anything I could change and consistently the bugged accounts stayed bugged and the unbugged accounts stayed unbugged.

[Angelox]

Then post a bug report

[techguy84]

Geez, this topic is coming up on 3 months old now. I am sure that in the past 3 months and 50 some post on this, a dev has read this and is aware of the issue. The OP made it clear what he belive the issue to be and that is that.

This project runs on hard effort and time from people that have lives outside of playing the game. Imagine trying to work through the code, fix errors, implement new things, play, test, take care of family, go to work, rinse, repeat.

They will work on things as they can, but drawing a bug out for 3 months in the form of "I get this error also" is rediculous. Things will be fixed when they can be, plain and simple.

[So_1337]

I agree, and I know that it doesn't help to say over and over that you're experiencing a problem, but we've yet to even see a red name say "I'll check into it", or "here's why it's so hard to fix", etc. The only thing we've seen is locks of similar threads by Mattmeck to keep things consolidated to this post.

Some people have gone to great lengths to not only report the error, but to delve into it with packet collection and give much more specific details than we're used to seeing here. If it's being worked on and we just haven't been told, it'd be nice to see whoever's hacking at the problem take a moment and thank them for making his/her job easier.

But yes, it'll be fixed when it's fixed. I don't know about everyone else, but I've noticed a sharp decline in the number of my friends who will log in and play on our server lately because of the pain of trying to log in two or three characters with this error. I know that's the only reason that I panic, is that I'd hate to see so many people drop off from such a fun project because of one intensely frustrating error. Most every other minor error with EQEmu is tolerable, but not even being able to log in just compounds all the others immensely.

[Angelox]

Again, Some of the Devs don't have time to look through all the threads in all the forums - but they have stated they will keep watch on the "bug report" forums.
I would think that a simple post, with direct access to the problem you all are having would be more attractive that a long and drawn out string of posts in a thread (in the bug report forum).
It can even be made "Sticky" so we can be sure they see the problem

[So_1337]

Myself and a bunch of my friends who play on our server received the survey when we logged in for the first time last night. Was this just dumb luck, or maybe a possible attempt to fix the issue by one of the devs?

We're appreciative of any help offered, but let us know here so we know who to thank =P

[Vast]

Yeah the one account that I got the survey on is working beautifully now. So that's 3 down and 9 to go... :(

[Trance]

ok so has there or will there ever be a fix for this? its literaly driving me up the wall.

Ive counted over 70 login attempts and it still wont pass the SSSE it logs in occasionaly when it feels like it but this is rediculis guys :(

anyone that has the actual fix or info on it please do post before i go crazy :(

[Trance]

ps. ive tryed everything said to be the "Fix" for it in this forum thread so far and nothing works so try not to repost.

[Vast]

Dralanna posted this over in the bugs section, it would be nice if it got some attention there so that possibly someone might notice it.

http://eqemulator.net/forums/showthread.php?t=22993

[Vast]

LOL, I like how as soon as it got posted in the Bug section not only did it stop getting attention here, but it hasn't gotten any there either.

P.S. Still Very Much In Effect

[Soregon]

I reinstalled Titanium and for 2 days I still had the same problems. One thing did happen, the "Is this thing working" poll popped up again. This time I answered yes and now I have not had a crash trying to log in for a week. I am not sure if reinstalling caused the poll to pop back up but I was glad to see it.

[Vast]

It seems 100% random for that poll to actually come up. I say this because I've been playing for a year and in that year only 2 out of 11 of my characters have ever had it come up. Dralanna has been going for around the same amount of time and in a week he got like 4.

[Dralanna]

I had a fifth come up 2 days ago, but the damn thing crashed before I could respond.

[Vast]

I'm crying on the inside...