Is it possible to raise the time required for there to be lag before the server autokicks someone for bad ping?
Whether he is winning or losing, it is frustrating for the player to be kicked in middle of fight. I suppose there could still be complaints of lag in which you go from pursuer to pursued if the time is increased, but so far I have only seen the autokick appear on a player who is about to be shot down.
It should be stressed that this is NOT an accusation of cheating, but rather a server issue with how it protects itself when it detects a bad connection, and the hope that a longer time allowed for a ping spike will reduce the number of autokicks.
autokick threshold
- Colslaw
- Lt. Colonel

- Posts: 779
- Joined: 05 Nov 2007 01:32
- Contact:
- RCAF_FB_Blood
- Posts: 45
- Joined: 22 Jun 2010 17:42
Re: autokick threshold
That Colslaw is a very good idea. But I would not raise it above say 800 do to just way to much lag issues between the 2 aircraft. If the other one is running even a 100 ping set to the 750 or near 800 ping then u are looking at close to a 1000 ping set difference between the aircraft.
In the past with my old connection thats the main reason I tried not to engage you guys. I knew that the longer that the fight went on the more probability I was gonna be booted. It aggravated me to all lengths on both sides of the equation as defender or attacker to get booted do to ping. Especially if I was wounded and knew it was a matter of time for me to die and then poof I was back on the desktop going wtf???!!!. I was always worried that Tiger would get tired of this and boot my sorry azz out of the campaigns do to it.
So yes I agree with that old slaw up there on raising it just a bit. ~S~ Blood out
In the past with my old connection thats the main reason I tried not to engage you guys. I knew that the longer that the fight went on the more probability I was gonna be booted. It aggravated me to all lengths on both sides of the equation as defender or attacker to get booted do to ping. Especially if I was wounded and knew it was a matter of time for me to die and then poof I was back on the desktop going wtf???!!!. I was always worried that Tiger would get tired of this and boot my sorry azz out of the campaigns do to it.
So yes I agree with that old slaw up there on raising it just a bit. ~S~ Blood out
- RAF209_Benge
- Posts: 169
- Joined: 06 Jan 2009 21:59
- Location: Iowa
- Contact:
Re: autokick threshold
We have a pilot who cannot fly this thing because he is in Nome and his avg. ping is 650
Wing Commander C.K.Benge
Commanding Officer
209 Squadron
Royal Air Force
"Don't Rest On Your Laurels"

Commanding Officer
209 Squadron
Royal Air Force
"Don't Rest On Your Laurels"

- Tiger
- Colonel

- Posts: 2845
- Joined: 17 Jul 2007 00:17
- Location: Noblesville, Indiana, USA
Re: autokick threshold
S!~ Gents,
I believe we can implement Colslaw's suggestion of raising the time required before a pilot is booted because of bad ping, but I do not believe we can raise the max ping itself. Here's the confc.ini file from the dedicated server; And, even if we could up the ping, I'm not sure we want to. Regarding Benge's comment, we have people from halfway around the world that have no ping issues, so the location is not the problem.
I believe we can implement Colslaw's suggestion of raising the time required before a pilot is booted because of bad ping, but I do not believe we can raise the max ping itself. Here's the confc.ini file from the dedicated server;
Code: Select all
[NET]
speed=8000
serverChannels=16
localPort=21000
SkinDownload=0
difficulty=1217791
serverName=
serverDescription=
checkServerTimeSpeed=1
checkClientTimeSpeed=1
localHost=
socksHost=
[chat]
autoLogDetail=3
[MaxLag]
farMaxLagTime=10.0
nearMaxLagTime=2.0
cheaterWarningDelay=10.0
cheaterWarningNum=3
[Console]
IP=2000
IPS=
LOG=1
LOGTIME=1
LOGFILE=logs.lst
HISTORY=128
HISTORYCMD=128
LOGKEEP=1Who is online
Users browsing this forum: No registered users and 4 guests


