"Cannot connect to server" message when loading game with failed missions
Sounds pretty specific, but here's my issue (ticket created):
When I was able to play the game, if I tried to abort a mission it would immediately display "Cannot connect to server" and kick me to main menu. When I returned to space and checked my mission data, I would find that the mission I tried to abort would still be present and active. Lather rinse repeat...
So since I couldn't abort the missions that I've taken, I let them expire and fail and took the penalty hit. The problem now is whenever I load the game with these failed missions, I immediately get the "Cannot connect to server" message and kick to main menu. Unplayable.
I checked back a day or two later to get a Netlog for the ticket, but then the immediate crashing stopped. I was able to play, and I found that still clicking on "abandon" or whatever is listed as an option for failed missions would still disconnect and kick me to main menu. For some dumb reason I decided to take on a new mission, so here I am today with a new failed mission and cannot play the game.
Here's my educated guess:
When a mission is failed or aborted, there is a certain handshaking that takes place between the client and server. This communication must be corrupt or unrecognizable by the server, and proceeds to kick the client for bad information.
I have just updated to G1.04 and am still experiencing the issue.