Jump to content

CS 1.6 Loss and Choke


RevServers

Recommended Posts

I have installed my CS 1.6 game and I am getting loss and chokes between 1 and 10 with or without people in the server..

 

the FPS is 520 constant but when people start joining (12 slots) the fps is not stable at all.

 

cl_maxupdaterate 101

cl_maxrate 25000

sys_ticrate 1000

 

I have windows media player running to boost the FPS

 

 

I am running the server on a Quad Core with 4GB ram

Link to comment
Share on other sites

Can you post your net_graph 3 when the issue is happening. Also what type of internet connection do you have? You might want to do a tracert from your location back to the server or even use HLSW to see a real time ping of each hop to the server. It could be a network problem instead of a config problem as this point.

 

George

Link to comment
Share on other sites

Even if they are all from different locations there could still be one shared point of entry where there is an issue. This is why it is best to run a tracert and see if there is a problem. Also you didnt answer my question has to what type if connection do you have. You might just be overloading the connection if you are hosting from your home, since most home connections are slow on the upload.

 

George

Link to comment
Share on other sites

I did it 3 times, here is what it shows when I tracert from my home to the server

 

Tracing route to 208.100.27.44

over a maximum of 30 hops:

 

1 <1 ms 1 ms <1 ms mylocalnetwork

2 * * * Request timed out.

3 10 ms 10 ms 9 ms gig7-0-0-104.orldflunpk-rtr2.cfl.rr.com [24.95.2

33.56]

4 14 ms 13 ms 14 ms gig3-1-0.orldflaabv-rtr4.cfl.rr.com [24.95.228.5

]

5 27 ms 23 ms 23 ms ge-1-3-0.cr1.atl20.tbone.rr.com [66.109.6.104]

6 25 ms 23 ms 23 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]

7 23 ms 26 ms 22 ms xe-2-3-0-303.cr1.atl1.us.nlayer.net [69.31.135.2

5]

8 38 ms 38 ms 37 ms xe-1-2-0.cr2.ord1.us.nlayer.net [69.22.142.45]

9 37 ms 37 ms 37 ms po2.ar1.ord1.us.nlayer.net [69.31.111.138]

10 38 ms 39 ms 39 ms as32748.tge8-4-116.ar1.ord1.us.nlayer.net [69.31

.111.34]

11 39 ms 38 ms 39 ms ip17.208-100-32.static.steadfast.net [208.100.32

.17]

12 39 ms 39 ms 37 ms ip44.208-100-27.static.steadfast.net [208.100.27

.44]

 

 

 

Tracing route to 208.100.27.44

over a maximum of 30 hops:

 

1 1 ms <1 ms <1 ms mylocalnetwork

2 * * * Request timed out.

3 9 ms 7 ms 9 ms gig7-0-0-104.orldflunpk-rtr2.cfl.rr.com [24.95.2

33.56]

4 27 ms 14 ms 13 ms gig3-1-0.orldflaabv-rtr4.cfl.rr.com [24.95.228.5

]

5 23 ms 23 ms 23 ms ge-1-3-0.cr1.atl20.tbone.rr.com [66.109.6.104]

6 24 ms 23 ms 22 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]

7 24 ms 22 ms 80 ms xe-2-3-0-303.cr1.atl1.us.nlayer.net [69.31.135.2

5]

8 37 ms 38 ms 38 ms xe-1-2-0.cr2.ord1.us.nlayer.net [69.22.142.45]

9 37 ms 37 ms 37 ms po2.ar1.ord1.us.nlayer.net [69.31.111.138]

10 40 ms 38 ms 40 ms as32748.tge8-4-116.ar1.ord1.us.nlayer.net [69.31

.111.34]

11 44 ms 39 ms 39 ms ip17.208-100-32.static.steadfast.net [208.100.32

.17]

12 40 ms 38 ms 39 ms ip44.208-100-27.static.steadfast.net [208.100.27

.44]

 

Trace complete.

 

 

 

Tracing route to 208.100.27.44

 

over a maximum of 30 hops:

 

1 1 ms <1 ms <1 ms mylocalnetwork

2 * * * Request timed out.

3 8 ms 8 ms 10 ms gig7-0-0-104.orldflunpk-rtr2.cfl.rr.com [24.95.2

33.56]

4 14 ms 15 ms 15 ms gig3-1-0.orldflaabv-rtr4.cfl.rr.com [24.95.228.5

]

5 23 ms 24 ms 26 ms ge-1-3-0.cr1.atl20.tbone.rr.com [66.109.6.104]

6 22 ms 33 ms 29 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]

7 23 ms 23 ms 23 ms xe-2-3-0-303.cr1.atl1.us.nlayer.net [69.31.135.2

5]

8 38 ms 37 ms 37 ms xe-1-2-0.cr2.ord1.us.nlayer.net [69.22.142.45]

9 37 ms 37 ms 41 ms po2.ar1.ord1.us.nlayer.net [69.31.111.138]

10 39 ms 39 ms 39 ms as32748.tge8-4-116.ar1.ord1.us.nlayer.net [69.31

.111.34]

11 38 ms 39 ms 40 ms ip17.208-100-32.static.steadfast.net [208.100.32

.17]

12 38 ms 38 ms 38 ms ip44.208-100-27.static.steadfast.net [208.100.27

.44]

 

Trace complete.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Who's Online   0 Members, 0 Anonymous, 6 Guests (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use