| Account Details | |
|---|---|
| SteamID64 | 76561198046110893 |
| SteamID3 | [U:1:85845165] |
| SteamID32 | STEAM_0:1:42922582 |
| Country | United States |
| Signed Up | August 8, 2017 |
| Last Posted | May 7, 2024 at 8:36 PM |
| Posts | 1534 (0.6 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
AimIsADickYeah 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, clearing up bloatware, etc.).
There's an OS optimizations section. https://docs.mastercomfig.com/en/latest/os/windows/
Using dxlevel 81 is not a misconception. It has a valid use case. Same with the force ID settings. I haven't looked too much into those but people do strangely get a benefit out of them sometimes.
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.
AimIsADickThey'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.
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).
AimIsADickdxlevel 95 is only available on xbox 360. On PC the dxlevel will be maxed to 90.
You may be thinking of dxlevel 98.
buudI really dont wanna verify integrity of game files and delete and paste my cfg and tf back every time i wanna change config
You don't have to do this anymore (and it doesn't have to do with VPKs anyway):
docsThese steps are no longer required to install mastercomfig, but is kept here to document how to completely reset TF2.
https://docs.mastercomfig.com/en/latest/setup/clean_up/
Also, as listed on the download page, you can access the mastercomfig zip package from here.
Having an FPS cap may be throttling your performance more than necessary. Try using an external FPS cap like Rivatuner.
AimIsADickOk I understand now. Guess I was just seeing a false correlation between the cvar and frames. Thanks again.
It does use some DX8 shaders so it might negatively affect stuff on your machine.
AimIsADickAlso just a heads up, but I personally think you should display frametimes in the graph in the performance section on your site. I heard that FPS is generally an unreliable metric, so I think it's a good idea to include frametime as a consistent metric as well.
frametime = 1/FPS
1/frametime = FPS
FPS is bad to measure as a relative thing, like "I just gained 30 frames!", instead of "I had 240FPS before and now I have 270FPS." That latter one is fine.
if you mean the frame pacing, that's harder to compare and measure between configs.
No, it controls shader quality. Reducing fillrate in this instance means reducing the required pixel fill cost.
This is irrelevant but given that I was mentioned and kind of misunderstood, I thought I'd respond. I didn't I said you would get higher FPS all the time with DX9 vs DX8. The more efficient renderer is rendering more, so it's just doing more, faster, but in more time than something that's doing less, slower. So it's understandable that it's getting less average FPS.
Anyways, DX9 can help a lot with drops, latency, resource usage, frame timing and performance over longer periods of time even if it isn't getting you higher average FPS. Finally, keep in mind that how you test dxlevel can affect your benchmarks. You should be setting dx9 and then launching without -dxlevel 90, or else you will experience some graphics options getting reset, causing lower FPS.
AimIsADickDo the launch options need to be in the latest game version? If so then I can adjust my launch option list to accommodate that. Also what do you refer to as a bad launch option?
The things you were saying: "junk strings that aren't launch options"
AimIsADickHow do I compile mastercomfig from the source that is on github? I'd like to try and help out development aside from updating the list of launch options to remove the junk strings that aren't launch options. This is the list that I'm going to refer to if I do.
P.S Can I use the 2018 code leak of TF2 as a source of information like the Source SDK?
Thanks for your interest in contributing to mastercomfig! There's a contributing document that contains packaging instructions here: https://github.com/mastercomfig/mastercomfig/blob/develop/.github/CONTRIBUTING.md#packaging
Beware that any sanitization of the launch options must be automated to be part of the generation process. So a filter of known bad launch options could work, as well as a heuristic for random garbage.
You can use your own personal knowledge of TF2 to develop mastercomfig. Where that knowledge comes from is not of my concern.
Yeah how Windows and Source interact for threading adds a lot of overhead and latency to the frame. That's sort of what I was working on that gave the biggest gains in TC2.
what's your hud
AimIsADickTo add rotten cherries as well, it seems that the MTU size is hard coded as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?
Limitation in Steam.
AimIsADickWill you use the 2020 leak of TF2 as research in mastercomfig?
Already done.
I am pretty sure that it's just a problem with TF2, since split packets (>1260 bytes) are kinda not well implemented.
are you using a surface properties mod, like no footsteps?