Waiting on Zen 2 benchmark1 run with mastercomfig v6 medium-low (or v7 low) then. Because if it can do at least 280fps under that condition, I will surely pick up a 3700X soon.

Didn't realise people were using different benchmarks now, I just assumed everyone was posting benchmark1.dem results so there would be a common reference point.

And above 1.4v is excessive vcore for Coffee Lake because it's well beyond the optimal range of efficiency. Beyond 1.4v you start getting very large increase in heat generation for little improvement in clocks. Not unsafe (1.45+), but excessive.

Higher RAM speed is an Intel advantage in this case as even Zen 2's memory controller won't achieve as high of a RAM clock.

And with voltages I'm going off SiliconLottery's stats for how common certain clocks are.

RAM matters a lot too for TF2. I have B-die at 4133 which allows >290 FPS in benchmark1.dem. You should OC to at least 4800 on your 8350K, which can be achieved with a fair voltage. 4900 and above start to require excessive vcore.

Not sure what you mean. My 8350K is pounding all these Zen 2 chips in TF2 performance. Unless you mean you regret not getting a much better overall chip that still has decent TF2 performance.

2639 frames 8.776 seconds 300.72 fps ( 3.33 ms/f) 21.626 fps variability
8350K@5000 w/4133C16-17-17-32-2N (all subtimings auto).

Interested to see 3600X and 3700X results with 3733 or higher RAM.

Does anyone know if running timedemo on a 6s POV simulates the real load on your PC during the match or is it less demanding than real-time? Because I never drop below 260~ FPS in 6s POVs but I swear I drop down to like 220-240~ during the actual match. Probably need to log my FPS next time I play.

Try -dxlevel 100. Best performance out of all DX9 levels for me, although still inferior to -dxlevel 81.

Anyone know why there's such variance in benchmark1 performance? Sometimes I'll get 283fps (multiple runs to confirm) then reboot my PC, run again, and immediately get 297fps. Never any difference in background programs – only have Steam, discord and RTSS running anyway.

I've never had an issue with 15.2ms interp (no players stuttering or hitreg issues or anything) and the difference in projectile delay is noticeable.

Also, how to get 15.2ms interp on V6? I set snapshots to "lan" in modules.cfg, but I still have 21.0ms interp.

I switched back from 7a to 6.11.4 (medium-low.vpk) and fences (like the one near snakewater spawn, or ammomod) look aids now even with MSAA enabled. How to fix it? On 7a, they only looked shit with MSAA disabled.

If ESEA dropped TF2 because it was losing them money, and ESL owns ESEA, for what purpose would ESL want to branch into TF2?

Finally managed to get over 300fps in benchmark1.dem.

2639 frames 8.499 seconds 310.52 fps ( 3.22 ms/f) 24.430 fps variability

-dxlevel 81, mastercomfig v7 all low/off except shaders medium.

CPU: i3-8350K@5,000MHz core, 4,400MHz cache, 1.41V
RAM: 4,133MHz, 16-17-17-33, 1.5V

What got me over the line was messing with one of the secondary timings on the RAM, tREFI. I maxed it out to 65535 and got a massive performance boost in TF2, about +20 minimum FPS.

I can't find anything in the hudlayout.res of m0rehud relating to seeker crosshair, or any crosshairs at all for that matter.

How can I get the "seekerShadow" crosshair from m0rehud in ahud? ahud only comes with KnucklesCrosses, is there a way to copy over the seeker crosshairs?

I like that with this new version I can use MSAA with lower quality settings. Before, I could not get MSAA to work with medium-low.vpk.

What settings should I set to get equivalent config to the old medium-high?

Why keep texture filtering reduced until higher presets? Isn't texture filtering a trivial performance cost?