I think this feature is needed don't you ?
...say average of 10 ? or better yet, UDP ping ?
TAS Client - Lag Meter to Game Host
Moderator: Moderators
TAS Client - Lag Meter to Game Host
Last edited by monohouse on 07 Jun 2007, 00:56, edited 1 time in total.
Well at the moment it's not possible anymore according to AF: http://spring.clan-sy.com/phpbb/viewtop ... c&start=86
The process of pinging in itself would cause a huge connection lag for all users as the number of pings would be n!
So 200 users online would generate 200x199x198x197x196... = 7.8865786736479050355236321393219e+374
Each user would recieve at least 199 pings.
The only option would be a central server. At which point you then have to make sure its a good server and then there're the issues neddierow pointed out.
So 200 users online would generate 200x199x198x197x196... = 7.8865786736479050355236321393219e+374
Each user would recieve at least 199 pings.
The only option would be a central server. At which point you then have to make sure its a good server and then there're the issues neddierow pointed out.
All that is unnecessary...all that would be required is for each client in a battle to ping the host with a UDP packet on the port that the game would be hosted on. This would test both latency and whether NAT traversal was done properly.AF wrote:The process of pinging in itself would cause a huge connection lag for all users as the number of pings would be n!
So 200 users online would generate 200x199x198x197x196... = 7.8865786736479050355236321393219e+374
Each user would recieve at least 199 pings.
The only option would be a central server. At which point you then have to make sure its a good server and then there're the issues neddierow pointed out.
Yeah, like what is a good server... there's a reason why there are western and eastern US, asian and also european servers available for online play for a lot of games.AF wrote:The only option would be a central server. At which point you then have to make sure its a good server and then there're the issues neddierow pointed out.
You can already test your ping to the central server (/ping in lobby, or heck you could even do ping http://www.google.com on the commandline). Not that this ping has any useful correlation with your in game ping though...
Peet seems right though, theres no need to make every client ping every client (plus the scalability problems..), simply pinging the battle host when in battle should be good enough.
Peet seems right though, theres no need to make every client ping every client (plus the scalability problems..), simply pinging the battle host when in battle should be good enough.
yes this is a good fix to the subject - indeed I mean latency to the host, not the main server, the main server is useless in determining game lag/latency.All that is unnecessary...all that would be required is for each client in a battle to ping the host with a UDP packet on the port that the game would be hosted on. This would test both latency and whether NAT traversal was done properly.
also, fluctuations will be refrected in the average, ping frequency is irrelevant as it's the players in the game and the host are the only thing affecting that.
the main server is also of corse irrelevant, only the lag to the host of the current game, so like an in-battle lag meter to the host only.
this should put an end to players that lag in games and don't know why, before the game is started the lag will already be known.
yhea, "pinging the battle host when in battle should be good enough" only battle host, the rest is irrelevant