Constant, serious lag

[Major Payne]

Well I seemed to have fixed my choke issue. I'm still getting pretty high numbers in the "In" area. But now I am experiencing being timed out after 5 minutes of gameplay, every single time. Anyone have ideas on that?

It's also not just happening in TF2. Just happened in CS:S a few minutes ago. And I'm also getting big numbers for "In" in CS:S.

And disabling my firewall didn't do anything, if that's a common remedy

 

[General Sanders]

I don't think anyone asked: Are you patched directly in to the school's network, or are you running through a router that you own?

 

[metro]

I missed this post, and no one has explained it yet, so here it goes.

Oh yeah I knew the FPS was good. I was pretty happy with that. But do you guys know what exactly determines the number for the "In" area?

The "In" and "Out" lines have 3 major components.

The first number, in your case the big one, tells you the size of packets (in bytes) that are being sent (out) or received (in).

The second one tells you the amount (in KiloBytes/second) of data being transfered.

The third one tells you how many times it updates per second.​

So, not only are the packets you're receiving larger than average, you are also receiving them less often.

For reference, I get around 60, 200 byte packages, per second. The first number on the "In" line is 200, and the last is 60/s. The number of times/second is controlled by the cl_updaterate command which you should have set up when fixing your choke. It is also limited by the servers tickrate.

Could you post some screenies of you playing now before you time out?

 

[Major Payne]

I don't think anyone asked: Are you patched directly in to the school's network, or are you running through a router that you own?

I definitely am not using a router of any sort, so I must be just patched into the network. The first day I moved into the dorms, it immediately connected me to the wireless internet and I set it as Public.

I missed this post, and no one has explained it yet, so here it goes.



The "In" and "Out" lines have 3 major components.

The first number, in your case the big one, tells you the size of packets (in bytes) that are being sent (out) or received (in).

The second one tells you the amount (in KiloBytes/second) of data being transfered.

The third one tells you how many times it updates per second.​

So, not only are the packets you're receiving larger than average, you are also receiving them less often.

For reference, I get around 60, 200 byte packages, per second. The first number on the "In" line is 200, and the last is 60/s. The number of times/second is controlled by the cl_updaterate command which you should have set up when fixing your choke. It is also limited by the servers tickrate.

Could you post some screenies of you playing now before you time out?

Also, I played a game for about 1 1/2 hours a bit ago. I didn't time out that time, but I'm playing another and I'll see if I time out.

EDIT: Didn't time out in the second game either. For now it seems like it solved itself. But I'm not totally convinced

 

[metro]

Those numbers look a lot more reasonable to me. Hopefully you never time out again!

 

[Major Payne]

Haha yes me too

And thank you to all who helped me!