Forum
Microlags problem
Created 29th June 2017 @ 18:42
Add A Reply Pages: 1
So I have this net breakdows while playing tf2 that makes my game unplayable
There you have the clue of the breakdowns:
https://steamcommunity.com/sharedfiles/filedetails/?id=959246105
https://steamcommunity.com/sharedfiles/filedetails/?id=959246040
What can I do to solve this problem? Thank you
Edit: Im playing with wireless
Last edited by Stuppa,
I’m not sure why you have 50ms interpolation and 20/30 cmdrate/updaterate. As far as I’m aware those aren’t default settings (default interp is 100 I believe), nor settings anyone should use regardless of how bad their internet is. Do you have regular internet dropouts outside of TF2? What is your download/upload speed? Are you sure the issue is network related and the microstutters aren’t being caused by something else?
// ----------------------------------------------------------------------------
// Net settings
// ----------------------------------------------------------------------------
// Whilst net settings perhaps aren't an integral part of an FPS config, they
// are a fact of life in competitive TF2, and as such, they are included here.
//
// A common question I am asked -- what defines whether a good connection is
// good or bad? Mostly personal preference. If you're not willing to make the
// choice, try both and see which is better for you.
//
// Generally, meeting both of the following conditions would classify it as a
// good connection:
//
// - Ping of <80 to the average server you join
// - Generally no/negligible choke/loss (can be checked with `net_graph')
//
// There's some pretty good documentation on this here:
// http://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking
//
// Uncomment (remove the `//' from) one of the groups if you want to use them.
// ----------------------------------------------------------------------------
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Competitive connection // Very few servers will have these settings
//cl_cmdrate 128
//cl_interp .007 // this will likely have to be user defined .007 should be roughly the lowest interp, hit scan might do well at .0152 for this
//cl_interp_ratio 1
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 128
//rate 90000 // With higher tick rates you have more bandwidth being used
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
Try putting this in your autoexec. These are the network settings Comanglia suggests.
http://www.teamfortress.tv/25328/comanglias-config-fps-guide
edit: formatting
Last edited by mellow,
I will put what you texted in my autoexec, thanks in advanced.
Add A Reply Pages: 1
content rss