Yeah I know about that. Point is that not all of the performance tips exist on your site documentation(, like reducing resolution and aspect ratio and changing the DNS server), and they're often scattered around the internet so they're not always easy to find. That's why I wanted to make a complete comprehensive performance guide.

Not everyone actually has the patience, programming and Source knowledge, or humility to be able to make a good performance config. The way I see it most players just shove in cvars with barely any research put into them without even bothering to save the changes to the video config. That's why I just recommend hunting down a good config made with thorough yourself.

Because me having only 150 hours on spy is completely irrelevant from whether I'm qualified to talk about game performance?

Ah yes an ad hominem attack.

(I think posting about the guide here was a mistake after all.)

I made a typo there. I meant which term I should use. I was unsure whether to use frametime or frame pacing.

They are the same metric but yes frametime is more granular than frames per second. This is what I was trying to explain to these people.

I am planning on contributing this information to the docs. I just have no idea how to explain the "misconception" (or rather misusage).

Your situation is really the only time to use the force driver ID launch options.

Yeah I get that but people seem to misuse dxlevel 81 a lot, so while I guess it technically doesn't count as a misconception, I still think what you said about dxlevel 81 earlier should at least be displayed somewhere in the docs, otherwise it likely will keep getting misused.

Yeah ik. I was just thinking of tips that weren't necessarily related to your config (like if neccessary increasing the page file size on windows, cleaning up bloatware, etc.).

I must have been thinking of something else when I thought that they weren't the same metric, but yeah they are the same metric. (Sorry about that!)

Yeah I was thinking of dxlevel 98 for some reason.

So I noticed that you were talking about how dxlevel 81 is often misused and that you wished you mentioned it? Why not go ahead and talk about it in the misconceptions page?

Same goes for the -force_device_id and -force_vendor_id launch options, though they seem to be rarely used nowadays. I personally think it's a good idea to do so anyways in case they ever got common usage again.

I'm starting to think this project was a bad idea.

They're the same metric type, not actually the same metric. The difference between the two is in how the information is represented. Frametime represents the time it takes to render the frame, while frames per second represents the amount of frames generated in a second. What I'm saying is that frametimes are generally better than frames per second as a benchmark metric, because it gives more information.

Well yeah I don't. I know fuck all about Source and I'd rather not try to bother with it.

1. This video presupposes that more FPS = better performance even though that isn't always the case.
   
2. dxlevel 95 is only available on xbox 360. On PC the dxlevel will be maxed to 90.
   
3. mat_queue_mode should be left to -1. Let the game figure out when to use queue mode instead of forcing it on or off.
   
4. Any evidence for these claims made in this video?

No I'm talking about that (those frametime spikes seem to be exaggerated btw. Just playing in some TF2 lobbies with cl_showfps 2 shows me that's it's generally pretty low like around 16.7ms, so it's likely the software I used for testing). I just got tired of those shitty performance guides online (like that one made by Delfy and that one other youtuber that said mastercomfig made his game run worse).

Uh no. I don't remember ever doing that.

No I'm serious. Frames per second doesn't give enough info for it to be useful, and it's often misleading. (Source 1 and Source 2)

They get the basics down, but the docs are still missing some information. For instance it is not recommended to use dxlevel 81 on modern computers because it uses an older rendering pipeline that is inefficient. Also most people don't realize that framecount per time (like frames per second) is a terrible metric to use for getting performance. They should be using frametime (or frame pacing? Which* term is it?) instead. Not all of this information is readily available and it tends to be hidden away in an obscure post or comment or something like that.

So one day I got irritated at the amount of horrible performance (game performance not the player performance) guides out there. I thought "I can make a better performance guide than most of these guys" so I started work on a comprehensive performance guide. It's not remotely good enough for feedback yet, but I do want to know: What information should I add to my guide pertaining to performance? What are the misconceptions when it comes to TF2 performance. (I'm not talking about the ones on mastercomfig docs I already have those.)