Not really a solution, but if you want to easily double-check if you're actually losing packets you can use net_showdrop 1. A message will be printed to the console every time a packet is lost.

1st step is always to verify game cache.

If that doesn't fix it, try other games and look for artifacts, you may have bad gpu memory.

also:

Valve fixed this recently (I believe with the gun mettle update). All quotation marks in chat are converted to single quotation marks, making it impossible to escape the chatbox's say command.

You haven't even used it yet.

Anyone else getting this? When playing on dx8 on windows 10 with the latest nvidia drivers, closing TF2 results in an instant bsod with the error message VIDEO_MEMORY_MANAGEMENT_INTERNAL. Just recently tried using dx8 and I really like how smooth it feels compared to dx9, unfortunately this makes it unusuable. Any ideas?

2639 frames 11.506 seconds 229.35 fps ( 4.36 ms/f) 11.492 fps variability

2639 frames 11.525 seconds 228.98 fps ( 4.37 ms/f) 11.855 fps variability

2639 frames 11.643 seconds 226.65 fps ( 4.41 ms/f) 11.369 fps variability

2639 frames 11.843 seconds 222.84 fps ( 4.49 ms/f) 11.428 fps variability

2639 frames 11.825 seconds 223.18 fps ( 4.48 ms/f) 12.324 fps variability

You are comparing a difference of, at most, 75 nanoseconds.

You can remove cl_lagcompensation and cl_pred_optimize from your config. Those are non-archived cvars, so there's no point in setting them to their defaults.

cl_smooth and cl_smoothtime are purely preference, but if you're disabling smoothing then there's no reason to include cl_smoothtime in your config.

tickrate is purely a server command, and iirc it doesn't even function on TF2 without modifications, so go ahead and remove that from your command line.

Your cl_interp and cl_interp_ratio values are conflicting. Interp is calculated to be max(cl_interp, 1 / cl_updaterate * cl_interp_ratio). It's still important to set both, as some poorly thought out networking settings in league configs (cough ugc) force cl_interp_ratio to 1.

Generally, cl_interp 0.033 is recommended for when you have cl_updaterate 66. If you're using cl_updaterate 66.6666, then you should try cl_interp 0.03 ( 1 / 66.666666666 * 2 ) and cl_interp_ratio 2. At least, that's what I use. There's many different opinions on what the "best" networking settings are.

Pretty big thing to not be specifically listed in the changelog.

you can build here

http://images.akamai.steamusercontent.com/ugc/425941828283918292/A53EFDC02D6CE19A8F5639F73CDCB0D36ED5C78D/

???

Aspect ratio has very little to do with FPS. The number of pixels (width times height) your GPU has to render is what uses up frametime (assuming you're not cpu limited)

Source: sv_cheats 1, play with r_aspectratio (0 is automatic)

IMO, logs.tf's damage stats (except for spy, where the backstab would have killed them no matter what) are a more accurate representation of your quality of play, and sizzlingstats are a more accurate representation of how you played against a specific team alongside your team. If you go crazy hitting meatshots all over the place, but your opponents were already at low health, sizzlingstats would report that your damage was fairly low, as if you had been missing a lot of shots. It's not your fault that your opponent's health was low, and logs accurately reflect how much damage you *would have done* on shots that killed them.

the circlejerk is real

*downvotes incoming*

If he damaged his cpu from heat, programs and/or the OS would be crashing. There would be no effect on clock speed or performance.

nice use of youtube 60fps

In what way would this help the OP? VGA does not support 144hz...