What's new

Welcome to HvH Forum!

SignUp Now! Download Free HvH CS2/CS:GO Cheats, CFG, LUA/JS Scripts, And More!


SignUp Now!

Request discharging doubletap breaks lc?

Newbie HvHer
User ID
45474
Messages
3
Reactions
0
Level
3

hi its kind of a dumb question but anyway so its clear that after achieving origin squared difference thats bigger than 4096 makes the whole lag-comp window drop out.
anything recorded above the sv_maxunlag threshold is effectively is cut off but this wont break lc, just that record is tossed out basically (so dont ping spike above 200 lol its useless).
defensive lag shifts the simtime forward resulting backtrackentity to skip those ticks due to it being greater than flTargetTime.

so looking at this, in conclusion people who claim to break lc solely based on velocity on ground with scout (unmatched ppl) are completelty wrong? am i missing something? did the lagcomp get updated? correct me if im wrong on anything but that simply is not possible. please let me know!
 
Administrator
User ID
2180
Messages
450
Reactions
618
Level
50
yeah, sorta. the games lagcomp system invalidates bt records if the positional delta between current and stored origins is above 4096, which is a 64 unit difference. This is to abuse. im assuming this just seems like some sort of a sanity check. it wont actually break lc completely but rather that individual record is discarded from the interpolation buffer
 
Newbie HvHer
User ID
45474
Messages
3
Reactions
0
Level
3
yeah, sorta. the games lagcomp system invalidates bt records if the positional delta between current and stored origins is above 4096, which is a 64 unit difference. This is to abuse. im assuming this just seems like some sort of a sanity check. it wont actually break lc completely but rather that individual record is discarded from the interpolation buffer
so like if there hasnt been a 64 unit difference does this mean that no records are discarded from the interpolation buffer?
 
Administrator
User ID
2180
Messages
450
Reactions
618
Level
50
so like if there hasnt been a 64 unit difference does this mean that no records are discarded from the interpolation buffer?
yeah if there hasn't been a 64 unit difference between a stored backtrack record and the player's current origin then no records are discarded for that reason

buffer will keep all valid records, unless:
  • position delta exceeds 64 units (4096.0f squared) → record skipped
  • record is older than sv_maxunlag → record skipped
  • simulation time is ahead of the shot time → record skipped
  • record is invalid for other sanity reasons (e.g., dormant, dead, etc)
if none of those apply all records stay valid in buffer
 
Rookie HvHer
User ID
66737
Messages
72
Reactions
20
Level
9
yeah if there hasn't been a 64 unit difference between a stored backtrack record and the player's current origin then no records are discarded for that reason

buffer will keep all valid records, unless:
  • position delta exceeds 64 units (4096.0f squared) → record skipped
  • record is older than sv_maxunlag → record skipped
  • simulation time is ahead of the shot time → record skipped
  • record is invalid for other sanity reasons (e.g., dormant, dead, etc)
if none of those apply all records stay valid in buffer
nerd
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Top