OHMY CTF

I looked at the packets I captured over a 30 minute period on July 8. These were the results: Number of packets sent by the client, client IP, client name and finally, occurrences of a large gap between transmissions from the client (>100 ms) 83376 ..........71-219-62-236.chvl.qwest.net.28960 .........

I have analyzed the server quite thoroughly and see no problems. I have run MTR and see no problems. I have verified that there is no swapping going on, I have verified that the processor is not overloaded. I have captured internet traffic and see no problems. If the server were malfunctioning, ever...

I have turned off antilag as an experiment in reducing lag (and turned it back on, did not seem to be noticed much except by Europeans, and negatively).

Main server refresh variable is the server fps, which is set to 20. The rate at which updates are sent out to clients is 1/fps seconds. So since we have 20 fps, every 1/20 second (50 msec) the server sents out a sequence of messages to the clients, each message taking an average about 96µsec, so wit...

Was talking with Auburn about the Lagometer, which does not have any documentation that I can find associated with COD2, but I do know that COD2 is based on the Q3A engine, which is open source, so I went to the folder where I have that and searched for lagometer and found this description: The Lago...

Looked at the scripts that start b3, made sure that it isn't possible for b3 to have more than one running at a time. Chatting with Auburn, he mentions that capturing the flag, sometimes picking up the flag induces lag spikes. I notice that when the lagometer has a yellow blip, the blue triangles th...

I have verified that there is no swap going on and have reduced the memory appropriated to the game.
Also discovered that I no longer have the game logs on the solid state drive, so move them over there today (reduces the possibility of a glitch when b3 reads the logs).

Note that I discovered that I had one of the settings on the command line (the port) repeated a large number of times, but the game appeared to be running, but it is possible that this was affecting gameplay. Message sent to NFO:************** We are continuing to have lag spikes that hit our server...

I had discovered a glitch in one of the files I had used to recreate the server on 6/15, which I fixed. Dunno if that will make a difference.

INFO FROM NFOSERVERS Between 2:30am and 5am CDT on Tuesday, June 30, we will be performing maintenance in Chicago in order to upgrade our connection to the Equinix peering exchange from 20 Gbps to 100 Gbps -- increasing our DDoS mitigation capabilities at this location. This will be a fully scripted...