I've updated the changes. https://gist.github.com/mastercoms/f54f6476e0f2e4bdcf860ef902f1f93f
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 |
4.4.0 released with probably huge performance enhancements and particle reduction.
Also, could people test dsp_off 1 in a bot match and see how they like the sound quality/spatialization?
EDIT: 4.4.1 released with a few comment updates and cleanup.
EDIT 2: 4.4.2 released with a few improvements to post processing settings and characters.
EDIT 3: 4.4.3 released with a few bug fixes, maxperformance optimizations as well as some optimizations ported to dx8 (still not recommended for most users).
Rockzim aware of that, i just wanted to know the fps variance
Yes I was trying to clarify for everyone, nothing wrong with your post :)
The default setting is your cores - 1, at a max of 3, just FYI.
Calling all testers with CPUs that have more than 4 real cores: add -threads core count - 1 to launch options
Please don't downfrag people who just want help!
(also sachiko, she*)
cantirecently switched over to Linux and can't seem to get 144hz working in TF2
I've set the correct refresh rate in my display options + NVIDIA driver settings, it works perfectly on the desktop and some games (namely Tropico 5) but in TF2 it's just choppy 60hz no matter what settings I use despite my FPS counter(s) showing up as constant 300+
any ideas? using Manjaro 17.0.5 w/ XFCE
EDIT: i turned off display compositing in my Window Manager tweaks and it immediately corrected the issue
Display compositing should automatically turn off. Are you in fullscreen mode?
can't wait to open an assassin's grade professional killstreak femscout in the next case
tf_viewmodels_offset_override 0
fagoatseNice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.
Alright, sounds good. Seems like we will have to find out if stabby was using -NoQueuedPacketThread.
osvaldoDunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.
Well you should also have the launch option if it is at 0. It saves memory and CPU which is being idly wasted.
Also, no, it isn't placebo. When packets are bigger than net_maxroutable, which is maxed out at 1260, Source divides them up into smaller chunks called splitpackets. These splitpackets are delivered in a sequence and with net_queued_packet_thread 1, each splitpacket after the first splitpacket is sent on another thread out after a delay that depends on your rate setting and the splitpacket size. If you have it set to 0, then the splitpackets are sent at the end of the frame immediately.
fagoatseI'll try it out and get back to you.
On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.
Yeah you only need mat_dxlevel 95, not the launch option. I already have it in the comfig.cfg. And thanks.
https://www.drewwolf.com/tf2alt
From Valve artist Drew Wolf.
Calling testers:
add "ConVar.cl_clean_textures_on_death" "1" to section 3 of dxsupport_override.cfg.
Added somewhere around Gun Mettle, I think. When you get a freezecam/die, it removes unused textures.
fagoatseI'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?
No, net_queued_packet_thread 1 will queue and delay packets regardless of -NoQueuedPacketThread, but will do this unthreaded if you have -NoQueuedPacketThread.
You should either use net_queued_packet_thread 0 + -NoQueuedPacketThread (which I recommend if you don't encounter problems with it), or net_queued_packet_thread 1 without the launch option.