After the CSS Update...

[bdeep]

So I have successfully updated all my CS:S Servers on my VPS

VPS: Win2k8 x64

I had no lag issues before this epic fail of a Valve update and now on all of my servers running on that machine when a player joins they lag for 2 - 5 minutes. Then their ping goes down and things settle in and game play is normal.

This happens when ANYONE connects, its not just one person or certain people, its EVERYONE.

Any suggestions.

[Edge100x]

Do others in the server have problems while that person is stabilizing, also?

Are you using any custom files that need to be sent to clients (custom maps, models, sounds, etc)? If so, is the fast download system working correctly?

What rate, sv_minrate, sv_maxrate, sv_minupdaterate, and sv_maxupdaterate are you using? Have you tried adjusting these?

Are you seeing a server FPS dip or high CPU usage when this occurs? You can see the server FPS through the client with net_graph 4.

Do you have any plugins running, and if so, have you also tested with them disabled?

[bdeep]

Yes, and I have talked to other server admins that are having the same issues (not on NFO)

Yes and Fast DL is working correctly.

Since the tickrates changed to max at 66 tic I havent changed and settings since I had it for 100 tic. What should I use?

No, everything is good on the server.

Yes I do, they were all working the other day after I redid all the servers for the update. This started happening 2 days after the updates were complete. This also happens on ALL my servers and not all of them are running mods that are the same, some of them arent running anything other than a basic default config.

[Edge100x]

If this started two days after the update, have you double-checked to make sure that you are running the latest optional release, from the 25th?

The rates you use should be the same as what worked well under the old version, but I just want to see them to double-check that you're using sufficiently high numbers.

[bdeep]

Code: Select all

// Edit this to your liking. These values are very close to what I use
// for my own servers.

//zBlock
cb_active 3
zb_active 1
//zb_authhost "www.eco-league.com/zblock.php"
zb_crouchfix 1		// ZBlock 4.4 Do Not Edit Must be 1
zb_bunnyfix 0		// ZBlock 4.4 Do Not Edit Must be 0

// Name Of Server
hostname "RSG Clan Scrim Server|1000 FPS"

// General HL Cvars
sv_contact BLANKED OUT

// Rcon Stuff
rcon_password BLANKED OUT

// Make sure the right people are banned
exec banned_user.cfg
writeid

heartbeat

// server cvars
mp_friendlyfire 1 
mp_footsteps 1 
mp_autoteambalance 0 
mp_flashlight 1 
mp_tkpunish 0 
mp_forcecamera 0 
sv_alltalk 0 
sv_pausable 0 
sv_cheats 0 
sv_pure 2
sv_consistency 1 
sv_allowupload 1 
sv_allowdownload 1
sv_airaccelerate 10 
sv_maxspeed 320 
mp_limitteams 0 
mp_hostagepenalty 0 
sv_voiceenable 1 
mp_allowspectators 1 
mp_chattime 10 
sv_timeout 65  
sv_download url BLANKED OUT
mp_dynamicpricing 0
mp_autokick 0 
mp_spawnprotectiontime 0 
mp_autocrosshair 0 
mp_fadetoblack 0
sv_friction 4
sv_gravity 800
sv_stepsize 18 
sv_stopspeed 75 
zb_active 1
zb_autoupdate 1

sv_unlag 1 
sv_maxunlag .5 
sv_voiceenable 1 
sv_minrate 30000
sv_maxrate 0
sv_mincmdrate 30
sv_maxcmdrate 100
sv_minupdaterate 30
sv_maxupdaterate 100
sv_client_predict 1
sv_client_interpolate 1
sv_client_cmdrate_difference 30

// round specific cvars
mp_freezetime 1
mp_buytime .50
mp_roundtime 1.75
mp_startmoney 16000 
mp_c4timer 35 
mp_fraglimit 0 
mp_maxrounds 0 
mp_winlimit 0 
mp_playerid 0
mp_timelimit 0

// server logging
mp_logdetail 3
log 1

// operation
sv_lan 0 
sv_region 1

// important settings inserted by NFo
sv_password BLANKED OUT
tv_enable 1
tv_name "STV 216.52.143.148:27021"
tv_title "Welcome to RSG SourceTV: Scrim Server #1
tv_port 27021
tv_password ""
tv_delaymapchange 0
tv_autorecord 0
tv_delay 10
tv_maxclients 1

exec pregame.cfg
sv_max_queries_sec 3

sv_max_queries_sec_global 150

sv_stats 0

fps_max 0

The config from my scrim server, with no plugins (zBlock is not currently running)

No I dont think i did that update. I will try that while I wait for your response.

[Edge100x]

I don't see anything wrong with your rates. Please let me know if the update helps.

[bdeep]

Didnt help

Supporting Screeny:

[bdeep]

My ping will stay that high for 2-5 minutes and i will be laggy as all hell then it will go to the normal ~60.

This is after the update and again happens on all servers.

[Edge100x]

Is the CPU usage in the task manager higher when this is happening?

It's normal for an individual player's ping to appear high when he first joins an OB server, but it shouldn't stay high for multiple minutes.

Could you try a completely stock configuration to see if that helps?

[bdeep]

I did try that and no it didnt help.

Here are some screens of when my ping goes down, this is in my GG server. The last screen is a shot BEFORE this epic fail of an update to OB.

[Edge100x]

L4D2 has a problem with a high cmdrate, so it might be worth trying a lower one (like 66) here, as well (the engines aren't the same, but they are similar, and it's possible that Valve ported some feature from L4D2 to OB). A higher number won't increase performance anyhow, since 66 is the maximum.

[bdeep]

I am still doing updates to servers so I will update that info as well. I will report back tomorrow night at some point to let you know.

[bdeep]

Ya... no joy. Still lags the same way after the updates. I also slimmed down my Pubs server.cfg and removed some needless SM plugins and nothing. Up for suggestions.

Also I did up the server to a 30 player server. Think that might have caused something?

Also on a separate note:

What are suggested Net Code settings for client side for a 66 tic server @ 1000 Fps. Its a 30 slot server.

I am off to the Bronx for 4 days for work, I will try and check in at night from the hotel

[bdeep]

No suggestions at all?

[Edge100x]

I haven't been able to come up with anything specific yet, no. But, you can try the standard troubleshooting things of starting over with a completely stock install, binding the server to a specific CPU core, making sure that it's running at high CPU priority, and so on.

On the client, I generally recommend high settings like this, if your connection can handle them:

cl_updaterate 66
cl_cmdrate 66
rate 100000