1.15.17 Bug?

[Blind Aviator]

While the client is running it will begin to generate spawns in the list without names... All other info besides the names are there...

Error log:

01/01/2004 12:20:18.52 - MySEQ Version: 1.15.17
01/01/2004 12:20:18.53 - Loaded Prefs.Xml
01/01/2004 12:20:18.53 - Loading MacroQuestPanel
01/01/2004 12:20:18.72 - Creating the Docking Manager
01/01/2004 12:20:18.91 - Loading Bitmap into ImageList
01/01/2004 12:20:18.94 - Creating SpawnList Window
01/01/2004 12:20:19.13 - Creating Spawn Timer List
01/01/2004 12:20:19.14 - Creating MQConsole Window
01/01/2004 12:20:19.24 - Loading Position.Xml
01/01/2004 12:21:10.91 - Short Zone Name: (PoTranquility)
01/01/2004 12:21:10.93 - Using Short Zone Name: (PoTranquility)
01/01/2004 12:21:11.01 - Zone Map Loaded: E:\myseq\maps\PoTranquility.map
01/01/2004 12:21:16.60 - Short Zone Name: (pofire)
01/01/2004 12:21:16.61 - Using Short Zone Name: (pofire)
01/01/2004 12:21:16.65 - Zone Map Loaded: E:\myseq\maps\pofire.map
01/01/2004 12:21:23.13 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:23.35 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:23.57 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:23.79 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:24.01 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:24.41 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:24.85 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.05 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.07 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.32 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.34 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.54 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.56 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.77 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.79 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:25.99 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue
01/01/2004 12:21:26.01 - Error in ProcessSpawns(): String cannot be of zero length.
Parameter name: oldValue

[Blind Aviator]

Got a totally different error after restarting client:


01/01/2004 13:11:52.46 - MySEQ Version: 1.15.17
01/01/2004 13:11:52.46 - Loaded Prefs.Xml
01/01/2004 13:11:52.47 - Loading MacroQuestPanel
01/01/2004 13:11:52.66 - Creating the Docking Manager
01/01/2004 13:11:52.75 - Loading Bitmap into ImageList
01/01/2004 13:11:52.78 - Creating SpawnList Window
01/01/2004 13:11:53.01 - Creating Spawn Timer List
01/01/2004 13:11:53.03 - Creating MQConsole Window
01/01/2004 13:11:53.09 - Loading Position.Xml
01/01/2004 13:11:55.27 - Entering in CSocketClient.CSocketClient()
01/01/2004 13:11:55.27 - Exiting in CSocketClient.CSocketClient()
01/01/2004 13:11:55.29 - Entering in CSocketClient.Connect()
01/01/2004 13:11:55.74 - Entering in CSocketClient.Receive()
01/01/2004 13:11:55.74 - Exiting in CSocketClient.Receive()
01/01/2004 13:11:55.75 - Entering in CSocketClient.Connect()
01/01/2004 13:11:55.90 - Entering in CSocketClient.Send(Byte[])
01/01/2004 13:11:55.90 - Exiting in CSocketClient.Send(Byte[])
01/01/2004 13:11:55.91 - Entering in CSocketClient.SendComplete()
01/01/2004 13:11:55.91 - CSocketClient.SendComplete(): GetNetworkStream.EndWrite()
01/01/2004 13:11:55.92 - Exiting in CSocketClient.SendComplete()
01/01/2004 13:11:55.92 - Entering in CSocketClient.ReceiveComplete()
01/01/2004 13:11:55.96 - Entering ProcessMap()
01/01/2004 13:11:55.97 - Short Zone Name: (Pofire)
01/01/2004 13:11:55.97 - Using Short Zone Name: (Pofire)
01/01/2004 13:11:56.01 - Zone Map Loaded: E:\myseq\maps\Pofire.map
01/01/2004 13:11:56.37 - Exiting ProcessMap()
01/01/2004 13:11:56.38 - Entering ProcessTarget()
01/01/2004 13:11:56.38 - Exiting ProcessTarget()
01/01/2004 13:11:56.42 - Entering ProcessPlayer()
01/01/2004 13:11:56.42 - Exiting ProcessPlayer()
01/01/2004 13:11:56.53 - Entering ProcessSpawns()
01/01/2004 13:11:56.55 - Exiting ProcessSpawns()
01/01/2004 13:11:56.55 - Entering ProcessSpawns()
01/01/2004 13:11:56.58 - Exiting ProcessSpawns()
01/01/2004 13:11:56.62 - Entering ProcessSpawns()
01/01/2004 13:11:56.63 - Exiting ProcessSpawns()
01/01/2004 13:11:56.64 - Entering ProcessSpawns()
01/01/2004 13:11:56.64 - Exiting ProcessSpawns()

[MQSEQ2]

Is your client machine on a wireless network?

I have seen this before with wireless, I've been adding code to prevent this type of stuff. I will do some more checking.

[Blind Aviator]

I have a DLink wireless router but no wireless clients attached to it... Everything is hard wired so far...

I have 2 different machines here that I run the client on... I haven't checked one of the 2 to see if it has the same error or not.... Generally when I setup the client on one machine I will just copy the directory as a whole to the other machine to help save time... Then all I have to do is adjust the directories in options...

Will check the other machine here in a bit to see if it does the same thing or not...

BA

[Blind Aviator]

I ran the client on the "main client" machine for about 45 minutes with error logging at 1 and it never had a problem....

I continue to have the problems on the other system... It usually takes less than a minute before it starts to have problems...

Not sure what the major difference between the 2 systems could be to cause it??
Both running the same software... Windoze XP Pro SP1a, .NET v1.1, both connecting across the same router...

Does the client utilize Java at all??
The system that has problems is running Sun's Java while the one without problems has the built in one from Windoze...

Any suggestions??

BA

[MQSEQ2]

No Java.

Sounds like the other persons problem. As soon as he connects his map screws up and fill the log with those error message. When he runs the client on a different machine it clears up.

The Client only need .Net Framework 1.1.

What network card are you using?

What I can do is create a debug version that will output all data being sent from the Server so we can actually view the garbage being sent.

[Blind Aviator]

Network card on problem system is Intel Pro 100+

BA

[NovaUSC]

Based on that you should be at least able to discount the server and the network itself(unless you have the machine configured for somethign special). Does it only happen in the Plane of fire? I noticed there were no errors in Tranquility. Does it not begin until you zone or does it just begin after a specified amount of time has passed regardless of where you go?

[MQSEQ2]

From the logs I seen from the other user it can happen in any zone. What it sounds like is when there is a packets coming from the server the the Client is trying to reassmble the packets to decode and there is logic in there that tries to copy incomplete packets to a buffer to be used when more packets come in.

This issue came to light when I broke out the Packet Processing and I setup logging for all errors. This means it's been there in the past but you may not have seen it unless you looked at the titlebar (it would change every now and then with Unknown Packet Type).

The new client didn't cause the issue but is trying to prevent the error by filtering out bad information. The new 2.x server handles the packets differently so this issue doesn't exist in that version.

Ok, I know Intel Pro 100+ nics have problems with certian hubs/switches/routers etc. Try setting the card to 100Mhz and Half duplex and try that. Don't use Auto/Auto sense most off the self switches really can't handle it properly on a port by port assisgnment. That means if you have a card set to 100/Half and it connects to the switch first it may force the switch to go into half duplex mode then when the 100/Full comes in it will cuase alot of retransmission of packets. This effectively slows your network down. Also remove QoS (Quality of Service), this tries to get the best network condition but does nothing more than add alot of overhead.

[Blind Aviator]

Tried switching it to 100/Half and no change...