Upvote Upvoted 2 Downvote Downvoted
tf2 freezes for 1 sec every minute or so
posted in Q/A Help
1
#1
1 Frags +

Ever since the update two days ago, I've been freezing for around 1 second every minute or so. It happens to me on all servers. Is this a rate problem, or does it just mean my internet is too shitty? Anyone know a fix for this?
Thanks for the help.

Ever since the update two days ago, I've been freezing for around 1 second every minute or so. It happens to me on all servers. Is this a rate problem, or does it just mean my internet is too shitty? Anyone know a fix for this?
Thanks for the help.
2
#2
0 Frags +

Do you mean the actual game freezing or the connection freezing and showing "Connection Problem"?

I have the latter issue occasionally.

Do you mean the actual game freezing or the connection freezing and showing "Connection Problem"?

I have the latter issue occasionally.
3
#3
0 Frags +

What are your net-related settings in your autoexec?

What are your net-related settings in your autoexec?
4
#4
0 Frags +

i just freeze, theres no red text in the corner. Everything speeds up the second after and i resume playing.
Settings:
cl_cmdrate 66
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66
rate 60000

i just freeze, theres no red text in the corner. Everything speeds up the second after and i resume playing.
Settings:
cl_cmdrate 66
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66
rate 60000
5
#5
0 Frags +

I know it sounds crazy but try these settings for a bit and see if you still have any issues. I know, tech wizards out there, it doesn't make sense to use these settings, I know, but it has helped me before (I think, unless it was placebo). It can't hurt to try it.

cl_cmdrate 100
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 100
rate 100000

I know it sounds crazy but try these settings for a bit and see if you still have any issues. I know, tech wizards out there, it doesn't make sense to use these settings, I know, but it has helped me before (I think, unless it was placebo). It can't hurt to try it.

cl_cmdrate 100
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 100
rate 100000
6
#6
0 Frags +

fps_max 0 used to cause stutters. Idk about your problem

fps_max 0 used to cause stutters. Idk about your problem
7
#7
0 Frags +

wireless connection used to do this on vista to me, is that your current set up?

wireless connection used to do this on vista to me, is that your current set up?
8
#8
0 Frags +
thinkI know it sounds crazy but try these settings for a bit and see if you still have any issues. I know, tech wizards out there, it doesn't make sense to use these settings, I know, but it has helped me before (I think, unless it was placebo). It can't hurt to try it.

cl_cmdrate 100
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 100
rate 100000

There really is not difference using 66 vs 100. Even using 100 for cmd/updaterate the packets just buffer and send the max rate the server can handle. Which is why in older hlds / half life 1 101 / 101 was always the pre-reqs. Some will say tuning cmd rate specifically (source / srcds) whereas leaving update rate 100 might have some differences. The stuttering itself could be caused by cl_interp in which interpolation from the server where players moving looks out of sync and crazy possibly extrapolating throwing off hit boxes, registry, ect... and making people look like a slide show / jittery. Even then it is a comfort thing for the player. Tweaking is done at risk since it does have a heavy effect on where your shots land, how the enemy (looks to be moving), and in other cases how soon you see him. So if player A has an interp of .015 15msec and player 2 has an interp of .03 30msec, player A would see player B slightly before player B sees player A. But if interp is too low this can also cause hit scan to be awful and completely inept on all accounts. Which is why pre-config'd FPS configs and others that do it for you can have a negative impact if the components are not up to snuff and numerous other factors. I advise no one to EVER look into net code and all the meanings. You will just get frustrated. Also depending on the server, they may have it min/maxed for you and you will never know.

On the topic. It sounds like you just need to up your rates or you could have loss (start > cmd > tracert IP ]Look for loss) / possible computer hardware issue in worst case scenario.

/rant

[quote=think]I know it sounds crazy but try these settings for a bit and see if you still have any issues. I know, tech wizards out there, it doesn't make sense to use these settings, I know, but it has helped me before (I think, unless it was placebo). It can't hurt to try it.

cl_cmdrate 100
cl_interp 0
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 100
rate 100000[/quote]

There really is not difference using 66 vs 100. Even using 100 for cmd/updaterate the packets just buffer and send the max rate the server can handle. Which is why in older hlds / half life 1 101 / 101 was always the pre-reqs. Some will say tuning cmd rate specifically (source / srcds) whereas leaving update rate 100 might have some differences. The stuttering itself could be caused by cl_interp in which interpolation from the server where players moving looks out of sync and crazy possibly extrapolating throwing off hit boxes, registry, ect... and making people look like a slide show / jittery. Even then it is a comfort thing for the player. Tweaking is done at risk since it does have a heavy effect on where your shots land, how the enemy (looks to be moving), and in other cases how soon you see him. So if player A has an interp of .015 15msec and player 2 has an interp of .03 30msec, player A would see player B slightly before player B sees player A. But if interp is too low this can also cause hit scan to be awful and completely inept on all accounts. Which is why pre-config'd FPS configs and others that do it for you can have a negative impact if the components are not up to snuff and numerous other factors. I advise no one to EVER look into net code and all the meanings. You will just get frustrated. Also depending on the server, they may have it min/maxed for you and you will never know.

On the topic. It sounds like you just need to up your rates or you could have loss (start > cmd > tracert IP ]Look for loss) / possible computer hardware issue in worst case scenario.

/rant
9
#9
0 Frags +

thanks think, that config+ restarting my modem did the trick.

thanks think, that config+ restarting my modem did the trick.
10
#10
4 Frags +

Suck it ApolloniusX.

Suck it ApolloniusX.
11
#11
0 Frags +
thinkSuck it ApolloniusX.

You do know what i posted was the reasoning why your post works right?

Then again i guess there is no need to explain why. My bad.

p.s. a few of those settings are default ;)

[quote=think]Suck it ApolloniusX.[/quote]
You do know what i posted was the reasoning why your post works right?

Then again i guess there is no need to explain why. My bad.

p.s. a few of those settings are default ;)
12
#12
0 Frags +

I get these stutters too, but I also get FPS 20 a lot. Basically anytime someone shoots me my game freezes. It was almost unplayable today (if anyone was in Soap or MGE with me in the past 2 hours you'd probably notice).

I think I might try think's config....but I feel like that's not the only problem.

I get these stutters too, but I also get FPS 20 a lot. Basically anytime someone shoots me my game freezes. It was almost unplayable today (if anyone was in Soap or MGE with me in the past 2 hours you'd probably notice).

I think I might try think's config....but I feel like that's not the only problem.
Please sign in through STEAM to post a comment.