Team fortress 2 validating every time
Compounding this, the ball has to travel really far in order to disarm players.Being hit by a long-range ball (more often than not) ends up feeling random, rather than skilled.The 1-second damage and accuracy penalty now applies to the first second of spun-up time, whether or not the Heavy is firing.Previously, the 1-second damage penalty would only be removed after 1 second of firing.These are just recent shots I've gotten) Has anyone else had these issues? Things I've tried to fix the issues: [list] [*] Validating Game Cache. Where text rather than an icon is used to indicate a controller binding, the text strings are now correct for non-Steam controller devices, and slightly more verbose in some cases to avoid confusion with regular keyboard bindings (e.g. "Press [B]") Added new action bindings for the most popular voice-line commands. no-penalty, on-demand launching of their target), and so their damage-potential can greatly exceed that of the other classes that also use this weapon.The default controller template now binds "Call Medic! The following voice lines are also available, but are not bound by default: "Go! Rather than take a heavier-handed approach to solve this, we've instead decided to remove airblast as a source for mini-crits. While playing Casual matches, any XP you earn will be matched and deducted from your overflow pool until it runs out. The main culprit seems to be the queued/delayed-fire aspect, which fights against the basic concept of the secondary slot on classes that can use this weapon (Soldier, Heavy, Engineer, Pyro); players generally expect a secondary that is immediately ready to fire - for the rare case where their main weapon isn't available (e.g. Pyros are too easily able to take advantage of this weapon's primary feature via airblast (i.e.
This might be okay given the trade-offs (risk-vs-reward of ranged shots hitting and the opportunity cost, no overheal).
Accuracy and damage penalties now reset when the Heavy spins down, rather than when the Heavy stops firing.
This means if you stay spun-up beyond one second, and fire in bursts, damage and accuracy will remain at 100%.
After updating to Windows 10, I've been using the same config and files for TF2 that I had from Windows 8.1.
The game ran perfectly fine back in 8.1 but for some reason after the upgrade I've been seeing these graphical glitches on every server I connect to.