I've noticed an increase of players using the console to make changes that the GUI doesn't allow for.  Namely, maxFPS.  It's been proven that increasing your maxFPS allows for weird situations to occur.  But looking at it from the server-side, when you set your maxFPS to some ridiculous number the server is working extremely hard to maintain the flow of data to fulfill that request.  And when you have a significant number of players drawing that much data the server has a difficult time calculating explosion particles and bullets and then everyone feels the lag.  The human eye can recognize frame rates below 65Hz or 65FPS.  Personally I have mine set to 85FPS and my monitors refreash rate is set to 85Hz (I still use a CRT).

 

Perhaps we could run an experiment to see if this would make a difference or not, but it doesn't take a rocket scientist to know that it would definitely help the server if every set their FPS to 75 or 85.  And for those who use the console to set their FPS to numbers higher than what is available in the GUI, and you know who you are, please at least use a setting available in the GUI.

 

 

 

Some of the problems with certain maps, Col1 for example, have been going on long before the switch to RPM Mod.  However, the increase in headshots/one shot kills, unpredictability of shotgun accuracy and strength manifested with the implimentation of RPM.  We're going to look into any possible conflicts with weapon configurations and other settings and also try to clear up previous anomolies such as the multiple death sound when you shot someone.

 

 

 

For now this is just a shot in the dark.  Perhaps there may be a way to reduce the data demand on the server which would in turn keep the frame rates high thus eliminating lag, or moments of laggishness.  We've been at this for over 5 years now so it would seem that we'd have the best settings, but it's always worth a look.