Indie-Resource.com

I know real time gaming on a phone with 2G isn't a true option, but I've noticed I cannot even connect to the server, is there a reason for this? I ping my server via cmd and get 400-500ms. I've tried changing the stream intervals and render latency, still the client doesn't connect. Instead it will hang at connecting, then after an inordinate amount of time will ask if the server is running. What intrigues me the most is the pure lack of activity on the server when trying to connect, no log files at all. Verified working on faster connections, just would like to get some sort of a connection on a slow connections as well, Thanks!

It is odd that you do not get any connection at all. Are you sure the server details are correct and that the device supports the transport you have selected (e.g. websockets etc)?

The speed of the connection is not taken in to consideration in connecting and stream settings will have no effect either until a connection is established.

Very interested to hear if you find out what it is as this is not normal behaviour for the networking system.

Probably should have mentioned I was tethering via WIFI, dunno if that makes a difference.

On the same connection I RDP'd into a cloud server and the game connected and loaded there, so I know the settings were all correct

I moved the server from a cloud-based VM to a physical machine and I can connect through 2G. Exact code, only changed the IP the client connected to, Thanks! Luckily you answered some other things I was wondering about too I can imagine you'll see a bit more of my posts. Hopefully they can become increasingly useful!

EDIT:
http://blog.hekkers.net/2012/12/09/webs ... operators/

I got lucky and it worked after the cloud to physical switch, but later tonight it started doing it again. I found this, and changed the port to 443. Flawless. Also I'm VERY impressed with the networking of the engine on a 2G connection.

Thanks!

Smoozilla wrote:I moved the server from a cloud-based VM to a physical machine and I can connect through 2G. Exact code, only changed the IP the client connected to, Thanks! Luckily you answered some other things I was wondering about too I can imagine you'll see a bit more of my posts. Hopefully they can become increasingly useful!

EDIT:
http://blog.hekkers.net/2012/12/09/webs ... operators/

I got lucky and it worked after the cloud to physical switch, but later tonight it started doing it again. I found this, and changed the port to 443. Flawless. Also I'm VERY impressed with the networking of the engine on a 2G connection.

Thanks!

Wow that is very interesting I never knew that some mobile operators blocked websockets! Great article & investigation.

Very happy you are impressed with the engine's networking over a 2g connection, keep up the updates, I think we'd all love to hear how you get on with your game!

Most definitely