Awful issues with TF2

Robert said:
http://forums.overclockers.co.uk/showthread.php?t=17861788&highlight=startername_Robert
Click to expand...

Thanks, what rates did you try? try the ones I suggested in my post above, 25000/66/66 if your still getting choke or loss try reducing the cmdrate and the updaterate if you've already tried them ignore me just a few of the suggestions in your original thread seem a bit off.

Have you tried also validating and defragmenting your local game files via steam (in my games right click tf2 and select properties).

Do you use a custom config either a downloaded one or one you created yourself? if so can you post it?

Disable every non essential program running.

Thats about it for suggestions from me really, if you get no joy at all I'll post this up on another forum I use for you and see if I can get any further suggestions.
 
Last edited:
I've tired:

Defule 10k/15k/25k
66/66 10k/15k/25k
100/100 10k/15k/25k

Default config, deleted it same again

:(
 
I've posted this elsewhere for you see if theres anything they can suggest, also I notice in your first thread you mentioned mpuk jolt and multiplay servers I cant comment on the first two but I decided to check out a multiplay server and have to say it was awful I was getting lots of choke and patches of lag there.

85.234.148.35:27025

Try the server above and see how your problems are there I'm a regular there and the server is pretty top notch.

I'll post back if I can find/think of anything else but I'm pretty much out of ideas :/
 
Thanks for your help mate :)

I formatted last night and I went on a few servers today. It seemed fine. I then went on another and found that I had to alter my rates, then I want back and had to change them again.

Surely the server should do this?

Edit: Your server seems to be full. I've just jumped out of a Multiplay server and it was awful. I was getting loss & choke, no matter what rates :(

Right I've just experienced some loss/choke and I alt-tabbed and pinged my router:

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=221ms TTL=255
Reply from 192.168.0.1: bytes=32 time=131ms TTL=255
Reply from 192.168.0.1: bytes=32 time=72ms TTL=255

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 221ms, Average = 106ms

I'm pretty sure it doesn't do this with WOW/COD4 :(
 
Last edited:
Right I have no idea.

I loaded up steam - lots of loss/choke. Alt tabbed and pinged me router - pings where 250+.

I then closed the server menu and they went down.

Did the same, but I pinged the router constantly. I then got time outs/250+pings

My router's resources where still normal...:confused:

Edit: Just thought I'd try it again:

Exited TF2 (whilst constantly pinging the router and saving to a text file)
Refreshed server list
Joined game
choke/loss - alt tabbed, packet loss to router, high pings as well
Close server list - go in and I'm still getting packet loss

Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=15ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=29ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=54ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=83ms TTL=255
Reply from 192.168.0.1: bytes=32 time=39ms TTL=255
Reply from 192.168.0.1: bytes=32 time=119ms TTL=255
Reply from 192.168.0.1: bytes=32 time=43ms TTL=255
Reply from 192.168.0.1: bytes=32 time=90ms TTL=255
Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
Reply from 192.168.0.1: bytes=32 time=80ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time=150ms TTL=255
Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
Reply from 192.168.0.1: bytes=32 time=168ms TTL=255
Reply from 192.168.0.1: bytes=32 time=11ms TTL=255
Reply from 192.168.0.1: bytes=32 time=196ms TTL=255
Reply from 192.168.0.1: bytes=32 time=32ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=201ms TTL=255
Reply from 192.168.0.1: bytes=32 time=98ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=68ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=11ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=25ms TTL=255
Reply from 192.168.0.1: bytes=32 time=60ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255

 
Last edited:
there must be something wrong with your router/cable/ethernet. pings to router should be 0-2ms max almost 100% consistantly. i have never seen anything like that unless its a dodgy wireless signal

Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

those are wireless pings to router, and even then, very stable.

try replacing the wire first. try a different pc maybe?
 
Yep looks like its router/wires/driver etc related in that case, but looking back at this that would affect everything utilizing the internet not just tf2.

Well at any rate you've got it narrowed down now, I'll butt out at this point as I have no clue at all about networks and the like, good luck :)
 
I'm on wired and I know my pings should be low - they always have been.

Now I maxed my internet connection out (newsgroups using SSL) and my ping varied from 0ms to 2ms. So why does CS screw it up? Packet size et?

Ping statistics for 192.168.0.1:

Packets: Sent = 1416, Received = 1409, Lost = 7 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 237ms, Average = 1ms
 
Last edited:
I suggest you borrow a new router from a Friend and put plug in, configure it and try then.

Could be your either net cable loosing connection or your ethernet port.
 
Tried it connected directly to the modem seemed fine with a tiny bit of choke.

Connected back up again and I didn't experience the issue again. I'll try again today.
 
You must log in or register to reply here.
Back
Top Bottom