Page 1 of 1
Switching to queued data mode
Posted: Wed Oct 30, 2013 4:09 am
by Harley
Code: Select all
Client#2 i/o thread starting
Client#2 i/o thread past initial lock
Account admin logged in from 127.0.0.1
Account admin selecting character Harley
[pkg/player/login/LogAccountLogin/logon.ecl]: Logon Harley (0x2) account admin ip:127.0.0.1
[10/30 13:38:14] Client#2: Switching to queued data mode (1, 12 bytes)
Client#2: Leaving queued mode (1959 bytes xmitted)
[10/30 13:38:18] Client#2: Switching to queued data mode (1, 10 bytes)
Client#2: Leaving queued mode (241 bytes xmitted)
Client#2: Switching to queued data mode (1, 10 bytes)
Client#2: Leaving queued mode (66 bytes xmitted)
Client#2: Switching to queued data mode (1, 12 bytes)
Client#2: Leaving queued mode (1889 bytes xmitted)
[10/30 13:38:19] Client#2: Switching to queued data mode (1, 10 bytes)
Client#2: Leaving queued mode (281 bytes xmitted)
Client#2: Switching to queued data mode (1, 12 bytes)
Good day! In this code I don't understand. Help me please, how can I disable this and what is this?))
Re: Switching to queued data mode
Posted: Wed Oct 30, 2013 10:45 am
by Harley
This occurs when two characters are close to each other. Everyone starts to hang and then knocks them out of the game.
But, I don't know how to fix that, and after what that were happened.
Need your help.
With best regards!
Re: Switching to queued data mode
Posted: Wed Oct 30, 2013 10:54 am
by Harley
I have found the cause!
This problem were at MontuZ megacliloc packethook for 096 core.
I don't know, how to fix it.
This is the packethook
Re: Switching to queued data mode
Posted: Sat Nov 16, 2013 12:40 am
by CWO
Switching to queued data mode is what happens when POL can't immediately send data to the client fast enough because the connection is congested (lag).
Re: Switching to queued data mode
Posted: Thu Jan 30, 2014 7:05 am
by Agata
That packethook doesn't properly use clilocs they way they are meant to, this creates LOTS of lag. I guess you already had a look at MY megacliloc packethook in the Custom Script Releases.
Re: Switching to queued data mode
Posted: Wed Mar 05, 2014 3:30 am
by Harley
Agata wrote:That packethook doesn't properly use clilocs they way they are meant to, this creates LOTS of lag. I guess you already had a look at MY megacliloc packethook in the Custom Script Releases.
Agata, of course! Your megacliloc packethook is great, I have changed to urs, but, there are some messages too:
Code: Select all
Switching to queued data mode (1, 18 bytes)
Switching to queued data mode (1, 7 bytes)
Switching to queued data mode (1, 7 bytes)
sysload=0 (0) cputime=1250000
(128) scin: 1726919 scsl: 318951435 MOB: 5241 TLI: 17715
Switching to queued data mode (1, 7 bytes)
...
Switching to queued data mode (1, 18 bytes)
And I really don't know how to fix it!
