//benchmark1
19.016 seconds 138.78 fps ( 7.21 ms/f) 9.395 fps variability
18.922 seconds 139.46 fps ( 7.17 ms/f) 9.424 fps variability
19.224 seconds 137.27 fps ( 7.28 ms/f) 9.394 fps variability
//AVG:
19.054 seconds 138.50 fps ( 7.22 ms/f) 9.404 fps variability

//benchmark2
41.737 seconds 116.04 fps ( 8.62 ms/f) 16.841 fps variability
40.163 seconds 120.58 fps ( 8.29 ms/f) 16.189 fps variability
40.448 seconds 119.73 fps ( 8.35 ms/f) 16.104 fps variability
//AVG:
40.783 seconds 118.78 fps ( 8.42 ms/f) 16.378 fps variability

CPU and overclock: i5 4460 @ 3.20GHz
Graphics Card: Radeon 270X
Driver version: 15.30.1025-151117a-296567C
dxlevel (default is 90): 98
Resolution: 1920x1080
Full-screen or windowed: full
FPS configs enabled: lqgfx
Shadows enabled/disabled: disabled

gonna go check to see if there's notable differences in the -dxlevel 9X's on this

e:

for whatever reason, chris' dx9frames config is actually worse for your performance. I still have no clue as to why, and comanglia's/lqgfx still gives better performance as a whole

that would be mat_picmip -1, which was required because of weapon skins breaking low-quality textures and actually making performance worse on anything but highest, but that was fixed and just not updated in the config

switch it to mat_picmip 2

ah, that's good. I was just thinking abt that because it might make people pug more on this map, since it's a map guaranteed to stay official while still using competitive input

well, at least it's one way to force it from valve's end, which helps

quick question, if bloodhound still reads this thread: fubar mentioned that he can make changes to vanguard, and it will be updated for TF2 (presumably, he didn't explicitly say that out loud it'd be weird for him to get officially in while he still wants to update it). is that similarly happening to this map?

it looks like a map that tried really hard to tone down the campy laziness of a CTF map, but no matter how you look at it it's still a CTF map and that means it still promotes players to sit in the same spot and do little to nothing for thirty to sixty minutes at a time

the game mode's just kind of flawed at the core, everything else has some form of push/pull that requires movement, CTF has nothing

since apparently TFTV only likes complaining about the maps on other threads, should show these over here:

http://www.teamfortress.tv/30635/the-tough-break-maps-discussion

I recall people mentioning that -dxlevel 98 is a bit more graphics-balancing a while back. I got about the same framerate as 91, but I have a pretty mid-range graphics card, so it might work out better for others.

it would help to find out what commands specifically offload to the CPU, if this is the case as people are assuming

felt like checking dxlevel differences post-update for all the DX9's (since that's going to be mandatory once matchmaking is out, r.i.p.)

