BenWiley4000 wrote:Ok so I updated the firmware today, which fixed a lot of problems with my system, so I thought I would give this another spin. I killed X before I ran this, to free up some memory. Unfortunately I got the same result as before-- I accelerated through space a little bit before the program quit and said it had lost connection. When I tried to run it again, it didn't even attempt to start because it "couldn't connect".
Also, the keyboard wouldn't respond, again.
First sorry for the slow response - I've been down in London for a week, far away from my Pi and Pi-related thoughts.
It sounds most likely that your Pi lost it's connection to the Internet when you got disconnected from the game, and then couldn't start it again. For the moment we have no offline mode, so you need a working internet connection. It's possible if your connection is very slow that the server might kick you off because your connection is getting too backed up - I need to improve the way we handle that, but with only 1 or 2 players online I've never seen it cause a real problem.
I'm very keen to understand how the game is quitting in such a way as to stop your keyboard responding. We change the keyboard mode while the game is running in order to capture the keyboard state (so we can see you are holding down a key, instead of just seeing characters). The keyboard state should be restored when the game exits or if the game crashes after pretty much any signal other than SIGKIlL (which we can't set a handler for). I presume you're not killing the game from an ssh session or anything weird like that though, so it really shouldn't leave your keyboard in a bad state. Could you tell me exactly what happened to the game before it exitted without restoring the keyboard?