While the old fix was working, it was a bit too much noticeable while
surfing, this is an issue we don't want.
We need a proper check for cheaters too.
- Fixed some game events not being sent to clients
- Use event instead of descriptor for sending it to client
- Moved server bullets to events
- Re-trained zstd data
- Corrected some stuff on clock correction
This check permits to fix interpolation problems on the
local player that valve has been (fucking finally)
caring about on counter-strike 2.
To recall the original issue, the
problem that Valve cared about is that interpolation
had some problems with interpolating the local
player because the screen would never in the first
place match the tick "screen", because interpolation
amount could never reach 0.0 or 1.0
Valve solution was to introduce bugs with lag
compensating the local player and made the game worse,
introducing a new way for cheaters to cheat even more
on their games.
I'm joking, but you can clearly see the outcome anyway.
My solution is to simply set interpolation amount
to 0.0 when a tick arrives.
So when we shoot, we get the frame we shot with an
interpolation amount at 0.0, perfectly aligned to user
commands which is ideal for us.
It might look a bit more unsmooth with lower fps
but with high enough fps, the issue goes away anyway.
It's not very noticeable which is very nice for us.
No need to lag compensate the local player anymore !
* BSD: Add support
* BSD: other fixes
There is still a bug when vgui haven't got text, maybe because of resources.
Also there is bug where when trying to start new game caption names shows wrong.
* BSD: Debugging
* BSD: modify preprocessor and fix windows
* BSD: Remove debugging and fix labels in gameui
* BSD: Remove disabling some DX9 commands
* BSD: Remove -g flag
