So it's a driver at fault then. The superuser link has an answer to the user's question where he suggests installing the Windows Driver Kit and running poolmon to figure out which pool is consuming the memory, and from there to figure out which driver(s) are using the pool.

You'll likely get a small list of suspect drivers, some probably packaged as part of Windows. Look at the non Microsoft drivers first because it's probably a fault from there.

Or if you have an AMD GPU you could probably just try updating or reverting to a different stable release and see if it's fixed.

Why don't you click on the "Resource Monitor" button/link on the screen? Then you can look at the table for memory usage and see what each user process is using.

You'll likely see memory usage low in the resource monitor (matching what you saw on task mgr). "Low" as in the usage doesn't add up to 14GB. This means the leak is probably from something running in kernel mode.

Here's a pretty good resource on diagnosing the driver at fault.
http://superuser.com/questions/533135/98-100-memory-use-no-process-uses-more-than-25mb

IIRC services are sometimes a bit funky about showing up on task mgr. If you see usage in resource monitor is high due to svchost, then it's a service at fault. You can use Process Explorer from SysInternals (available on microsoft's website) to figure out which service.

Do you have a DamagedPlayer event in your hudanimations? Try removing everything inside it so that it's an empty event.

Make sure you aren't generating mipmaps (check the flags for the VTF). Something odd about this that usually works is making your outline not a pure black. For example, using 0 0 0 220 RGBA instead of pure black 0 0 0 255 RGBA usually fixes this. If that works, try slowly raising the alpha from 220 up to 250. Alpha 250 often works for me.

Alternatively, depending on your crosshair and if you don't care about linear scaling, you could try the Point Sample flag. This will avoid the problem but you probably don't want this if you scale up or down your crosshair.

Check value of mat_fullbright in console

I think he's suggesting a brand new damage mechanic where the amby and only the amby can have a second-level critical hit? Amby does base damage 34 with crits 102. Raising the damage would be absolutely ridiculous because revolver has base damage 40.

@DatDrummerGuy, you're advocating for changes to a weapon that the top of HL honestly thinks is fine. Rather, top of HL thought was fine but most of the top have quit in the past couple years in both NA and EU. Sniper is broken in HL even with stock items. The class's primary weapons are too powerful. The fact that the class can survive a backstab is not what makes sniper broken in HL.

Valve has historically been slow with major item rebalances. With the exception of gun mettle, I don't recall them ever balancing more than a handful of weapons in an update (at least not for a number of years). The razorback isn't one that needs to be balanced before items like the wrangler or vita saw.

Probably because there are at least two dozen unlocks that need a rebalance before the razorback.

And there's also the problem that sniper in HL at the top level is pretty much the same with or without the razorback because the problem is the class's damage. Yes, without razorback the sniper will get stabbed a few times in a half but all of the situations where you can't push due to their sniper remain the same without the razorback.

But really there is so much more broken shit in this game that should be fixed first.

Something like...

bind j "toggle cl_crosshair_file crosshair1 crosshair2 crosshair3 crosshair4 crosshair5 crosshair6 crosshair7 default"

But that can't be used if you wanted cl_crosshair_file "" (the 'none' crosshair) because you cannot nest quotes and afaik, there's no support for a special delimiter in tf2 scripting. Instead you'd need something like

alias "xhair_file_now"     "xhair_file_none"
alias "xhair_none"          "exec xhair_none.cfg"    // xhair_none.cfg should have cl_crosshair_file "" and nothing else
alias "xhair_cross"        "cl_crosshair_file crosshair7"
alias "xhair_circle"       "cl_crosshair_file crosshair3"
alias "xhair_dot"          "cl_crosshair_file crosshair5"
alias "xhair_file_none"    "xhair_none;   alias xhair_file_now xhair_file_cross"
alias "xhair_file_cross"   "xhair_cross;  alias xhair_file_now xhair_file_circle"
alias "xhair_file_circle"  "xhair_circle; alias xhair_file_now xhair_file_dot"
alias "xhair_file_dot"     "xhair_dot;    alias xhair_file_now xhair_file_none"
// you can fill in the rest here
bind j "xhair_file_now"

Basically each alias sets the current crosshair and then changes the bind's alias to the next one in the cycle.

1. Launch TF2. Do _not_ launch casual or comp MM. Once those screens are launched and complain about prec, you have to restart TF2 to get past them.
   
2. Verify prec is loaded via "plugin_print" in console
   
3. If loaded, unload prec via "plugin_unload prec" or "plugin_unload 0" where the 0 is the index of prec from the plugin_print command output. Likely it's 0.
   
4. Verify prec is unloaded via plugin_print.
   
5. Now you can play casual or comp MM. They won't complain about you having PREC loaded.
   
6. When you have scrims or a match or something, you can load prec by "plugin_load addons/prec" from the main menu. Or you could just restart the game.

Or you could bind a key to "ds_record" and a key to "ds_stop" and just remember to press one key before your scrim/match and press the other after. ds_record will name the demo with a timestamp.

The scoreboard shows 6 players per team in minmode. You can toggle it in advanced options in game or via cl_hud_minmode console command.

The size of the hud crosshairs is determined by the font. If you look at the scripts/hudlayout.res file and find the crosshair you're using, you'll see a "font" property. That property is the font defined in resource/clientscheme.res. You could just duplicate that font's entry and change the "tall" property of the entry, or you could just modify the one that's there. Whatever you do though, make sure the crosshair entry in hudlayout.res is using the correct font.

Spend 20 minutes practicing with the lochnload and see if scoutany class is still a problem.

EDIT: Good luck finding people willing to practice against lochnload demo in MGE or DM though... Although that might change now.

At least the soda popper is still banned.

https://play.esea.net/index.php?s=support&d=faq&id=241

crosshair 1 in console and a nonzero cl_crosshair_scale (32 is default) inside your scripts. Your scripts are setting the scale to 0.

Quake Champions*. Quake 4 was released 11 years ago.

Diabotical looks more complete than Reflex, which is unfortunate for the Reflex devs. They've done some pretty impressive things over there (the ingame map editor and netcode changes), and Diabotical already has the map editor. I'd be happy if either of the games blows up in popularity.