Page 1 of 4
netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 12:27
by hirecuery
hello everyone. for a long time I did not dare to describe this problem, but still I am not able to solve it on my own.
I play valorant, I moved away from my parents and felt problems with registering bullets.
I started changing routers, providers, and my game always felt different.
nevertheless, I found a cmd command that helped me. this is netsh int tcp set global autotuninglevel=disabled. but when I use it, I feel like my opponents see me much earlier than I see them, and I often catch a enemy ferrari peek. when I set this value to normal, the enemy's spikes are not that fast, but I have a problem registering bullets.
also, the clip from a vandal with disabled goes crookedly when it is smoother with normal.
I've tried a lot, but it's the only thing that gives me any usefulness. help me.
sry for my english

Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:14
by Slender
interesting.
im use disabled value a lot of time, it gives me more stable gameplay, but yeah im notice that picking. Lets go with wireshark and make test with normal / disabled and send me results.
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:16
by Slender
also, that command affect on bufferbloat
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:20
by JimCarry
try mine
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:27
by Slender
yeah try ctcp
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:29
by hirecuery
Slender wrote: ↑27 Jan 2025, 13:14
interesting.
im use disabled value a lot of time, it gives me more stable gameplay, but yeah im notice that picking. Lets go with wireshark and make test with normal / disabled and send me results.
Okay, I'll do it when I get home.
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 13:43
by Slender
also try that:
netsh int tcp set global nonsackrttresiliency=disabled
netsh int tcp set global ecncapability=disabled
netsh int tcp set global timestamps=disabled
netsh int tcp set supplemental custom tcpackfrequency=1
+ you can try disable rss / taskoffload (cpu will interrupt network)
Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 14:54
by Misha1337
Slender wrote: ↑27 Jan 2025, 13:14
interesting.
im use disabled value a lot of time, it gives me more stable gameplay, but yeah im notice that picking. Lets go with wireshark and make test with normal / disabled and send me results.
You can try those other values

Re: netsh int tcp set global autotuninglevel=disable
Posted: 27 Jan 2025, 19:47
by hirecuery
Slender wrote: ↑27 Jan 2025, 13:27
yeah try ctcp
idk why its default, i installed ctcp above. driver problem?

- Снимок экрана (1).png (383.18 KiB) Viewed 13982 times
Re: netsh int tcp set global autotuninglevel=disable
Posted: 28 Jan 2025, 01:51
by ahead
This relates to the TCP protocol.
Valorant, CS2, Call of Duty, Battlefield, and other FPS games use the UDP protocol to exchange information between servers and clients. The use of UDP for communication in FPS games can easily be found on this forum, other forums, through Google, or even by asking ChatGPT. Based on this, I have a question: *** *** *******? This is a rhetorical question, so please refrain from answering.
[Moderation Bot: Removed slur. We aren't X or Facebook.]