| Account Details | |
|---|---|
| SteamID64 | 76561198374045865 |
| SteamID3 | [U:1:413780137] |
| SteamID32 | STEAM_0:1:206890068 |
| Country | Pirate |
| Signed Up | March 20, 2020 |
| Last Posted | July 30, 2025 at 5:34 PM |
| Posts | 311 (0.2 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | 5.2 |
| Windows Sensitivity | no |
| Raw Input | yes |
DPI |
no |
Resolution |
1024 768 |
Refresh Rate |
120 |
| Hardware Peripherals | |
|---|---|
| Mouse | no |
| Keyboard | yes |
| Mousepad | no |
| Headphones | no |
| Monitor | yes |
AimIsADickBumFreezemiles per hour is a very misleading metric. i measure my speed in hours per mile. its soooooo different and so much better!!!Strawman.
What do you mean strawman? Miles per hour has the exact same kind of relationship to hours per mile as FPS has to frametime. It's identical.
Go look at what an fps indicator does, it's literally 1 over the last frametime. Here's cl_showfps for instance https://i.imgur.com/QNjUyPI.png
changed from google to cloudflare dns, fps tripled, ping halved, tysm!!
AimIsADickThey 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.
Scroll up and read mastercoms' post, looks like you missed it
AimIsADickI 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.
The cool thing about mastercomfig is that you can go ahead and add it to the docs right now if you want. I'm sure it would be merged if you write a good description of it.
You may consider collaborate with this gentleman https://www.teamfortress.tv/56288/fps-config-based-on-research-and-not-vpk
AimIsADickThere is a difference between the two though; frametime states how long it takes to render a single frame. This is useful because it can tell the client if they have a bottleneck somewhere, need some stability or a frame cap, or just need to reduce the details, or whatever the solution is. Meanwhile frames per second merely state how many frames can be generated in a second, which can only tell the client if they are getting enough frames, and that means the client can miss out on tons of information crucial to proper optimization and it's extremely misleading if you get more than enough frames per second consistently.
P.S I did make one change to my OS: I changed my DNS provider to OpenDNS. Is this a good idea? Are there better options?
I mean, if you measure fps at the same resolution (every frame) that you're talking about, you will see the exact same variations. It really is the same metric.
Why are you mentioning DNS here?
if you're not already running some super low resolution, have you tried lowering your res to something like 1024x768 or even 800x600? super weak gpus, especially intel graphics, can actually see quite a performance benefit from lowering res in tf2, and higher overall framerate will make framerate inconsistencies less noticeable.
also, check your cpu/gpu temp and clockspeeds to make sure they are not thermal throttling, as that would absolutely lead to lower framerate and greater framerate inconsistency.
AimIsADick
fps and average frametime refer to quite literally the exact same metric. diving (1) second by your frames per second will directly give you the average frametime over that second (eg. 1 second / 144 fps = 6.9 ms frametime).
bearodactylMoisthttps://streamable.com/51qdnewe need the heavy pov for this
delete_my_accounthttps://www.youtube.com/channel/UCnak_45PiKmwC9GUzkeoRPw
richest 2 men in all of tf2 but has no skill
he has the skill of making more money than u ....
https://i.imgur.com/9VnxKQc.mp4 plz fix asap very serious
Try the pre-JI demos branch
https://i.imgur.com/uNT4ysG.png