Not a bug CS:S - hit registry on CS:S 24/7 Dust2

-Luke-

Rookie
=(e)=
Joined
Aug 6, 2022
Messages
93
What is the scope of your bug report?
CS:S

Short description of the bug
hit registry on CS:S 24/7 Dust2

Detailed description of the bug
The ongoing hit registry on the server is not acceptable - it needs to be addressed. Look at this gameplay, how is this acceptable?

https://drive.google.com/file/d/1dbwAiWRRILe0ySPilimyo4zmkmqJwk38/view?usp=sharing
 
chrome_zX0Mv7Zynv.png


erm... im gonna need a demo w/ hitboxes for this one
 
As jii said, unfortunately, the provided clip is too short and does not allow for analysis. Should you get demos that allow for such reviewing to be conducted, you can add them to this post.
 
Adding to this. I am getting a weird lag at the beginning of every round. Stuttering lag for probably 30 seconds at the beginning of every round.
 
Yea, unfortunately I don't have demos, only what I can record with clipping software, it doesn't happen often enough to start recording demos every round, I only submitted this one to demonstrate the problem. The enemy was shot square in the head with a scout and only did 61 dmg. Something is off with the hitboxes and/or registry and it tends to occur when the server fills up, leading many to believe it has something to do with the server's tickrate. Is this not something that can be addressed/upgraded?
 
I'll try to get some recordings tomorrow. There is definitely a stuttering choppiness to players at the beginnings of a round as they run out of spawn. As I mentioned elsewhere, I am not a tech guy at all. But I noticed since the server change, some of the server values are now different. I believe the server cmdrate and updaterate were previously set to 67 for being a 67 tick server. After the change I noticed my interp was different, and I didn't change anything on my end! So I checked server cmdrate and updaterate and they are now set to 128, when the maximum is 100. I thought 128 is geared for CS;GO/CS2 ? Correct me if I'm wrong, but I thought cmdrate and updaterate were supposed to sync to what server tickrate is? Anyways, all I did on my end was switch my 67tick rate values over to 100 in my config, save and rejoin, and at least judging by my games last evening, the registration was improved and better than it was previously.
 

Attachments

  • 20240727195235_1.jpg
    20240727195235_1.jpg
    695.2 KB · Views: 57
That is correct wired. Also cl_interp_ratio is set to 2. That's why lerp numbers are not the same and cannot go lower. And I also agree, when there is no lag, reg has been better than before.

The screenshot is showing when and why is stuttering. Apparently the server can't keep up (or there is a setting preventing) with the information it needs to sent to clients. (cl_updaterate)
 

Attachments

  • 20240727213145_3.jpg
    20240727213145_3.jpg
    90 KB · Views: 50
Last edited:
Ah, ok! I didn't check if the interp ratio changed, but I know before I was able to use an interp ratio of 1 instead of it being set by the server for 2. Makes sense that's the reason why it's higher now. That checks out!

Yes! I too noticed that the updaterate number fluctuates alot more, is less stable, than before. I looked back at my recent clips and screenshots, and as before the change, all my numbers were damn near in sync at 67 with each other, and now that number you have listed with the red arrow pointing to it does bounce around some.

I appreciate you bringing your knowledge to us here! Thank you!
 
erm, sv_maxrate was fudged so fixed that, i did bump interp ratio up to 2 because 1 is just toxic - also the server rates were set to sum like 128tick for some reason: for now they are adjusted to this:


Code:
sm_cvar host_thread_mode 2
sm_cvar mat_queue_mode 2
sm_cvar net_compresspackets 0
sm_cvar net_maxcleartime 0.01
sm_cvar net_splitpacket_maxrate 1048576
sm_cvar net_splitrate 2
sm_cvar sv_maxcmdrate 66
sm_cvar sv_maxrate 0
sm_cvar sv_maxroutable 1200
sm_cvar sv_maxunlag 1.0
sm_cvar sv_maxupdaterate 66
sm_cvar sv_mincmdrate 30
sm_cvar sv_minrate 786432
sm_cvar sv_minupdaterate 20
sm_cvar sv_parallel_sendsnapshot 1
sm_cvar sv_sendtables 1
sm_cvar sv_voicecodec vaudio_speex
sm_cvar sv_client_min_interp_ratio "2"
sm_cvar sv_client_max_interp_ratio "2"
sv_clockcorrection_msecs 0
sm_cvar sv_competitive_minspec "1"

open to suggestions for changes, let me know how it feels
 
Yes, server is very good for now. Reg is good also.

Voices are sexy.

Also, I don't know if it was on purpose, but there are no team flashes for now.
 
Last edited:
Back
Top