Sorry for the plug, but could you see if it happens when you use my config? http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config
I would also recommend trying -dxlevel 98.
Account Details | |
---|---|
SteamID64 | 76561198046110893 |
SteamID3 | [U:1:85845165] |
SteamID32 | STEAM_0:1:42922582 |
Country | United States |
Signed Up | August 8, 2017 |
Last Posted | September 14, 2024 at 1:13 AM |
Posts | 1545 (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 |
Sorry for the plug, but could you see if it happens when you use my config? http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config
I would also recommend trying -dxlevel 98.
Why did you put Comanglia's config in the config folder? Just test it with a clean TF2 to see if Comanglia's config is causing the issue.
4.0.0 released. Completely rewrote the config and added the mat_ CVars I was missing.
Delete those folders and then verify game cache, then launch with -autoconfig.
Does the screen freeze (can you open the escape menu) or is it just network lag?
What are your launch options? And are you using a config?
What's the value of mat_dxlevel before and after you do mat_specular 0?
There are some different things that will affect your performance on Linux.
1) Drivers. In some drivers, you won't be able to use high texture quality due to some problems with large texture stores in 32-bit processes. Also of importance is getting the latest drivers. You should be using a git version of Mesa for Intel or AMD, or the latest drivers from Nvidia.
2) CPU scheduler. It is important to use a desktop oriented scheduled like MuQSS.
3) Kernel Hz. If your kernel is configured with a low hz, you will get less FPS and longer startup times, unless you have a kernel with the high resolution timeouts patch included in the ck patchset.
4) Disk scheduler. A lot of the frame hitching in TF2 is caused by delayed disk loading for sound and models. If you get a desktop oriented disk scheduler, like BFQ, TF2 will have less problems with the disk.
5) Process prioritizing. You can use Ananicy to prioritize the TF2 process on the CPU and IO.
mba_Sorry if this is a noob question but the link on your main post https://github.com/mastercoms/tf2cfg and the link in your latest post in this thread mastercomms https://github.com/mastercoms/tf2cfg/tree/4.0.0 are giving me different configs. Which do I use?
Well 4.0.0 is in beta but should be better than the main version. Has less extra config customization options, though, which I am working to add soon (stuff like chat and hud customization).
stabby
Is that with -high? And it will be interesting to test this on Windows vs Linux, because of the different CPU schedulers they have.
knuckidk if this has been discussed but
the sound setting causes this weird issue where sounds don't update where they originate from properly within surround sound.
so for instance if a heavy starts shooting to my left and I rotate my mouse it still sounds like it is coming from the left no matter what
Try snd_spatialize_roundrobin 1 to reduce the effect or snd_spatialize_roundrobin 0 to completely remove the effect. This questionable default will be fixed in 4.0.0.
Schweppesthe ultimate reminder that valve's horizontal "work on whatever you want and you don't have to commit" company structure is fucking shit and always has been
https://s.aolcdn.com/hss/storage/midas/19b72899298e2257b6b0be1add946eda/205551007/youtu.be-DA5mY8XqrHU.jpg
but we'll get this guys so it's alright haHAA
Except Valve has changed its policy in ~2010 to 2013, when they had to accommodate for Dota 2 development with IceFrog and also had the great cleansing in 2013. The work on whatever you want policy produced Half Life 2, Half Life 2: Episode 1, Half Life 2: Episode 2, Portal, Portal 2, and Team Fortress 2.
This is a new Valve nowadays.
Project Borealis
maniacalOnly maxperformance
Ok, I updated the config. Is the issue solved now?
maniacal
new maxperformance cfg crashes tf2 on launch. this may just be my shitty computer, but i'll have to look into it
Only maxperformance, or does it happen with the default config as well?