It really bothering me when i hit a meaty shot it deals like only 30 damage.
What network settings does most good scout use?
posted in
TF2 General Discussion
Welcome to Team Fortress 2. After nine years in development, hopefully it will have been worth the wait.
Welcome to Team Fortress 2. After nine years in development, hopefully it will have been worth the wait.
cl_cmdrate 66 or 67 or 66.6667 (it's a repeating decimal)
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.
cl_cmdrate 66 or 67 or 66.6667 (it's a repeating decimal)
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.
wareyacl_cmdrate 66 or 67 or 66.6667 (it's a repeating decimal)
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.
ty~
[quote=wareya]cl_cmdrate 66 or 67 or 66.6667 (it's a repeating decimal)
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.[/quote]
ty~
cl_updaterate to the same
set those to 40 instead if you're on bad internet or the server is shitty
cl_interp 0 if you use cl_interp_ratio
cl_interp_ratio 1 (or 1.2 if you're ballsy about source engine's quirks) on projectile classes (including medic/spy) or 2 (or 2.2 if you're ballsy about source engine's quirks) on hitscan oriented ones
ratio is based on your rates so if you use that then you don't have to worry about
cl_interp_ratio 0 if you use cl_interp
cl_interp 0.015 (0.0152 for 66 exactly) for projectile classes and cl_interp 0.03 for hitscan oriented ones IF YOU HAVE RATES >66
cl_interp 0.025 for projectile classes and cl_interp 0.05 for hitscan oriented ones IF YOU HAVE RATES = 40
Increase cl_interp by like 0.005 or or something in that area if you have bad latency jitter fucking up the animations. If it gets really bad then use hitscan settings on all classes. If it's still bad, use "bad net" settings even if your connection should be good.
you can use whatever you want as long as it's not pants on head retarded and it'll mostly work, these are good guidelines though
#1 cause of bad hitreg on a decent connection is lag compensation glitching up, not shit settings. In fact, the default tf2 settings have ridiculously good hitscan hitreg; it's just that they ruin timing, a lot.[/quote]
ty~
the biggest culprit of shitty hitreg in this game is variance in your ping (jitter)
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber
the biggest culprit of shitty hitreg in this game is variance in your ping (jitter)
http://www.pingtest.net/
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber
http://www.pingtest.net/
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber
enigmathe biggest culprit of shitty hitreg in this game is variance in your ping (jitter)
http://www.pingtest.net/
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber
As a time warner cable customer, I can confirm this. :(
[quote=enigma]the biggest culprit of shitty hitreg in this game is variance in your ping (jitter)
http://www.pingtest.net/
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber[/quote]
As a time warner cable customer, I can confirm this. :(
http://www.pingtest.net/
cable connections during peak hours are usually most susceptible to jitter, but there's unfortunately nothing you can really do about it other than switch to dsl or fiber[/quote]
As a time warner cable customer, I can confirm this. :(
Please
sign in through STEAM
to post a comment.