Moved the post from here because I posted it in the wrong forum.
Context From Post
So I have an issue with packet choke. Every time I get packets ~1300 bytes or higher, they choke up. I tried setting the MTU size to 1464, but I could not change it on my router. I think it's something else instead, and if it is the MTU size, then well fuck. Also my cmdrate usually dips below 66, while my updaterate stays near 66, and I'm uncertain if that is normal behavior.
Keep in mind that I use mastercomfig and changing my modules.cfg a bit. I also already tried running default TF2, but I ended up also getting packet choke. I hope to soldier that this is not a hardware issue…
Moved the post from [url=https://www.teamfortress.tv/58139/packet-choke-issues]here[/url] because I posted it in the wrong forum.
[url=https://old.reddit.com/r/tf2techsupport/comments/kj86lu/re_packet_choke/?depth=4]Context From Post[/url]
So I have an issue with packet choke. Every time I get packets ~1300 bytes or higher, they choke up. I tried setting the MTU size to 1464, but I could not change it on my router. I think it's something else instead, and if it is the MTU size, then well fuck. Also my cmdrate usually dips below 66, while my updaterate stays near 66, and I'm uncertain if that is normal behavior.
Keep in mind that I use mastercomfig and changing [url=https://github.com/WhyIsEvery4thYearAlwaysBad/420weedsmoker69/blob/mastercoms/cfg/config/home.cfg]my modules.cfg[/url] a bit. I also already tried running default TF2, but I ended up also getting packet choke. I hope to soldier that this is not a hardware issue…
I am pretty sure that it's just a problem with TF2, since split packets (>1260 bytes) are kinda not well implemented.
I am pretty sure that it's just a problem with TF2, since split packets (>1260 bytes) are kinda not well implemented.
Yeah from what Setsul said in the post in Customization:
SetsulYeah, I don't think you're getting choke because the packets jump to twice the normal size, you're getting packets twice the normal size because half of them are choked back so you get twice the data in the next packet.
Yeah this seems to be an issue with the game itself, and not necessarily my configuration or hardware.
To 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?
(EDIT) P.S Will you use the 2020 leak of TF2 as research in mastercomfig?
Yeah from what Setsul said in the post in Customization:
[quote=Setsul]Yeah, I don't think you're getting choke because the packets jump to twice the normal size, you're getting packets twice the normal size because half of them are choked back so you get twice the data in the next packet.[/quote]
Yeah this seems to be an issue with the game itself, and not necessarily my configuration or hardware.
To add rotten cherries as well, it seems that the MTU size is [i]hard coded[/i] as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?
(EDIT) P.S Will you use the 2020 leak of TF2 as research in mastercomfig?
As said from Setsul, the only thing that may be causing the choke is probably because of my FPS. I usually get ~60fps in a not maxed out server, and ~100fps when no one is around and I am in a tight room. I have no idea how else to optimize TF2 though…
[url=https://www.teamfortress.tv/post/1021076/packet-choke-issues]As said from Setsul[/url], the only thing that may be causing the choke is probably because of my FPS. I usually get ~60fps in a not maxed out server, and ~100fps when no one is around and I am in a tight room. I have no idea how else to optimize TF2 though…
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.
[quote=AimIsADick]To add rotten cherries as well, it seems that the MTU size is [i]hard coded[/i] as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?[/quote]
Limitation in Steam.
[quote=AimIsADick]Will you use the 2020 leak of TF2 as research in mastercomfig?[/quote]
Already done.
mastercomsAimIsADickTo 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.
I'd like to know more about this actually.
mastercomsAimIsADickWill you use the 2020 leak of TF2 as research in mastercomfig?
Already done.
Ah ok. I was planning on replacing the list that could be junk with the list of launch options from the 2020 code leak of TF2. (NOT the documented list!)
[quote=mastercoms][quote=AimIsADick]To add rotten cherries as well, it seems that the MTU size is [i]hard coded[/i] as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?[/quote]
Limitation in Steam.[/quote]
I'd like to know more about this actually.
[quote=mastercoms][quote=AimIsADick]Will you use the 2020 leak of TF2 as research in mastercomfig?[/quote]
Already done.[/quote]
Ah ok. I was planning on replacing the list that could be junk with the list of launch options from the 2020 code leak of TF2. (NOT the documented list!)