me!

https://cdn.discordapp.com/attachments/389091098922057728/620277650946129930/mastercomfig.zip

mastercomfig 8.0.0-b4:

* Increased rate from 262144 to 281952 to add padding for split packets. Improves network reliability.
* Added a max accumulated network delay of 30ms (similar to the 15ms delay limit in 6.14). May cause some network resources to be exhausted, let me know if you see problems.
* Restored client precache from before experimental change in 6.12.0 to improve performance
* Removed some redundant to default filesystem settings, improves performance
* Updated screenshots on docs
* Fixed typos/style in documentation

https://cdn.discordapp.com/attachments/389091098922057728/619854792386281482/mastercomfig.zip

mastercomfig 8.0.0-b3:

Updated recommended base launch options: -novid -nojoy -nosteamcontroller -softparticlesdefaultoff -reuse -nohltv -particles 1 -primarysound -snoforceformat

* Added -primarysound and -snoforceformat to launch options. These reduce stutters related to the sound system.
* Improved networking compression settings to reduce overhead in packet processing on packet_size_balanced
* Decreased smoothing time to stay in sync with other entity's smoothing (interp)
* Increase rate to a stable speed that resolves stutters when dealing with larger traffic.
* When on packet_rate_congestion, don't do added interp for snapshots_balanced
* Optimized lighting settings
* Tweaked lip sync rules to ensure smoothing is disabled on lower modules
* Addons now override modules
* Enabled batch decals across the board for improved performance
* Reduced overhead of decal system when decals are disabled
* Improved decals_high usage of memory systems
* Added hud_panels module to disable health/player info panels
* Reordered console module selection execution to reduce delay up front in loading settings
* Removed Slow IO addons. These changes are now in the base config, because model loading in the thread pool was causing performance issues even on fast SSDs.
* Fixed color correction not being enabled on post_processing_ultra
* Fixed some unused software anti-aliasing settings being used
* Decreased dynamic light limits
* Fixed hud_reloadscheme once not working properly
* Renamed game_override_once_c to game_overrides_once_c
* Fixed typos in documentation and improved some descriptions slightly

https://developer.valvesoftware.com/wiki/Material_Types

- just makes it not found.

I disable impact particles using fx_* commands in the dxsupport_override.cfg in the low and very low VPKs.

I don't know why demos are choppy. Been trying to look at it for a while, but it seems like some TF2 issue? Could you confirm it doesn't happen without the config? But very low does lots of stuff that might be causing it

-particles 1 limits the number of beam particles (particles with a start and end point). It also allocates less memory for those particles. The minimum is 512, so 1 is just saving space.

A stable FPS is better than high peak FPS.
An FPS limit decreases loading screen time.
An FPS limit saves power which can improve performance due to resources not being used for little reason.
FPS has diminishing returns for higher FPS because the frame time reduction is inversely proportional.

I'd recommend setting fps_max to FPS you can stably get.

mastercomfig 8.0.0-b2
https://cdn.discordapp.com/attachments/389091098922057728/618702620940566528/mastercomfig.zip

* Enhanced networking settings to improve reliability
* Removed recommendation to disable networked packet thread (-NoQueuedPacketThread, net_queued_packet_thread 0) on Linux because Linux now uses the packet thread. Please remove these from your settings if you have them.
* Optimized graphics performance
* Fixed a few ragdoll bugs
* Optimized CPU performance
* Improved filesystem and memory management
* Improved sound system performance
* Disabled TF2 in-game HUD messages (mostly seen on cl_hud_minmode 0) with No Tutorial addon
* Disabled enforcing hit/kill sounds

https://mashable.com/2016/03/08/secret-service-trump-threats-twitter/
http://www.thesmokinggun.com/buster/obama-twitter-death-threats-486712
https://www.washingtonpost.com/arts-entertainment/2018/11/26/tom-arnold-says-one-anti-trump-tweet-caused-secret-service-show-up-his-house/?noredirect=on
https://supreme.justia.com/cases/federal/us/394/705/
https://en.wikipedia.org/wiki/United_States_v._Stickrath
https://www.law.cornell.edu/uscode/text/18/871
https://casetext.com/case/united-states-v-apel

91 doesn't exit. There's only 90 and 95 for PCs.

DX9 is the latest graphics API, with more efficient resource handling. The only reason why DX8 gets more frames in some cases is because it can't support rendering some things, so it uses less advanced graphics. If DX9 were able to fallback to those simplified graphics, then it would have greater performance. But simple FPS comparisons are not what you should base things on anyway. Due to DX9's better technology, you get less stutters, smoother frame rates, and faster loading and window resource grabs.

DX8 is also a huge technological burden to maintain for the TF2 team. If we get usage numbers down for it, that would be a possible graphics pipeline they could drop support for, and thus improve efficiency by removing all those outdated pathways and not worrying about compatibility.

@Cache11031992 use the defaults in mastercomfig. I'm not making the defaults purposefully worse.

Anyone who has been having crashing issues when they join a game: which version was the version it started happening and which version was the last one that was working for you?

Is this only happening with in-game notifications or does it happen if you have a notification at all?

Yeah jump maps are fine at 15.2ms because it's just your own client which is locally predicted.

If you want.

Not seeing anything faulty there. Everything related to lerp time is a float with no discarding. Also the fact that we experimentally tested it on a server with no issue leads me to believe this only happens on bots.

But you're always going to get packet loss on 15.2ms. There's not servers that ever have a 66 sv tick rate and 0ms var. Also, placebo has a big impact on this stuff. You need to do blind tests, or analyze it logically/mathematically using the code.

6.14.1 released with bug fixes.

Changelog

Just curious why you'd like 15.2ms, it'll help me improve the config.

Read this thread on why 15.2ms is not the default: https://www.teamfortress.tv/51693/current-year-net-settings#4

If you really want it, put snapshots_lan for each class config you want 15.2ms for, or if you want it for all classes, put snapshots=lan in your modules.cfg.

That's a good point. My current inclination is to say that it doesn't matter on the receiving end as much because your own movement is not interpolated. However, I'm not sure. Will have to see the pros/cons more.

The module is silly_gibs=on.

6.14.0 released with a new in game customization system.

Changelog

I've now opened up ways you can support me:

• Ko-Fi: https://ko-fi.com/mastercoms
  
• Liberapay: https://liberapay.com/mastercoms/
  
• Gift items: https://steamcommunity.com/tradeoffer/new/?partner=85845165&token=M9cQHh8N

Support is much appreciated and super encouraging to me! But thank yous always mean a lot to me, too.

Yeah, because hitscan has pretty much no downside with interp. It's fully lag compensated. With 30.3ms, you get guaranteed protection against packet loss and slightly more predictable/stabler entity movement.