Try hardware decoding with some variation of mpc-hc setup.

Is this thread about the benefits and shortcomings of different formats now?

8v8 with classlimits of 2.

In all seriousness though even if there's no classlimits in MM, skill ranking (you know, the "matchmaking" part) will take care of everything and put format players with other format players.

"Waaaa I can't get an unfair advantage anymore"

░░░▄▀░░░░▄▄███░▌▀▀░▀█
░░▄█░░▄▀▀▒▒▒▒▒▄▐░░░░█▌
░▐█▀▄▀▄▄▄▄▀▀▀▀▌░░░░░▐█▄

It has always been like this. If anything, it should be restricted to 0.015-ish, but it's not because you set your cmd and updaterate to impossible values. Either way, the engine will use the 0.015 value because of cl_interp_ratio 1.

>sv_client_min_interp_ratio 0
>sv_client_max_interp_ratio 2

These do literally nothing as a client, remove them.

The net settings you actually get (and have always gotten) with the settings you posted are these:

cl_interp_ratio 1
cl_cmdrate 66
cl_updaterate 66
cl_interp 0.015152 // rounded

If you feel a difference between these and what you're using right now, it's 100% certainly placebo.

Interp values below one updaterate frame (0.01515etc in this case) would cause extrapolation to always be occurring, so the engine, of course, forcibly limits it. If it were possible to go below one updaterate frame of interpolation, it would wreak total havoc on your hitreg.

High framerates are inherently good for shooters, ultra widescreen is not.

The fov cap could be what it is now or it could be higher, I don't particularly care.

Just don't try to justify outright giving an advantage to people who happen to have a particular subjectively different setup, when balancing it for other subjectively different setups is outright easy.

So how about that diagonal cap so that people with 21:9 monitors don't have a rare and inherent advantage?

edit: I can't read, ignore me

If you have over 500fps you have a place to disable multicore rendering, which is the only possible cause of fps_max giving uncalled-for input lag. (no, multicore rendering otherwise can only reduce input lag when there's no fps cap)

16:9's max FoV with a setting of 90 is currently 73ish vertically, 106ish horizontally, and 113ish diagonally.

We should cap every aspect ratio's diagonal fov at the same value (preferably at 113 so that 90% of players don't have to change anything) , so that using different aspect ratios is always a tradeoff of horizontal vs vertical, and so that superwide aspect ratios like 2:1 have diminishing returns instead of being useless or being overpowering.

How you fix stairs is give mappers something that blocks rockets but not hitscan so artmappers are willing to clip their staircases with it and no, displacements flagged to block projectiles do in fact let rockets through because rockets are actually just short hitscan in the physics engine.

Change it to an octagonal prism like warsow did.

sunshine only gives some people worse fps than it should because of the grass sprites. http://www.teamfortress.tv/20219/detail-sprite-commands
I think older versions had denser grass, which was a problem.

but i like hearing about peoples' experiences

try mat_queue_mode 0

try disabling all threading commands

try fps_max 300

try removing most of your launch options (including threads, nod3d9e2)

try all of the above at the same time

As long as they cap it at 100ms and don't put a floor, everything will be fine