What degu said. net_graph doesn't show you the server bounded interp, only the initial client side calculation, which is then changed based on the server telling your client to clamp your interp. If you really had 0 interp, players would be jumping around with no continuous motion, and you should realize that if you understood what interp did.

And pro players using something doesn't mean it's correct. Many people have misunderstandings of these commands and it's just what they've been playing with for a while. Many configs have clearly bad settings all over the place, like rate 60000, which is lower than the default rate of 80000, yet many pro TF2 players use configs based on those settings.

Please show me one YouTube video where it shows you need to lead targets with hitscan. With projectiles, it is a different story, and I think any demonstration you show with negative effects will have a super high interp to show the extreme effects. But as I said, there is no adverse difference in position within a few milliseconds due to max velocities in TF2.

It's obviously placebo in your case, if you say there's a difference past 10ms. The lowest TF2 can go is 15.2ms. There is a reason why interp exists, and why I have that recommendation. Extrapolation is much more harmful than interpolation, especially since you have server frame rate drops and variance regularly on most servers.

The latest version of the config has 17.9ms interp, not 21.

The server is aware of and accounts for client side interpolation latency, so the hitbox argument is invalid entirely for hitscan. And for projectiles, the difference of like 2ms latency does not adversely affect hits, as accurate trajectory is of utmost importance, rather than accurate position within 2ms, since projectiles have a travel time.

Those are low violence settings. Please turn on all violence_ cvars to 1 so you don't enable low violence mode, which enables this and other silly gib effects.

If you're using mastercomfig 7 with just modules and no custom settings, I just pushed a fix removing those violence_ cvars, as I had mistakenly kept them in while testing something.

Since all the game's voicelines use mp3 files, you can remove the miles library that Source uses for playing them. If you move bin/vaudio_miles to somewhere else (to back it up), the game will no longer be able to play voicelines, as well as music and some additional ambient sound effects.

If you want to restore the original behavior, just move vaudio_miles back to the bin folder.

I'm going off of memory here so this might not work, but I'm pretty sure it will.

edit, sorry the file name is bin/vaudio_miles, not bin/libMiles

Thanks!

This is an incomplete UI feature.

Not sure why that would happen.

I haven't found a good way to apply anti-aliasing settings.

Check tf/cfg/config.cfg and your regedit if on Windows (HKEY_CURRENT_USER\Software\Valve\Source\tf\Settings\mat_antialias).

tf/cfg/app/profiles/default/custom

mastercomfig 7.0.0-a.15

This was already solved on Discord. They forgot to set their rates using the rate generator.

Hi, what version of the config did you install? 6.9.0?

Profiles are in the works.

New format was revealed for this week's Summer Skirmish. Pro players queue up for pub solo matches and get points for the tournament based on kills and if they win.

https://www.epicgames.com/fortnite/en-US/summer-skirmish
https://www.epicgames.com/fortnite/en-US/news/summer-skirmish-week-2-standings-friday

Yes, the checkbox is to say "i want to set this setting manually and override what this module sets", and then the toggle is what value you're setting the option to.

Yes I saw, I'm still looking into it.

Hi, this should have been fixed since 7.0.0-a.12. Could you help me debug this issue by opening dev tools and typing this into the console and sharing the output:

require("systeminformation").graphics().then(data => data.controllers.forEach(card => console.log(card.vendor)))

The app doesn't have a stable release, it's still an alpha, as I said. What is stable is 6.9.0, which is mastercomfig before 7 came out, with some of the config fixes/optimizations I had done to 7. I released this because there were some problems with the previous stable release, 6.7.0, and I wanted to fix those issues for people who don't want to test out an alpha.

This would be a completely different issue from the one you quoted. But I'm not getting that issue. I have the toggle set to on, and it loads the no tutorial config into my client-custom.cfg. There is, however, an issue where you can't disable a community config.

Do you have -dxlevel in your launch options? If so, remove it.