'Hit reg' is NOT the same as 'Server is running at 2 ticks and therefore didn't count my shot' (aka packet loss, for want of a better term).
So Stop saying hit reg is a problem when that's not what you mean. And if that is what you mean, then you're wrong. Flat out wrong. If you disagree with this statement, prove ME wrong with a video showing the hit reg failing. I bet you can't.
Now server performance DOES have a problem, and there are some poor servers out there, still. I'd like to see the 'performance' value in the server browser derived from an average +/- standard deviation tickrate from all previous full-server rounds since (resettable if player count is changed, for example). Any server that can't hold 25+ ticks into 1h games when full needs to be reporting numbers significantly less than the 100% performance that basically all servers seem to report in the browser at present.
Comments
So Stop saying hit reg is a problem when that's not what you mean. And if that is what you mean, then you're wrong. Flat out wrong. If you disagree with this statement, prove ME wrong with a video showing the hit reg failing. I bet you can't.
Now server performance DOES have a problem, and there are some poor servers out there, still. I'd like to see the 'performance' value in the server browser derived from an average +/- standard deviation tickrate from all previous full-server rounds since (resettable if player count is changed, for example). Any server that can't hold 25+ ticks into 1h games when full needs to be reporting numbers significantly less than the 100% performance that basically all servers seem to report in the browser at present.
darkhunt promised a video two weeks or so back. But never showed one.