Odd problem..

[Mixy!]

This one is going to be hard to explain so bear with me. Im running server 1.11, and client 1.15.14 on two seperate boxes. I have the client set to debug mode.

For the past two releases of the client (even before the whole 'daily patch' stuff the past few days) will "die" on me during play. By "die" i mean i'll look over and the client will be on GO (meaning it stopped, and the GO button is active). When i hit the GO button, sometimes it will start working properly again. Sometimes it will not restart, and just toggle back to GO instantly without restarting. My error logs have nothing in them other than the usual "Unable to update spawn info", and the "drawline errors".

On the server side... each time i hit GO on the client, the server responds with the usual "Found connection on IP XX" (or whatever it says), so the server is detecting the client.

Now here's where it gets odd... i discovered that if i relogged it would often cure the problem. Even odder, if i did a /loadskin 1 it would sometimes cure the problem.

So, i guess the point of the whole thing is that it's randomly stopping on me.
PS - I use the offsets posted here.

-Mixy!

[MQSEQ2]

It sounds like the Client/Server is getting messed up when you do the loadskin since the EQ Client stops responding for a short period of time during the skin loading.

Do you switch back and fourth alot?

Do you log out of EQ to desktop then come back in without restarting the Server?

We gonna have fun trying to track this down. This "drawline errors" sounds like an older client is being used. Post your error log so we can tell what's going on.

[Mixy!]

Ok, i'll post my log filewhen i get home today.
Just to clarify (because i know im confusing) the loadskin is what i do to FIX the problem. I never do a loadskin other than when i need to fix the client from not responding.

I never log out to desktop, or anything. The client will just stop in the middle of a LDoN adventure, or running to the Tranq stone in PoK for example. There isnt a certian thing that causes it (to the best of my knowledge) it appears to just happen randomly.

My client box's CPU useage is only around 14% also, so i dont think it's a memory leak or anything of that nature.

-Mixy!

[MQSEQ2]

Ok, while in the dugeon are the mobs stopping in what looks like a circle about 1000 feet away from you? If so, this is normal because you are not moving for a period of time, this is a EQ client doing this to reduce the the traffic and updating.

If not, then the log file might help us out.

[Mixy!]

Nah, im aware of the ol' bandwidth saving techniques of SOE. The client actually dies, meaning my location and FoV dosnt get updated or anything... and the GO button (which usually says STOP when the client is active) is toggled to GO. As i said before, i'll post the log file when i get home. This is an odd problem, and i'll do my best to help you track it down.

-Mixy!

[MQSEQ2]

Cool, I can make you a special Client version that will have more Logging in it if needed.

[Mixy!]

PM'd you my email address, as i dont want it floating around.

-Mixy!

[MQSEQ2]

I will start adding more logging code then email it to you. The version I'll send you will be part of the next release as well.

[Mixy!]

Here's y log MQSEQ2. The whole thing is about 6000kb in size, but this repeats over and over. This is the last section, prior to quitting:


12/24/2003 16:04:13:77 - CSocketClient.SendComplete(): GetNetworkStream.EndWrite()
12/24/2003 16:04:13:77 - Exiting in CSocketClient.SendComplete()
12/24/2003 16:04:13:77 - Exiting in CSocketClient.Send(Byte[])
12/24/2003 16:04:13:78 - Entering in CSocketClient.ReceiveComplete()
12/24/2003 16:04:13:81 - Entering in CSocketClient.Dispose()
12/24/2003 16:04:13:81 - Entering in CSocketClient.Disconnect()
12/24/2003 16:04:13:81 - Exiting in CSocketClient.Disconnect()
12/24/2003 16:04:13:81 - Exiting in CSocketClient.Dispose()
12/24/2003 16:04:13:82 - Entering in CSocketClient.Receive()
12/24/2003 16:04:13:82 - Error in CSocketClient.Receive(): Socket Closed
12/24/2003 16:04:13:82 - Exiting in CSocketClient.Receive()
12/24/2003 16:04:13:82 - Exiting in CSocketClient.ReceiveComplete()

I hope you can make sense of that :P

-Mixy!

[MQSEQ2]

Ok, I will get you a new Client that will have some more logging. It will be later tonight, dang Sanata is coming and I have to work around his schedule tonight.

[xeerex]

Ho Ho Ho....3 boys under 5 yrs old so I know the Santa syndrome!

My client has been doing almost the exact same thing in most but not all zones. I attributed it to the offset changes and have not played EQ since the last update. Prior the the 18th patch and subsequent SOE really bad screw ups, mine performed flawlessly hence my reasoning that it was an offset issue.

Anyway, I'm off to hunt down the current offsets if available and get back into EQ mode.

[MQSEQ2]

Sorry Mixy, I didn't forget about you, I'm testing 1.15.15 right now I have added some more Logging in it and I'm sitting in game with it running, I want to see what it does in about an hour or two.

Logging=1 shows Error type messages
Logging=2 Shows Error type messages and Entering/Exiting mesaages.

I also added the Short Zone Name to the log file.

If everything goes good I will release it tonight (about 6 hrs from now).

[Mixy!]

Fine by me bud. Myseq is still functional for me, just slightly annoying. Plus im busy with holiday stuff too.

-Mixy!