What if TF2 ran better? Would settings restrictions be ok then?

9.0.0 released with new customization UI and performance optimizations.

Changelog
Support me

This release took 63 hours to produce. If you like the work I do, consider supporting me!

I hope the Team Fortress 2 competitive community takes the hint and starts shifting over to Mannpower leagues. It's the only way we will get a Valve Major.

You should be able to update the model, not sure though.

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

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

When rewinding back in time to approximate the view the player saw when they took a shot, Source has a limit, so the game doesn't always "favor the shooter" past a certain point when their ping (or fake lag) is too high. So it will only rewind back 200ms instead of a full second.

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

Come join us! connect tf2.mastercomfig.com

Testing on Suijin!

https://cdn.discordapp.com/attachments/389091069091905546/759920979710967849/Team-Comtress-2-main-menu.mp4

edit: im getting 160FPS ON 32 PLAYER SUIJIN

What are your launch options?

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

Yeah, it doesn't affect anything graphically. It does cause the same reload that mat_antialias does though, but I haven't blocked it because HUDs don't use it.

Usually HUDs will have a wait command which delays toggling mat_antialias, and this causes a material system reload. This is usually to force removing the dimmer on the main menu, which is not worth the material system reload, which causes unoptimal reinitialization and some rendering/HUD bugs. For example: https://github.com/n0kk/ahud/blob/master/cfg/valve.rc#L22

You can disable this behavior for HUD editing by adding alias block_antialias in your autoexec.cfg, or you can use mat_aaquality.

It's not substantially different, but it will increase water quality at a distance, lighting detail extremely slightly, sound quality, and contains system optimizations which don't affect quality which may increase FPS/prevent drops.

Got rid of a huge bottleneck for particle simulation!

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

We're playing on connect tf2.mastercomfig.com!

Because the only thing carrying the iron bomber to total domination of the GL meta is this one unintended stat (not any sort of interesting new mechanic), and if it was fixed, then we could see more variety based on the mechanics of different rollers. These weapons you mentioned are completely different classes of utility versus the stock (especially the melee weapons), so I find it misleading to mention these examples.

I mean within the context of changing/keeping ONLY the Iron Bomber being our sole balancing tool, which is what I understood #92 to be saying. Being that if we think Demoman needs a nerf, nerf the Iron Bomber, if we think Demoman is fine, keep the IB how it is.

But the balance is much more complicated than that. I see this more of a discussion about GL balance as whole, rather than just about the Iron Bomber. At this rate, Demoman is going to become an IB only class, so talking about the IB in vacuum vs the other grenades is not useful. I think the two valid sides to this discussion are either you think what the IB has in radius is good for the game, and should be applied to the other GLs, because it makes no sense to force everyone to pick a single GL when there would be some valid choices all other things held equal. Or you can think the IB radius is bad for the game, and in that case, it should be the same as stock.

I don't think there is a valid argument for keeping them different, but hopefully recontextualizing the debate into two sections: should they be different, and then if not, should we use the stock or IB hitbox, will produce better discussion.

I think people are more concerned that because IB is just better for directs, when it shouldn't be, people are going to have no choice but to go with it in most situations because of the hitbox. Whereas it shouldn't be the hitbox size that determines what to pick, but the behavior of the rollers. And now that this is becoming common knowledge, IB is just going to become the definitive pick rather than something most people use because it feels better but they don't exactly know why they use it.

Veering off into discussion about base Valve balance and if it's legitimate is irrelevant in this discussion. The fact is Valve did add a hidden stat to the IB which makes no sense for it to be different and on its own, isn't an interesting part of the unlock, and isn't intended. The discussion is purely about the existence of a difference, not if the base value is good or bad. There unequivocally should not be a difference in hitbox size for stock and IB. The base value can be up for debate.

So, this discussion about demoman buffs or nerfs is kinda irrelevant. Pick which one you want, and make the rest of the GLs on the same level as the IB, or the IB the same level as the rest of the GLs.

Kisak is not affiliated with Valve. They are a community moderator for the GitHub Issues. Don't just see that the issue is on GitHub, and decide that's good enough. Please email the TF Team and Eric Smith directly with your feedback about this issue and illustrate how important it is to you that this gets fixed. This helps the TF Team see how important an issue it is to people. It is a surprise to many how few people and how few issues actually get reported to them, because of assumptions that the team has already seen some issue because of this or that.

Here are links for your convenience.

https://www.valvesoftware.com/en/contact?contact-person=TF%20Team
https://www.valvesoftware.com/en/contact?contact-person=Eric%20Smith