Could you clarify what you mean?

Yeah I'd still use null movement, it was just a neat fact I thought I'd bring up in conversation. The amount of input delay it adds is so small compared to the benefits and the possible increase in responsiveness due to brain/finger delay for releasing keys :)

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

Update on the fixed weapon spreads: it resulted in worse play than normal, since the fixed seed for the weapon spread could be terrible to aim with, while a randomized seed plays better, since there's even chances of god spread and bad spread, so you aren't stuck with any one spread. It's pretty hard to find a seed for a pattern that's truly "average", so I think randomization is a better way of averaging this out than a fixed one.

Also about multi-threading, I don't think Source really needs much more multi-threading than it already has

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

playtesting here: connect tf2.mastercomfig.com

playtest over, thanks all!

Just sent an email to Valve with a fix.

I'd like to see how it plays in practice. It's not exactly CS:GO spray patterns.

I'm personally able to connect to casual and many other mastercomfig users are able to as well. What version, preset and addons were you using? Any custom settings like modules you had?

You can probably use the preload settings from mastercomfig if you aren't already.

Essentially checked mat_antialias > 0 for initializing anti-aliasing (ultimately ended up disabling it anyways), and on AMD cards on Linux and macOS, it did a full color clear which was only intended to happen when anti-aliasing was enabled.

Now it checks for mat_antialias > 1, which is what the game sets in the video options menu (mat_antialias 1) for Anti-aliasing: None.

Hopefully this anti-aliasing fix is less controversial :)

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

Also, the first Team Comtress 2 playtest is live!!! connect tf2.mastercomfig.com

EDIT: server down now! thanks for playing, we learned a lot!

I'm not saying the visuals are placebo, obviously they are not because they can be recorded and shown. But I am just saying that the assumption that it is a reduction in ping that causes that may be placebo, because the projectiles spawn at the same time when recording it.

I think there's a few misunderstandings here. So the initial claim that I was disputing was that the 0 lerp exploit lowered ping:

As shown by my two videos, this is not the case. This is what I was addressing when I said "it was either placebo or parroted from someone else". There is no difference in projectile delay. Waldo's video does nothing to refute the original point (as you say 100%). It only proved that you could see your stickies while moving fast. So now the whole discussion is about how you can see your stickies while moving fast, still inferring that there is somehow a difference in projectile delay while moving. Honestly, that doesn't make sense to me. If projectiles are spawning at the same position and delay on either setting, that means something else must be different. That means the only way you could see your stickies with projectiles being the same (as proven by my video) is if you yourself were behind.

So ironically, that high update rate exploit is behind normal values because of how the game handles extremely low interp values, so you could be a few frames behind, depending on your frame rate.

Probably same reason they encrypt the weapon script files. To make TF2 a distinct thing you can't modify the integrity of, without actual mods/addons. I wish they did open those things up more, so that the community can experiment, but I'm not sure if it'll be done.