Aimpunch causes server hit registration to be aimed higher than the client.

[Smrekishs]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: https://gist.github.com/Smrekishs/cd470b11ada1a6919b78e9c00ececa1a

• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

https://github.com/ValveSoftware/csgo-osx-linux/assets/117657435/f2db3ca7-72c2-430c-be63-b31966d8269b

Expected Behaviour: Server and Client hits in the same spot despite I'm getting aimpunched.

Actual Behaviour: Getting aimpunched and shooting at the same time causes the server hit registration (Blue cubes) to be aimed higher up than the client (Red cubes).

I don't know which update cause this behaviour started but I suspect it's been in the game for a long time.

Steps for reproducing this issue:

1. Get a player to continiously shoot you ( I used a bot )
2. Shoot your gun until the bug happens ( Shotguns make noticing the bug easier )

[thouravi]

I tried to re-create this bug and it seems like it has been fixed now. @Smrekishs close this request, cheers.

https://github.com/user-attachments/assets/7b2c10a2-ccf4-46e4-88f2-4c3c3009ca4f

[Smrekishs]

@thouravi Did you test with loopback=1? The bug only occurs if loopback=0

There was an update a couple months after I made this post which made loopback=1 the default so I didn't include it in the original.

[Poggicek]

It is still reproducable, you're fighting latency here though, the information about aim punch will always be desynced on the server from your client, just like tagging. The server will always be ahead of the client, so either server applies aim punch sooner than your client or your client sees aim punch after the server no longer does.

[thouravi]

@thouravi Did you test with loopback=1? The bug only occurs if loopback=0

There was an update a couple months after I made this post which made loopback=1 the default so I didn't include it in the original.

Hi, yes. I tested it with the default (loopback=1) before. Now, I tested it with loopback=0 and it still happens.