I did this about 6 months ago and have streamed with it + sent it around; I'm surprised someone else made one independently.

You don't need to have 10000 frames since you can do each digit individually with some arithmetic.

Here's the proof-of-concept which I've been using, no comically large textures needed:
https://mega.nz/file/oe5yELKB#Wc5HRl7PW1DZjgynS-tpqrOP9_k8cx-PRd7-tUIrrXc

The speed you get from the material proxy is an absolute speed, so there is no way to convert it into components and make an x/z-only speedometer like the speedo plugins in jump servers. There's a PlayerPosition material proxy which you can split into components, but it's ultimately not useful since there's no way to take the derivative using material proxy math.

https://mega.nz/file/ED4GXR5J#oQh8jASy7OFIh7zeUTpYvE2B3cczLz3b8zKU3Bk2mXM

You can't jump when unducking from full duck in tf2 if grounded, so it will just unduck if you're grounded and wait too long. This works for partial duck-> jump (e.g. ctapping) or for aerial unduck->jump (jumpbug).

alias jumpbug "+duck; bind space +jumpbugjump"
alias +jumpbugjump "-duck; +jump"
alias -jumpbugjump "-jump; bind space +jump"
bind c "jumpbug"

the answer is literally just ad revenue. people watch videos less if they can infer low quality before clicking

the fact that anyone would believe The Official YouTube Blog about this is astounding

cp_sunshine_rc1a: https://mega.nz/file/kHBgFLCT#mwglQOJYgsPzTzNb5Jp5-9m0e3mk_VAMzWtHZMhR3ag

see: https://www.teamfortress.tv/60313/server-list-a2s

shitty software developers will always manage to make exponentially better hardware feel like a 5% improvement

proof of work systems should be outlawed by international treaty

Total logs seen: 2761285
Sixes overall data:
red:
Wins: 687879/1505856 = 0.45680264248374347
Loss: 702667/1505856 = 0.4666229705894853
Ties: 115310/1505856 = 0.07657438692677122
blu:
Wins: 702667/1505856 = 0.4666229705894853
Loss: 687879/1505856 = 0.45680264248374347
Ties: 115310/1505856 = 0.07657438692677122
By map:
process
red:
Wins: 211045/472281 = 0.44686320220377274
Loss: 221659/472281 = 0.46933711074550954
Ties: 39577/472281 = 0.08379968705071769
blu:
Wins: 221659/472281 = 0.46933711074550954
Loss: 211045/472281 = 0.44686320220377274
Ties: 39577/472281 = 0.08379968705071769
((product)|(viaduct))
red:
Wins: 144088/293807 = 0.49041717862406276
Loss: 144784/293807 = 0.4927860806583914
Ties: 4935/293807 = 0.01679674071754587
blu:
Wins: 144784/293807 = 0.4927860806583914
Loss: 144088/293807 = 0.49041717862406276
Ties: 4935/293807 = 0.01679674071754587
((snake)|(snack))
red:
Wins: 121982/269120 = 0.453262485136742
Loss: 124347/269120 = 0.4620503864447087
Ties: 22791/269120 = 0.08468712841854935
blu:
Wins: 124347/269120 = 0.4620503864447087
Loss: 121982/269120 = 0.453262485136742
Ties: 22791/269120 = 0.08468712841854935
ultiduo_baloo
red:
Wins: 77280/162308 = 0.47613179880227713
Loss: 81457/162308 = 0.5018668211055524
Ties: 3571/162308 = 0.022001380092170442
blu:
Wins: 81457/162308 = 0.5018668211055524
Loss: 77280/162308 = 0.47613179880227713
Ties: 3571/162308 = 0.022001380092170442
villa
red:
Wins: 2089/4807 = 0.43457457873933847
Loss: 2246/4807 = 0.4672352818805908
Ties: 472/4807 = 0.09819013938007073
blu:
Wins: 2246/4807 = 0.4672352818805908
Loss: 2089/4807 = 0.43457457873933847
Ties: 472/4807 = 0.09819013938007073

https://clips.twitch.tv/CrypticWimpyRuffOMGScoots

Patched as of August 21st; server operators can change sv_maxupdaterate if they want old behavior.

https://www.teamfortress.tv/10097/when-is-it-time-to-quit

Remove CPU cooler + GPU (and any other PCIE devices), probably also hard disks/disk drives/anything else shock sensitive

Pack all of that into your carryon along with peripherals. Computer case (with motherboard and other remaining 'secure' hardware) goes into a large suitcase packed with clothing.

Can also ship the case in its original box/padding ahead of time, but that's more expensive than checking it in my experience.

Source: I've done this >15 times in the last 4 years.

Immediately discarding reero's video, calling everything a placebo, and immediately doubling down when contested were all very much not "trying to figure things out." I don't doubt that mastercoms has a very good understanding of how the game works, but in this case she was wrong and it's massively harmful for a trusted community figure to double down on something that's simply incorrect.

In this case the result of playing with zero lerp was well known by the jumping community for a long time, regardless of how well understood the mechanism was. I'm only trying to make very clear that there is a real benefit to sub-15.2ms lerp.

The patch is not necessarily a bad thing; it would be strictly better to have servers run a higher sv_maxupdaterate than to rely on the exploit- this seems to fix some of the jitter from the exploit. However, it's important that we respond to this patch by doing that instead of just leaving the default.

It's worth figuring out what the actual downsides to very high sv_maxupdaterate settings are; sub-1ms lerp requires around 15x the default so it's worth checking that it doesn't harmfully increase server load or allow for any funny hitreg sillyness.