AXESWY wrote:Yunus wrote:So, what do you think now??
Please open your CMD and type the following :
the ip address belong to RepZ.eu Conquest Top Maps #2 server it's located in Germany
in Nexus server browser I get 80 which not accurate
It's perfectly accurate because when you do a cmd ping command you get the response immediately, when you are in game it takes a few milliseconds for your game client to send the request and for server to process and respond, and plus the fps lock on the servers adds about 1-10 ms (this is why servers have different ping). The game measures time to register that's much higher than the ping itself due to the client. For example in counter strike 1.6 you could have a ping less than 10 in game, but what most players do not know is that they are playing 100 ms in the past because a delay is needed to prevent "rubberbanding". In cs 1.6 it can be lowered to 9 ms minimum but when spectating players they would appear move and aim snappy, it wouldn't be smooth. So if i was to monitor how long it takes in counter strike when I pull the trigger until it registers a death on my screen it would be around 130~150 ms, but the game would say less than 10 because that's how long it takes to ping the server. BC2 counts all these things in so you know when you pull the trigger it takes that long to register it on your screen. There is also a flaw in the net code where you shoot people who you see on your screen but server processes things on their screen (it's gets a bit tricky here, if your ping is 70 and the other player's ping is 30 on the server you are 70 ms in the past and the other player is 30 ms, but for you the other player is 100 ms in the past), so it's missing some kind of a delay on the client side. Sometimes when it looks like you hit him, and you see the animation, but a different situation actually happened on the server so it would not register a hit.
