freezing on zoning

[Wiz]

There are two possible reasons for this, in my experience.

1) Playerprofile is scrambled, a required packet is missing or a bad packet is sent.

This occurs during login, when playerprofile, checksum, weather, etc are being sent. If the playerprofile has some bad values, you send a packet that really shouldn't be sent at this point, or you're not sending one of the packet it expects it will sit and wait for the proper packets forever, never proceeding with login. The server admin needs to ensure all the routines are in order.

2) A required packet is properly constructed in the client process, but fails to be received by the player's client.

Some ISPs in particular has an issue where they require a packet going out (in the EQNetworkConnection's Process()) to be resent a bunch of times. Also if the packets are too speedily resent, it won't have properly recieved them, and thus gains the same problem as 1). Having the server admin increase the time between packet resends in EQNetworkConnection::Process() (I've found that upping the minimum from 250 to 500 works) will generally solve this for most users. Lower datarate will solve it for some because it artifically increases the resend time.

[mwmdragon]

I an having the same problem on one of my lan computer while connecting to the minilogin. I have other computer connecting and playing together but for some reason one pc will crash on zoneing and then if i watch the zone.exe while that player is connected after the crash it keeps giving an Unknown packet error and the player can't attack or use a merchant or even see other platers who are in the same zone. What could be causing this corruption? We have deleted the character and re-made him and it had the same problem.

I would love to get the other PC playable on our minilogin server again. please let me know how I can prevent this.

[vladimir]

Wiz, Image asks which process he should change from 250 to 500. THanks for you help so far

[image]

I think I found it, just wanted to make sure if wasn't something else, the line is like data < 5 && last->PacketSent + 250 .... I set the 250 to 500.

[Wiz]

Originally Posted by image

I think I found it, just wanted to make sure if wasn't something else, the line is like data < 5 && last->PacketSent + 250 .... I set the 250 to 500.

That's it.

[fathernitwit]

I think these are things that should not remain hidden in the netcode, so I will make them into defines in features.h. I am not sure the right names for them. I have turn this:

if (((pack->LastSent + 500) <= Timer::GetCurrentTime()) || (datahigh < 5 && (pack->LastSent + 250) <= Timer::GetCurrentTime())) {

into:

if (((pack->LastSent + DATA_RESEND_DELAY) <= Timer::GetCurrentTime()) || (datahigh < 5 && (pack->LastSent + DATA_RESEND_DELAY_IDLE) <= Timer::GetCurrentTime())) {

I am not sure if those two names are really the right words though. Does anybody have any better suggestions for names on these parameters?

[Wiz]

Nix the differentation between data < 5 and data >= 5. It's pointless. Just make it a halfsecond either way.