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.

Yeah, I increased it to 21ms based on human tolerances to get a bit more in the buffer.

6.12.4 released with bug fixes and performance enhancements.

Changelog

Please remove the following from your launch options:
-threads
-limitvsconst
-gl_enablesamplerobjects
-gl_nv_bindless_texturing

6.12.3 released with bug fixes.

Changelog

Same! But in my case, I woke up early to pee and checked my phone and was able to cash out!

aa=medium and aa=high were removed, but I forgot to update the modules documentation. It is now aa=on.

Yes, Mouse Tweaks was renamed to Flat Mouse to help people better understand what the "tweaks" were.

6.12.2 released with bug fixes, quality of life improvements and documentation updates.

Changelog