Monday, April 16, 2012

0 Ping Lobby Bug

It might have just been co-incidence, but some of us on our teamspeak server were looking to play a game of SupCom2, but couldn't get all of us into the lobby because 2 of them couldn't connect; they always got the 0 ping lobby kick bug to each other.
UNTIL
Someone suggested using Hamachi (a VPN program that we all use wnyways to play FA), and low and behold it worked. Only the 2 of them had to load it, but as soon as they did all connection issues were solved.
Now I know it is not realistic to have everyone on a VPN but I am merely posting this so that the guys at GPG know that this may have been (again I don't know for sure) how we solved the lobby issues.|||I'd be really surprised if the game would even publish on an address/interface through which it couldn't ping the steam servers. But then again, you can supposedly play LAN games via Steam so long as you have some kind of internet connection, so maybe that works.
If so, and all players were in the same hamachi group and were all able to see each others' hamachi IPs, that probably means that somebody had a firewall or poorly-configured NAT that was interfering with the game's connection, and hamachi just sidestepped that.|||I'm pretty sure that the game can connect over any available connection to other clients, Steam only dishes out the client list and handles the Internet case.|||Well, what I'm wondering is whether the initial connection is handled entirely via steam / internet interface, after which point the host shares all peers' addresses (including local addresses?) among each other, or if the game simply does local broadcast and discovery on the 'LAN' adapter, and that's the only way that the peers connect.

No comments:

Post a Comment