The player speeds or angles aren't even consistent in the videos, which is super important when your entire premise of argument is based on visual positions (hint: you might be shooting your sticky at a different angle and speed than what you're travelling at). This is especially important when you're talking about a change in time which could be at most 15.2ms. Please let me know when you've done me the same favor of preparing specific test cases as I have done for you.

https://cdn.discordapp.com/attachments/389102232747900929/746811319214407720/high_update_rate_exploit.mp4

https://cdn.discordapp.com/attachments/389102232747900929/746811333248286791/normal_update_rate.mp4

300 FPS videos, so I can't upload to YouTube.

Notice the higher ping when using the update rate exploit, and also tell me if you can even see a difference between the two projectile spawns. The crosshair turns blue when I press mouse 1.

Anyways, someone was talking about how interp was ping. It's not. It's a client side delay, and doesn't delay what you send to the server, like actual ping does. The update rate exploit increases ping, which actually delays what you send.

When someone long ago told me about the benefits of this for jumping, he had tested on a local server, and I had assumed he was right without testing further. On a networked server, it's different. Furthermore, due to clientside prediction, the supposed benefits of reducing interp past the game simulation rate are even less to non existent, with all the downsides and more still being there.

Whatever you thought was happening, it was either placebo or parroted from someone else. And you insulted another human being because of it, for practically no reason.

Because that's the server restrictions and you shouldn't be able to bypass server restrictions by default. You don't really get any sort of lower ping, because it shows you a different state than anything you'd get in the future with interp, due to it being extrapolated and/or teleporting client side rather than being what's happening on the server.

And now, if the server allows it, there won't be lag compensation issues anymore because this change acts as a forcing function to have correctly synced interp values. So it's allowed in cases where it wouldn't cause any issues beyond just the normal lack of interp.

What happened before was just a shitty workaround for a client or server misconfiguration. Now you actually have to have both in sync. Furthermore, with higher update rates, it actually improves the behavior of lower interp values because server data can be sent as fast as possible according to the network tick, rather than being limited by the snapshot rate of max 66, like it was before because update rate on its own was bounded by server settings.

So in conclusion, instead of pretending there isn't a problem, it shows an issue which can be properly resolved for a better result than the previous bypass.

So why did you mention tourney servers and not jump servers? Jump servers are a whole different thing and I agree that in those cases, the server owner should allow for that to happen or you can use a local session. But for the vast majority of cases, which is what we're talking about when we discuss game defaults, this is a good change.

Only if you want the client to extrapolate entity movement with no server data (bad idea). This is a good change that I reported to Valve a few weeks ago because of the server desync and lag compensation problems it could cause.

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.9

Cursed video no professional Team Fortress 2 online video gamer should see: https://cdn.discordapp.com/attachments/743724583697383435/745764291675816146/Half_Life_Source_2020.08.19_-_18.00.37.06.mp4

(working on getting live client parity, with comtress now supporting the latest TF2 assets (excluding HUD) and item schema!)

I added a form to submit requests! You can continue to use the forum if you want, but I thought I'd include a form to make tracking somewhat easier because atm I'm getting overwhelmed https://airtable.com/shrVvwlQ6Bl7F5VRk

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.8

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.7

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.6

What's a wallbug?

Seems like pretty much all glaring performance problems should be fixed by the next release (though please let me know if you still have issues, especially on low end hardware). I'd like to some help prioritizing future tasks so let me know:

What things would you like from Jungle Inferno and later?
What features/fixes would you like from CS:GO's engine?
What TF bugs would you like fixed? (excluding le demo det fix meme, I'm already certainly aware)

For those of you who have given feedback already, thank you, I'm investigating most of what you all have mentioned already!

@mlns r_worldlightmin 0.0002

@Chris_ if you download a new preset you have to delete the old one. For example if you have mastercomfig-low-preset , you can delete that one and download mastercomfig-medium-preset for example. If you are using the pre_comfig approach you don't have to download anything.

hud_panels=on in modules.cfg