-noipx does not exist.
-w-h hurt performance slightly, it's better to use the in game options to set your resolution
Account Details | |
---|---|
SteamID64 | 76561198046110893 |
SteamID3 | [U:1:85845165] |
SteamID32 | STEAM_0:1:42922582 |
Country | United States |
Signed Up | August 8, 2017 |
Last Posted | May 29, 2025 at 11:21 PM |
Posts | 1557 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
-noipx does not exist.
-w-h hurt performance slightly, it's better to use the in game options to set your resolution
http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config
However, I doubt it has to do with graphics settings. You wouldn't drop that much because of anything in-game. More likely a hardware or OS issue.
HazzordHow do you get the vpk config working. I installed it in my custom folder with the rest of my mods but it doesn't work and I removed my previous autoexec in my cfg as well. I'm also using the max performance config.
So you dropped mastercomfig-maxperformance.vpk into your custom folder?
maniacalmastercomsWhat do you have r_shader_srgb set to?
set to 0
Try -1 or 1.
nuthousemastercomswhat dxlevel are you using?
81, i used chris' dx90 config for a bit but that didn't do anything either.
what did you put in your launch options for dxlevel?
Although I'm not going to criticize people for making new configs, I do think it is more productive to gather work into one place so that we can work together to get the most optimal values.
The customization options argument makes sense for something like a HUD, where a lot more variation can go into it. However, with a config, we're just tweaking the same settings, trying to find the most optimal values for each use case. If we were all to spend infinite time researching values, we would all end up separately reaching the same values.
solly6Can you help me? TF2 seems to use less GPU than CPU. My CPU is somewhere 90% usage while my dedicated GPU is only at 20% and my integrated one at 1%. Is there any cvars to make TF2 use GPU more? This causes me frame drops.
Specs:
CPU: i3-4170 3.7 GHz
GPU: AMD Radeon (TM) R5 M330
Intel HD Graphics 4400
Resolution(TF2): 1280x720
Preset
Also in the maxperformance preset, isn't r_worldlightmin 1.1 too much?
The default config already focuses on balancing load more on the GPU more than the CPU. The igpu preset reverses this. There's not much else you can really do in terms of cvars, it's just how the game was made. However, there are a few launch options you might be able to tweak. So, what are the ones you currently use?
The framedrops are another issue though.
I agree about maxperf, I'll add that to stripped instead.
JackStanleyThere is a mod that adds dxlevel 10 and higher support. Is there any difference? How does it work?
It doesn't work, doesn't add anything. It just sets some commonly used cvars.
Xorickhow much do you pay for that?
Google Fiber internet is $70/month.
Vote on December 23!
Rotten_Mind// -r_emulate_gl : emulates OpenGL, FPS boost on certain cards/drivers for Windows, probably NVidia cardsdoes this actually work, and if does, how do I know that?
The title of the window will be Team Fortress 2 - OpenGL.
WolfMachinaI just used 132 because it's double what my normal settings are, that's why I said imo :shrug:
Oh ok. It's best to set it to 133 since that's the server tickrate.
FreudCan't think of a good way of phrasing this, but I don't think you should be giving out advice based on justification this weak.
Since this is an Essentials.TF server, and someone with the Essentials.TF label said to use 132 update/cmdrate, I figured there was a good reason the server owners are saying to use that. I am also curious why they said to use 132 instead of 133.
FreudI'm not sure what your logic is here. If compression reduces the average packet size to X% of what it was originally, only X% of the original bandwidth will be used. This saving will apply regardless of the rate packets are being sent at.
If packets are being sent at a faster upload speed in bytes per second, the benefits of compression in terms of speed diminish. Also, the load from compression increases the more packets you're sending.
ArieThe point is reduced transmission times and fitting all packets within sv_maxrate, it's a trade-off.
The rate settings are increased anyway, so fitting packets into the rate isn't really an issue.
ArieThe time you lose (<0.02ms) to compress a packet is gained by having to spend less time transmitting it (because it's now smaller).
With a higher rate setting, bytes are being sent faster and thus the transmission time you save from compression is less.
ArieI'd stick with the defaults (both client and server) over lists of TF2 client and server cvars with no data/benchmarks.
The defaults aren't designed for this higher cmd/update rate. It is more optimal to change them. Though, I agree that some of the more controversial settings might be best to discuss later since this thread is mainly about tickrate rather than net settings.
ArieWe're talking kilobytes per second here, this will not cause >1% CPU load on any CPU made since TF2 was released. Also, only large packets are compressed (net_compresspackets_minsize).
But there's no point for that extra load/delay on packets being compressed. The server and client both have to do extra processing for compression, and for little benefit. With such high rates being used anyway for this server, I don't think compression even has any sort of case to be used.