I’ve been working on a game you can see over at its website, and sometimes get updates in it’s playcanvas blog. Recently I implemented the some networking - a game tracker allowing people visiting the website to see any other people playing the game.
So, why am I posting this?
Pretty much, Will had some issues while testing it, and I want to get some others involved in testing it. I made a couple changes yesterday which made the tracker survive high ping times better, but I need people to test it from (ideally) all over the world. Even just going and seeing if there are games listed will help me check that people can see the tracker.
The tracker can take up to 10 seconds to show a game.
If you’ve tried to play my game before, it would be great if you could clear your browsers cache. I’m looking into ways to remove the need for people to do this.
Thanks to all the people who have connected to the tracker. I have now had succesful tests of the tracker from nearly every continent. (Japan, Lithuania, Turkey, Phillipines, Russia, US, Uk, Ukrain, South Africa and Germany to name a few).
The tracker appears to be working relatively reliably (or is at least able to recover from any issues).
I’ve made a few changes to the tracker and it is now feature-complete. I will continue monitoring it closely for the next day or two.
Thanks to all who have helped in testing.
The biggest issue people have had is unrelated to the tracker: the game sometimes gets stuck on loading (ie sitting at “Loading Object 4/9” or "Loading Script 9/18."
I am unsure why this is happening and suspect it is cachine rearing it’s head again. I have a plan though, and will implement it over the next few days.
(I assume you’re the guy in the UK who connected roughly an hour ago)
So the tracker is receiving information from you.
You can see that one instance (id 19) hosts a game using the ‘HOST’ command, and then the next time id 17 requests a game list, that game information is relayed along.
Another thought is that you didn’t host the game for very long (about 10 seconds), and it is possible that it simply didn’t refresh the page in time (sometimes things happen a little slowly for an unknown reason).
And that’s GMT the tracker records in, not local time. It is mid-day here, not mid-night…