The 01/12/16 update broke some scoreboard elements for me. Uncommenting the "spacer" property resolved this issue. The default value of "5" seems to work just fine.

Also: I voted Option 1 for the item meters because I believe preserving the health-ammo spacing is more important than preserving the size of the item meters. The screenshots are misleading because of varying ammo counts, but both Option 1 and Option 6 will result in double-digit ammo being tightly aligned to the item meter, with regular spacing between health and single-digit/no-clip ammo. Given that the majority of 6's classes don't even use an item meter, plus the fact that many of your other HUD elements are aligned with the current ammo positioning, I feel it would be wiser to modify the item meters and leave the other elements as they are.

It's difficult to say for certain without access to your scoreboard.res file, but you're probably missing one of these entries under "scores" in scoreboard.res. You don't need to have these exact values (the ones I listed are the default values), as long as they're all included. If you have "status_width", be sure to remove that, since it was disabled in the Tough Break update.

"medal_width"		"20"
"avatar_width"		"65"
"spacer"		"5"
"name_width"		"118"
"name_width_short"	"85"
"nemesis_width"		"25"
"class_width"		"25"
"score_width"		"30"
"ping_width"		"25"
"stats_width"		"30"
"killstreak_width"	"15"
"killstreak_image_width" "15"

Haven't had a chance to look at what the root cause is, but a simple short-term fix if you want to keep your scoreboard is to rename scoreboard.res to something else, hud_reloadscheme, restore the name back to scoreboard.res, and then hud_reloadscheme again. This needs to be done again if you exit TF2.

And in response to StaticVoid's post, my scoreboard was affected (SolarHUD in 4:3 aspect ratio).

I believe it also affects Pomson w/ Pistol.

wrong subforum

Is this new information? The Q&A video mentioned that certain commands would be restricted.

Another issue I've found is that the item meters clip if you have double-digit ammo in clip, e.g. Cleaner's Carbine.

The default FOV is 75 (and people still use it) because that's how the game is supposed to look. We know Valve is trying to standardize the appearance of TF2, which is an overall GOOD thing; the last thing we need is a higher FOV cap which, aside from radically altering the appearance of the game, also impacts actual gameplay.

I'm honestly surprised that they'd allow custom HUDs in matchmaking, and those don't affect gameplay at all.

On a related note, I'm also glad they're restricting viewmodel_fov to 75 (in matchmaking). I don't understand how completely broken viewmodels at viewmodel_fov 90 are considered "acceptable" production value by casting organizations.

It does get pushed slightly to the left when capping more than x1, so there might be some way to push it completely off the control point. Another suggestion might be to change the icon; maybe a smaller or less opaque image would be a better fit.

Why the chat modifications? I assume it's for mp_showrespawntimes, but that command has been blocked as a cheat for a while now. Edit: the chat text size is just hugely resolution dependent; pretty much unusable at 640x480, the other modifications are fine.

It's nearly impossible to tell if someone is capping at a x1 pace since you removed the cap image, and no numbers appear for a x1 cap.

There are also a handful of glitches in a 640x480 resolution and/or non-widescreen aspect ratio:

1. Chatbox is too large vertically, barely clips ammo, only fits one line at a time (due to low resolution)

http://imgur.com/tL7yFIn.png

2. Scoreboard playerlists are misaligned and show only 5 players (due to low resolution) [Fix for 640x480]

http://imgur.com/wL08HE9.png

3. KOTH active timer BG doesn't align with timers (due to aspect ratio) [Fix]

http://imgur.com/KxpaBug.png

4. Red team's name label is off-screen (due to aspect ratio) [Fix]

http://imgur.com/ZPAF8L2.png

I prefer using mat_monitorgamma 1.8, and have it in my autoexec. Every time I ALT-TAB, the game appears to switch to mat_monitorgamma 2.2, but console still displays the value as 1.8, and entering "mat_monitorgamma 1.8" does nothing; I have to change mat_monitorgamma to another value, and then change it back to 1.8.

I don't have mat_monitorgamma in any config file or in the launch options.

I tried using mat_monitorgamma 2.2 with mat_monitorgamma_tv_enabled 1 and mat_monitorgamma_tv_exp 2.3, but this encounters the same issues. I normally have mat_monitorgamma_tv_enabled 0.

Not counting double-donks, a Loose Cannon direct deals a maximum of 50 damage. Somehow, Loose Cannon rollers are doing more than that.

Drivers have already been updated.

Ever since upgrading to Windows 10, I've been experiencing freezes that come every 5-10 minutes and last 30 seconds or more. Sometimes I can move my mouse during the freeze, sometimes not, but I can't interact with anything and Ctrl+Alt+Delete does nothing. Usually after it unfreezes itself, my internet connection will stop working and I'll have to reconnect. I haven't had it happen while playing TF2.

According to online searches, it might be caused by faulty display drivers; however, they usually involve NVIDIA drivers, whereas I have integrated Intel graphics. I've also heard it could be f.lux, but I've had this problem without f.lux installed. I didn't see anything obvious when looking at Task Manager directly after a freeze.

Things I've tried:

• reinstalling display driver
  
• resetting Windows post-upgrade
  
• replacing Razer Synapse with legacy drivers
  
• disabling f.lux

Does anyone have a similar problem or know of a solution?

Increase your standards. Most HUDs are garbage. There are like 10 worth-while HUDs, even fewer being actively maintained.