cs movie eka8 (deathmatch 1.6)
Started by ecliptic, May 25 2006 04:39 PM
32 replies to this topic
#21
Posted 06 May 2008 - 06:23 AM
from what i remember its alot of your net connection to a particular server. you getting the same amount on different servers? just one in particular? what rates are you using (rate,cl_cmdrate,cl_updaterate)
#22
Posted 06 May 2008 - 08:17 PM
Quote
from what i remember its alot of your net connection to a particular server. you getting the same amount on different servers? just one in particular? what rates are you using (rate,cl_cmdrate,cl_updaterate)
I really appreciate your reply and possible help bro, i really do. Noone on friggin pubs give answers.. and my old boys are no longer playing.
Heres what ive tried:
My connection is 20 / 5
rate: 99999
cl_cmdrate, 101 ( usually) 100, 90
cl_updaterate: 101, 100, 70 , 65, 75, 350 (lol) etc.. No difference
ex_interp : 0
My connections more than able to handle this game as is my pc, but i cant get a f*kin shot to register. I used to go from a 40 -10 ( 4:1 ratio) and now i sit at mabey 8 - 26 ( 0.2 : ? ratio) it just takes forever for a shot to register , right on the head with a degal on an AFK player, it takes mabey 6 shots when stryfing. 2 shots standing still. Almost impossible with the ak and rarely with an m4.
Dont get me wrong, the few kills i get on servers are just about all headshots, but their just WAY too hard to get kills now.. i get so frustrated i have to leave the puter. This is on mainly a couple different servers, but if the servers large its 100% of the time. If i go to a deathmatch server, my choke is at 100 , 100% of the time. If im on aim_ak_colt, my choke is at 30 - 50 % if players are about 10 - 16. If its like 6 or 7 its " ok" .
My box:
Intel quadcore 2.4
4 GB dual channel DDR2 667mhz
nvidia 8800GT with up-to-date drivers
Windows vista home premium
500 GB Raid-0 drives ( 2x250)
If you like i can make a .dem vid for you to watch and see what im talking about/
#23
Posted 06 May 2008 - 08:24 PM
Also heres the tracert to the two or three servers i play on the most:
[size=1]
Tracing route to 72.5.250.116 over a maximum of 30 hops
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms 72.91.11.1
3 8 ms 9 ms 9 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 23 ms 22 ms 21 ms so-7-3-0-0.BB-RTR1.ATL01.verizon-gni.net [130.81.19.30]
5 44 ms 45 ms 43 ms 0.so-5-0-0.XL3.DFW13.ALTER.NET [152.63.98.73]
6 44 ms 45 ms 43 ms 0.so-6-0-0.GW3.DFW13.ALTER.NET [152.63.100.73]
7 44 ms 45 ms 46 ms internapGIGE1-gw.customer.alter.net [65.208.15.230]
8 45 ms 44 ms 44 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]
9 45 ms 43 ms 44 ms 72.5.250.116
Trace complete.
==========================================================================
Tracing route to 72.5.86.174 over a maximum of 30 hops
1 1 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 6 ms 72.91.11.1
3 9 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 22 ms 22 ms 24 ms so-7-3-0-0.BB-RTR1.ATL01.verizon-gni.net [130.81.19.30]
5 23 ms 24 ms 84 ms 0.so-7-0-0.XL1.ATL1.ALTER.NET [152.63.86.105]
6 24 ms 24 ms 24 ms 0.so-7-0-0.XR1.ATL1.ALTER.NET [152.63.86.86]
7 23 ms 25 ms 21 ms 195.ATM6-0.GW9.ATL1.ALTER.NET [152.63.85.105]
8 25 ms 23 ms 24 ms internap-gw.customer.alter.net [63.122.231.198]
9 23 ms 25 ms 24 ms border2.tge-4-1-bbnet2.acs002.pnap.net [64.94.0.83]
10 25 ms 24 ms 25 ms 72.5.86.174
Trace complete.
=============================================================================
Tracing route to atl1.artofwarcentral.com [69.12.53.108]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 7 ms 72.91.11.1
3 9 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 42 ms 41 ms 41 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]
5 42 ms 41 ms 42 ms 130.81.15.42
6 52 ms 43 ms 42 ms so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]
7 44 ms 44 ms 44 ms so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]
8 43 ms 44 ms 44 ms so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]
9 43 ms 45 ms 43 ms so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]
10 57 ms 56 ms 57 ms so-1-0-0.mpr2.atl6.us.above.net [64.125.28.230]
11 56 ms 56 ms 57 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
12 40 ms 39 ms 39 ms 209.249.11.205.speakeasy.net [209.249.11.205]
13 39 ms 39 ms 39 ms atl1.artofwarcentral.com [69.12.53.108]
Trace complete.
[size=1]
Tracing route to 72.5.250.116 over a maximum of 30 hops
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms 72.91.11.1
3 8 ms 9 ms 9 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 23 ms 22 ms 21 ms so-7-3-0-0.BB-RTR1.ATL01.verizon-gni.net [130.81.19.30]
5 44 ms 45 ms 43 ms 0.so-5-0-0.XL3.DFW13.ALTER.NET [152.63.98.73]
6 44 ms 45 ms 43 ms 0.so-6-0-0.GW3.DFW13.ALTER.NET [152.63.100.73]
7 44 ms 45 ms 46 ms internapGIGE1-gw.customer.alter.net [65.208.15.230]
8 45 ms 44 ms 44 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]
9 45 ms 43 ms 44 ms 72.5.250.116
Trace complete.
==========================================================================
Tracing route to 72.5.86.174 over a maximum of 30 hops
1 1 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 6 ms 72.91.11.1
3 9 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 22 ms 22 ms 24 ms so-7-3-0-0.BB-RTR1.ATL01.verizon-gni.net [130.81.19.30]
5 23 ms 24 ms 84 ms 0.so-7-0-0.XL1.ATL1.ALTER.NET [152.63.86.105]
6 24 ms 24 ms 24 ms 0.so-7-0-0.XR1.ATL1.ALTER.NET [152.63.86.86]
7 23 ms 25 ms 21 ms 195.ATM6-0.GW9.ATL1.ALTER.NET [152.63.85.105]
8 25 ms 23 ms 24 ms internap-gw.customer.alter.net [63.122.231.198]
9 23 ms 25 ms 24 ms border2.tge-4-1-bbnet2.acs002.pnap.net [64.94.0.83]
10 25 ms 24 ms 25 ms 72.5.86.174
Trace complete.
=============================================================================
Tracing route to atl1.artofwarcentral.com [69.12.53.108]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 7 ms 72.91.11.1
3 9 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
4 42 ms 41 ms 41 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]
5 42 ms 41 ms 42 ms 130.81.15.42
6 52 ms 43 ms 42 ms so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]
7 44 ms 44 ms 44 ms so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]
8 43 ms 44 ms 44 ms so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]
9 43 ms 45 ms 43 ms so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]
10 57 ms 56 ms 57 ms so-1-0-0.mpr2.atl6.us.above.net [64.125.28.230]
11 56 ms 56 ms 57 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
12 40 ms 39 ms 39 ms 209.249.11.205.speakeasy.net [209.249.11.205]
13 39 ms 39 ms 39 ms atl1.artofwarcentral.com [69.12.53.108]
Trace complete.
#24
Posted 06 May 2008 - 10:00 PM
well you usualy want to keep you cmd and update rates the same number, your RATE caps out at 25000, not sure if having a higher number can cause choke, its quite possible, never tried it.
I also did a bit of poking around, and it seems that a servers 'tic rate' + 1 needs to be your cmd and updater rate, IE if the server tick rate is 100, then your cl_cmdrate and cl_updaterate need to be 101, 66 = cl rates of 67. if your rates are too low or too much above that rate, you will get choke.
You can also try playing with ex_interp .05 (its what i use on most servers online) it seems to give the closest to .001 without getting too choppy cause that can happen with online servers.(which is what zero will set it to if you have cmd and update rates set to 101) if that doesnt work stick with the default of .1 cause some pub servers can be horrible.
make sure fps_max is set to 101 or even 121
If you do not know of the Tic-rate of the server you are connected to you can type:
sv_maxupdaterate
it should tell you
feel free to ask anymore questions
I also did a bit of poking around, and it seems that a servers 'tic rate' + 1 needs to be your cmd and updater rate, IE if the server tick rate is 100, then your cl_cmdrate and cl_updaterate need to be 101, 66 = cl rates of 67. if your rates are too low or too much above that rate, you will get choke.
You can also try playing with ex_interp .05 (its what i use on most servers online) it seems to give the closest to .001 without getting too choppy cause that can happen with online servers.(which is what zero will set it to if you have cmd and update rates set to 101) if that doesnt work stick with the default of .1 cause some pub servers can be horrible.
make sure fps_max is set to 101 or even 121
If you do not know of the Tic-rate of the server you are connected to you can type:
sv_maxupdaterate
it should tell you
feel free to ask anymore questions
#25
Posted 06 May 2008 - 10:36 PM
Ill go give that a look tomorrow or so. kinda late / early lol
also, check this out when you get a sec, try and keep an eye on my choke
http://uploadingit.c...ti8/wtf.dem.zip
also, check this out when you get a sec, try and keep an eye on my choke
http://uploadingit.c...ti8/wtf.dem.zip
#26
Posted 08 May 2008 - 10:24 AM
Tried the different settings, helped a bit havnt been to a large server here yet but ill give it a shot.
edit: ok here we go, in a deathmatch.
edit: ok here we go, in a deathmatch.
#27
Posted 08 May 2008 - 11:26 AM
wow and thats with trying what i said to try?
matched your rates with the tic rate and such?
matched your rates with the tic rate and such?
#28
Posted 09 May 2008 - 02:31 AM
Quote
wow and thats with trying what i said to try?
matched your rates with the tic rate and such?
matched your rates with the tic rate and such?
yessir, indeed i did.
sv_maxupdaterate 100
cl_cmdrate 101
cl_updaterate 101
rate 25000
ex_interp 0
Ive never had this problem before bro..
#29
Posted 09 May 2008 - 06:31 AM
i generally use these as my pub rates
rate 20000
cl_updaterate 70
cl_cmdrate 70
ex_interp .05
fps_max 101
fps_modem 101
give those a shot :-/
rate 20000
cl_updaterate 70
cl_cmdrate 70
ex_interp .05
fps_max 101
fps_modem 101
give those a shot :-/
#30
Posted 09 May 2008 - 06:10 PM
Quote
i generally use these as my pub rates
rate 20000
cl_updaterate 70
cl_cmdrate 70
ex_interp .05
fps_max 101
fps_modem 101
give those a shot :-/
rate 20000
cl_updaterate 70
cl_cmdrate 70
ex_interp .05
fps_max 101
fps_modem 101
give those a shot :-/
Mabey its in a good mood, or mabey the "fps_modem 101" but my choke is barely existent now.. the fps_modem is the only setting i havnt tried till now. seemed to work, for now i think.
#31
Posted 09 May 2008 - 06:47 PM
yar, its always something dumb :-/ now that i think about it, thats what was screwing me up when i formated my comp a few months back
#32
Posted 09 May 2008 - 06:50 PM
lol lets hope for the best ^__^ thaks for all your help, hope im not just getting lucky lol..
#33
Posted 19 May 2008 - 08:08 PM
Well think i figured out the problem.... not fully but MUCH better,
Now i overclocked my video card, like... alot... 145 mhz i believe.. and my shots register BEAUTIFULLY . On deathmatches my chokes still 100 % but its not effecting my shots any now!
A mixture of thoes rates you gave me as well as the OCing is a miracle.
Now i overclocked my video card, like... alot... 145 mhz i believe.. and my shots register BEAUTIFULLY . On deathmatches my chokes still 100 % but its not effecting my shots any now!
A mixture of thoes rates you gave me as well as the OCing is a miracle.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users













