i'm pretty sure those are comprehensive enough

if you think you can make a better write up than mastercom without making 80% of it her work i'd like to see

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.

Yep Cock

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)

aren't you the dude that was going around to twitch chats saying you had a secret google doc that would help people's performance if they were nice to you?

https://media.giphy.com/media/fDzM81OYrNjJC/source.gif

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

also as everyone already told you
you wouldn't have to care about half this shit if you just saved some money and got an actual pc

https://youtu.be/pXAQNGUcTjs

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).

Aim Is A Dick

Have you checked this one out?

bullying aim on a tuesday

https://media.discordapp.net/attachments/779486942370594827/819017906713002025/unknown.png

this is from the first source that you linked in #6

"frametime" and frames per second are the same fucking thing lol

you cannot seriously think you know more than mastercoms about tf2

If you're referencing this, I can't find a single thing in this video that is wrong or shitty. it's geared at pubbers. it's not made with disabling literally every graphical setting in the game in mind lol

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?

There are two incorrect things in the Delfy video that I spotted: r_lod 2 instead of r_rootlod 2 and the recommendation to use -threads -high in launch options (granted, I skimmed through it).

Anyways, the mastercomfig docs are open source! So you can improve them however you'd like.

How do you think a game engine or any benchmarking tool measures FPS? It uses frametime by measuring the time taken between the start and end of the frame, then takes the reciprocal of that (divides 1/frametime).

You may be thinking of dxlevel 98.

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.

You may consider collaborate with this gentleman https://www.teamfortress.tv/56288/fps-config-based-on-research-and-not-vpk

i cannot wait for AimIsADick to start playing 6s

we may need to start a gofundme to buy him a 50 dollar discrete gpu from like 2010 to make that happen

i think you just mean that sometimes it's better to have a stable framerate rather than an unstable but high-ish one. then the frametimes are also stable, because it really is kinda the same thing (so the experience is far more enjoyable)

You know its going to be a good config when OP proposes to not use frames per second and instead suggests using something he forgot the name of...

Maybe I misunderstand what frametime is, but isn't frame time more granular than FPS...? B/c you get a time for every frame and can see very detailed oscillations that FPS hides. (like one frame takes 10ms to render and the next spikes to 150ms for some reason.) FPS gives aggregate info over the second so it loses some of that detail. The mean or total frametime over the second is the same as FPS, but you can't recover individual frametimes from the FPS... So, they're not the same metric..., right?
I need someone to explain it to me. ;-;

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.

ok, do it then, instead of making this thread.

yeah that's smart, something tells me you wouldn't really be able to talk on that either

Ah yes an ad hominem attack.

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

how tf is any of this ad hominem im saying youre unqualified to talk since your most played class is 150 hours on spy?