exit all programs that access internet.
exit all other clients (smartphone, tablets etc) out of your internet.
press winkey+r (run) -> cmd -> ping google.com -t
analyse if the results are stable.
if not -> open a cmd window -> tracert google.com
get the first IP address and do a ping firstip -t
check if that is stable, otherwise continue on the route.

wrote:

...
get the first IP address and do a ping firstip -t
check if that is stable, otherwise continue on the route.

hmmm ))
there is the following command for this, xD:

C:\>pathping /?
 
Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
                [-p period] [-q num_queries] [-w timeout] [-P] [-R] [-T]
                [-4] [-6] target_name
 
Options:
    -g host-list     Loose source route along host-list.
    -h maximum_hops  Maximum number of hops to search for target.
    -i address       Use the specified source address.
    -n               Do not resolve addresses to hostnames.
    -p period        Wait period milliseconds between pings.
    -q num_queries   Number of queries per hop.
    -w timeout       Wait timeout milliseconds for each reply.
    -P               Test for RSVP PATH connectivity.
    -R               Test if each hop is RSVP aware.
    -T               Test connectivity to each hop with Layer-2 priority tags.
    -4               Force using IPv4.
    -6               Force using IPv6.

wrote:

... no improvement. So that isn't the problem.

You might warp if you play with wireless connection; have background services generating network traffic - eg. torrents, inbrowser chats/shouts/web UIs, windows update /any other update; share internet with someone and they're browsing/downloading/torrenting; just have crappy connection/ISP; have bad net settings (dont be lazy - backup/moveout current cfg and run empty to generate from a scratch); try to run another q3-engine based game as per they have different network code to compare; etc etc etc

p.s. Suddenly remembered one interesting thing: if you have an ATI card - try to kill/unload CCC dotnet based control panel together with parent process (use this tool https://technet.microsoft.com/en-us/sysinternals/bb896653) and also change to r_finish "0" inside q3config

wrote:

exit all programs that access internet.
exit all other clients (smartphone, tablets etc) out of your internet.
press winkey+r (run) -> cmd -> ping google.com -t
analyse if the results are stable.
if not -> open a cmd window -> tracert google.com
get the first IP address and do a ping firstip -t
check if that is stable, otherwise continue on the route.

In his case he have a router, so first IP will be his router - pointless test.

I will sugest to test with this soft http://winmtr.net/download-winmtr/ , for host enter IP of the server you play, also from options set ping size from minimum 1500 bytes (this is the normal size of IP packet) , you can increase it up to 65535 but not every host will respond to it. Then you can see if there are packet loss and where. This is better test.

Btw Q3 uses UDP, not ICMP or TCP, but i don't know for now how to test UDP conectivity.

wrote:

wrote:

In his case he have a router, so first IP will be his router - pointless test.

Back to schoolbench for you sir.

@greengirl - pathping is a good idea, however i don't think it brings us any further.
However if he says its stable at 33ms, I don't think someone is causing him extra traffic.
Also ping uses udp like q3 does.

so how about u do ping serverip -t and connect to the server and compare the shown ms with the lag?

Check again? what internet protocol use ping?

Also normal ping with 32 bytes could not give lost packets, but larger can give it if they exists.

Don't bully Schoool , i expect Johnin test results.