(06-28-2014, 09:27 PM)NaturalViolence Wrote: [ -> ]Jesus christ how do you people put that kind of time in? I just passed 700 hours game time after 4 years and I play this game way too much for my own good.
The five goes high.
These are true no-lifes, considering that, for a whole year, I was almost constantly surfing, and I only have 669 hours into the game. And I even used to be a compie-in-training before I got obsessed with surfing and jumping!
Well to be fair I don't exactly know how much of that was idling for the year or two prior to Valve cracking down on idling. It's likely almost double or more what it should be plus I don't have a job atm and am in the country without transportation except when my dad can give me a ride to the store. Also accounting that for the longest while I primarily played TF2 without touching other games.
Steam server browser keeps killing my connection when loading the list of servers or refreshing.. :/
Can't figure out how to solve but this pos seems to get saturated easy therefore higher than normal ping, choke and ping spikes. Although it's still better than 3G and satellite but am still slightly disadvantaged.
Xtreme2damax Wrote:Steam server browser keeps killing my connection when loading the list of servers or refreshing.. :/
Change the caferate or get a better router:
https://support.steampowered.com/kb_article.php?ref=4487-YUOC-6922
I used to have that issue too until I upgraded my 10 year old router. Changing the caferate did mitigate the problem at the expense of slower refresh speeds until I got the new router.
And for a more detailed explanation:
Quote:The problem stems from the fact that game server communications utilize the UDP protocol. UDP being connectionless, the only way a router's NAT can keep track of which UDP sessions are no longer needed and remove them from the NAT table is to wait for a certain period of inactivity (timeout). This means in the case of the server browser that the router's NAT table fills up very fast with sessions to each server being queried. Once the NAT table is full, what happens next depends on how well the firmware for the router has been written. An ideal router would continue accept new connections/sessions, albeit a bit slower as old NAT entries are gradually flushed out. However many router's firmwares are poorly written and will crash, hang, or fail to accept any new connections, effectively making the internet connection unusable.
There are a couple of solutions to the problem, the first being to have a larger NAT table in the first place, which requires more RAM, thus higher production costs which the manufacturers are for the most part not willing to do. Second is for better written firmware that manages NAT more efficiently and responds appropriately to a flooded NAT table. Fortunately, there is 3rd-party firmware such as Tomato and DD-WRT available for some routers which fixes these problems.
With my old linksys wrt54g the NAT table would fill up and crash the router in about 3-6 seconds after hitting refresh. I would have to reset the router every time to get my connection back.
install dd-wrt on that old wrt54g, makes it a top router.
(07-06-2014, 05:40 AM)NaturalViolence Wrote: [ -> ]Xtreme2damax Wrote:Steam server browser keeps killing my connection when loading the list of servers or refreshing.. :/
Change the caferate or get a better router: https://support.steampowered.com/kb_article.php?ref=4487-YUOC-6922
I used to have that issue too until I upgraded my 10 year old router. Changing the caferate did mitigate the problem at the expense of slower refresh speeds until I got the new router.
And for a more detailed explanation:
Quote:The problem stems from the fact that game server communications utilize the UDP protocol. UDP being connectionless, the only way a router's NAT can keep track of which UDP sessions are no longer needed and remove them from the NAT table is to wait for a certain period of inactivity (timeout). This means in the case of the server browser that the router's NAT table fills up very fast with sessions to each server being queried. Once the NAT table is full, what happens next depends on how well the firmware for the router has been written. An ideal router would continue accept new connections/sessions, albeit a bit slower as old NAT entries are gradually flushed out. However many router's firmwares are poorly written and will crash, hang, or fail to accept any new connections, effectively making the internet connection unusable.
There are a couple of solutions to the problem, the first being to have a larger NAT table in the first place, which requires more RAM, thus higher production costs which the manufacturers are for the most part not willing to do. Second is for better written firmware that manages NAT more efficiently and responds appropriately to a flooded NAT table. Fortunately, there is 3rd-party firmware such as Tomato and DD-WRT available for some routers which fixes these problems.
With my old linksys wrt54g the NAT table would fill up and crash the router in about 3-6 seconds after hitting refresh. I would have to reset the router every time to get my connection back.
It's a brand new Lte device/router but it was cheap, doesn't support external antennas nor usb tethering so the wifi router in this is likely junk too. Only thing I can say is when the service is working at full capacity speed is great and pings are lower than 3G and satellite. However I think because of the poor wifi I'm getting choke/ping spikes but that or at least ping spikes may be due to playing on Valve servers where the majority seems to have pings over 100ms to 200ms+ lately.
Spaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaace
But in all honesty, they just leave the tf2 beta to die. These changes BELONG into the TF2 beta.