same specs as before in this thread (tho I'm now on a clean windows 10, doubt that did too much since this is about the same framerate)

//running a very gently modified version of:
//https://github.com/triant9/my_custom_stuff/blob/master/cfg/lqgfx.cfg
//** denote the timedemos with -dxlevel 9X in launch, * is first run after
//removing -dxlevel, all other benchmarks were after one run

//dxlevel 90
19.415 seconds 135.93 fps ( 7.36 ms/f) 10.504 fps variability **
19.333 seconds 136.51 fps ( 7.33 ms/f) 10.369 fps variability *
18.470 seconds 142.88 fps ( 7.00 ms/f) 10.052 fps variability
19.332 seconds 136.51 fps ( 7.33 ms/f) 9.867 fps variability
18.466 seconds 142.91 fps ( 7.00 ms/f) 10.148 fps variability

//dxlevel 91
19.432 seconds 135.81 fps ( 7.36 ms/f) 10.041 fps variability **
19.916 seconds 132.50 fps ( 7.55 ms/f) 10.165 fps variability *
18.096 seconds 145.83 fps ( 6.86 ms/f) 10.276 fps variability
18.114 seconds 145.69 fps ( 6.86 ms/f) 9.770 fps variability
18.574 seconds 142.08 fps ( 7.04 ms/f) 11.125 fps variability

//dxlevel 95
19.320 seconds 136.59 fps ( 7.32 ms/f) 10.266 fps variability **
19.249 seconds 137.10 fps ( 7.29 ms/f) 10.457 fps variability *
18.223 seconds 144.82 fps ( 6.91 ms/f) 10.019 fps variability
18.288 seconds 144.31 fps ( 6.93 ms/f) 9.519 fps variability
18.263 seconds 144.50 fps ( 6.92 ms/f) 9.867 fps variability

//dxlevel 98
19.297 seconds 136.76 fps ( 7.31 ms/f) 10.139 fps variability **
19.660 seconds 134.23 fps ( 7.45 ms/f) 10.269 fps variability *
18.655 seconds 141.46 fps ( 7.07 ms/f) 10.163 fps variability
18.670 seconds 141.35 fps ( 7.07 ms/f) 9.906 fps variability
18.721 seconds 140.96 fps ( 7.09 ms/f) 9.970 fps variability

first runs always seem to be a bit slower on all counts?

also, since we're pointing out small stuff:

Unknown command: mat_shadowstate

I have no clue what this command was, all googling does is send you to other FPS configs that have it

mat_antialias 1 is literally just x1 and thus has no antialiasing, is it not?

I have time to waste, going through the config commands and seeing what happens

I thought I found out what causes the black textures, but I couldn't get it to work again, so it's likely a result of more than one command at the same time?

one of the most unbalanced weapons of all competitive FPS games? well, I don't need to learn positioning to deal with it, can't be as bad surely

it's entirely possible for valve to make massive, sweeping changes for pyro. remember, both of the major updates this year had those type of changes, and regardless of the outcome being positive or negative (uber pickup whyyyy) they've certainly been big.

the way I see it, there's really no greater gap of design between pubs (or, to a smaller extent, HL) and 6s than with the pyro. the pub pyro is your team's helpful little support buddy, maybe not the best in all situations but he's good glue and can basically work together with anyone else to a good effect, so people like him. in 6s, though, he's just a shitty little defensive class that you use when you decide that you need to use his one good stat, his airblast, and then you go right back to scout the second that's dealt with.

the pyro is really good for teaching new players a lot of important stuff (truktruk mentioned in the tough break thread that the phlog is good on its own just to force novice opponents to learn strict positioning, which I'm cool with), but... you can say the same thing about the soldier, and the soldier is still incredible at top 6s play. you can still raise the skill ceiling without touching the skill floor, and if anything that's precisely why a pyro redesign could be a great thing. it's hard to go wrong with a class that anyone can learn, but you can still skillfully use at top levels of play

e: btw, I found this gfy on /r/truetf2: http://www.gfycat.com/WideeyedDeficientCaecilian
not much actually changed, at worst you just needs to aim a bit better

personal benchmarks, using this dem file (which I still need to replace, but I'd like to have a potential worst-case scenario, and it's hard to find a pub of ppl using only wep skins), -dxlevel 91 put in and then removed after one launch before testing

//-default in launch, host_writeconfig in console, added commands to end
//of cfg to disable gibs/ragdolls/facialstuff/shadows
2639 frames 21.994 seconds 119.99 fps ( 8.33 ms/f) 10.030 fps variability
2639 frames 21.890 seconds 120.56 fps ( 8.29 ms/f) 10.015 fps variability
2639 frames 21.632 seconds 122.00 fps ( 8.20 ms/f) 9.447 fps variability

//chris' dx9frames config
2639 frames 24.860 seconds 106.16 fps ( 9.42 ms/f) 8.768 fps variability
2639 frames 23.128 seconds 114.10 fps ( 8.76 ms/f) 8.654 fps variability
2639 frames 23.304 seconds 113.24 fps ( 8.83 ms/f) 8.340 fps variability

//comanglia's high quality config. note that it broke on my computer with
//the tough break update (https://streamable.com/z7l1) but I can still
//technically get benchmarks with it, so w/e
2639 frames 18.391 seconds 143.49 fps ( 6.97 ms/f) 12.265 fps variability
2639 frames 17.894 seconds 147.48 fps ( 6.78 ms/f) 10.973 fps variability
2639 frames 17.967 seconds 146.88 fps ( 6.81 ms/f) 11.462 fps variability

so until it's figured out what breaks comanglia's config, default is actually the way to go, I guess

help

(it was even worse w/ transparent viewmodels on, the entire screen would look spotty and fiery until I set r_drawviewmodel to 0) (r9 270x, i5 4460)