https://github.com/mastercoms/mastercomfig/releases/tag/6.8.0b5

And this did not happen on b3?

Also, what modules were you using?

Just some output spew that is labeled as an assert. Not much realistically.

Yes

Party force update and HUD reload, as mentioned in the change log. The other one that was not already there is compacting memory.

New cvars point to what was fixed:

sv_max_dropped_packets_to_process        : 10       :                  : Max dropped packets to process. Lower settings prevent lagged players from simulating too far in the past. Setting of 0 disables cap.

Fixes timeshift hack

sv_max_usercmd_move_magnitude            : 1000     : , "sv"           : Maximum move magnitude that can be requested by client.

Fixes players moving too fast (most of the time due to accumulating movement from lagging)

sv_quota_stringcmdspersecond             : 40       :                  : How many string commands per second clients are allowed to submit, 0 to disallow all string commands

Fixes a DoS attack

sv_signon_dos_disconnect                 : 20       :                  : Number of extra signon state confirmations required to disconnect a misbehaving client.

Fixes another DoS attack

They also changed tf_autobalance_dead_candidates_maxtime from 20 seconds to 15 seconds, which means it will wait 5 seconds less for people to die before forcibly switching autobalance candidates.

A screen overlay is a texture that is put on your whole screen. Think jarate or afterburn. This command was used by server mods to do some screen effects, but some of them tried to clear the screen using 0 which didn't do anything, instead of using off. Now, 0 also works so the mods don't have to be updated to properly clear the screen.

They also added some GDPR stuff to the protocol and added more rate limits internally (to prevent DoS attacks).

Could you launch TF2 with the -condebug +cvarlist launch options? Then send me your console.log in the tf folder.

https://github.com/mastercoms/mastercomfig/releases/tag/6.8.0b4

What's your launch options and dxlevel? Also make sure you have r_pixelfog 1

Disables a few debug systems.

I'm expecting it to be out about 3 days after this Internet outage is resolved and I am expecting it to be resolved on Thursday. So if everything goes to plan, June 10th.

mastercomfig 6.8.0b3 https://github.com/mastercoms/mastercomfig/releases/tag/6.8.0b3

It's very possible that mastercomfig 7 will not be releasing on June 7 due to an Internet outage. Sorry for the inconvenience this may have caused you.

mastercomfig 6.8.0b2 https://github.com/mastercoms/mastercomfig/releases/tag/6.8.0b2

Today I am releasing mastercomfig 6.8.0b1. This is a prerelease which has extensive configuration changes that need to be tested in preparation for their release in mastercomfig 7.

I would love to get your feedback on the performance of the config to ensure mastercomfig 7's release is as smooth as possible.

https://github.com/mastercoms/mastercomfig/releases/tag/6.8.0b1

It doesn't do anything for TF2.

You know that you can be banned from Casual+MvM as well?

The unity example in the video is very misleading because most PC games factor in delta time when running updates or run at a fixed rate. The beneficial effects of it come from polling multiple times, leading to higher responsiveness, not faster movement.

yes, it has 3 separate frames instead of 2 so theres more delay from what your gpu last rendered

also Dota 2 has a an experimental option to reorder logic to prevent latency from vsync: https://dev.dota2.com/showthread.php?t=184108

half life 3

Try snd_mixahead 0.08