
Originally Posted by
Rusty
It could be that the error message is just inaccurate.
Do you know that error 2 is specifically a disconnect error?
Is it possible that one of the tabbed games was unable to receive or send for some reason and the error reporting just landed here?
It IS a disconnect error, and it IS associated with one of the tabbed games. The question is WHY can ONE game not be able to communicate with the SAME SERVER that the other 4 are happily communicating with.
It looks like there is an untrapped error. The server has "dropped a packet" somewhere, this being the reply to the game, but there has NOT been any attempt by the client to reestablish contact, and the software MUST "know" that contact is still available, because it is doing it for the other games. WHY does the client not simply ask for the "lost" packet to be resent, which would be a reasonable attempt to recover the error without having to throw the player out of the game.
There is a more specific problem when this happens during tabbed gaming. When 3 or 4 games get "casino error 2", it prevents any action being taken by the player, because the entire client enters this "blocked" mode, and will not accept ANY commands from the player. Even the EXISTING game that is running in the foreground of my first screenshot would not accept any commands to stop or close the game or casino. I could not tab anywhere else to a window that might have allowed me to close the casino either. The ONLY way I was able to eventually close it was through the task manager.
This problem could be more serious. What if a player was making bigger bets, and the lobby froze, but they could NOT stop a game that was still running, but had appeared to have entered "suck mode" at a time when they had a significant balance. What if this player knew little about computers, and simply sat helplessly watching the slot "suck" the entire balance, unable to stop the game, nor close the casino. They may not think it "safe" to do anything more forceful (like pulling the plug from the wallsocket), nor know how to identify and stop the task from the task manager. Even if they did, they might worry that forcibly aborting the casino could cause all their balance to "disappear".
I have my suspicion that the problem is caused when a game gets the error, and is then unloaded by the client, BUT it's ERROR WINDOW is NOT unloaded along with the game. This window thus becomes invisible, so it CANNOT be closed, and this then results in the entire lobby being locked out from processing ANY further commands, because the client REQUIRES the window to be closed BEFORE any further commands can be accepted.
Given how common this situation has always been, I would have thought MGS would have tested how such errors were handled when tabbed play was in use.
Empty Fruities Astern Capt'n
Back to port for unloading.
Full Sails - before we get raided ourselves.
Bookmarks