Super!

/T

yeah - I think its down to your client and what specific part of it is trying to send to the server. If its the game itself where you are running around (e.g. arena game) - I'd freeze the game and show a "reconnecting" message. For chat application, do like Skype. For a turn based game, ca...

Ahhh yeah - a non-running server in the first place. I read it as a server that is turned off and the client then keeps the connection alive. No issues here on server that isnt running. So a little more info needed if you still have this issue consistently with the latest dll. Anything from OS to Un...

Not tried myself - for our games and examples we always centralize network communication in a single network handler component for the game. But afaik there should be no reason for it not to work - registering from separate scripts and getting dual callbacks. Are you certain you are registering agai...

Fixed in next update of the docs - thx for reporting

/T

It should be fixed in 1.0.3 version of the API. But also make sure you update your server to latest version.

Several good fixes are in the new server

/Thomas

This should be fixed in the 1.0.3 release of the API.

If not, hit me with a bat!

/T

Putting things into a single object and sending that is a very good approach. Use the players sfs connection id as key. Check the documentation and examples using SFSObject and SFSArray on how to embed things into something you can send in a single request to the server (or from server to clients). ...

Wow - mega weird. Thanks for reporting and warning others.

We definitely didnt add any changes there with ToString, so unsure if its fixable.

But at least someone searching for it will find it now.

/Thomas

Never seen that before and seems to happen deep inside mono. Googling points to machine resource issues (memory or number of sockets).

What OS and environment?

Do you have a repro case? And are you using the 1.0.3 C# API?

/Thomas

We had a similar issue for our upcoming game, but I was not personally involved in the fix. So I dont know for certain if there was anything else done than the server side configuration change. The programmer who did it is on vacation this week. Will ask him next week when he returns. On the server ...

We have not been able to reproduce any types of crashes on disconnect with the 1.0.3 version.

If you have any repro case, please send it over and I'll take a look! Otherwise will try to repro it with server shutdown (we've tried that several times and not had issues anymore)

/Thomas

Think I missed this one and answered for the same question somewhere else. Anyways - lots more info to go by here. Generally it is pretty weird error. We have lots of iPad code that works flawless - never had this issue on any of our own games. I take it that your own builds work perfectly well as y...

Will check it out - seems there is generally an error on logout/disconnect to be investigated and fixed.

Going to take at least 1+ week before it gets attention, as I'm hit by vacation and conference time

Will check it out - seems there is generally an error on logout/disconnect to be investigated and fixed.

Going to take at least 1+ week before it gets attention, as I'm hit by vacation and conference time

/Thomas