ChessCube Version 3: Known Issues

The developers are going to be fixing bugs and building some exciting new functionality for the upcoming World Chess Championship (more on that will be announced later), so there are various known bugs and issues that will only be fixed in a new version, due by the end of this month. The following is a list of bugs/issues, in order of frequency reported to support. It is not a comprehensive list and I will add to this thread as needed.

Unable to connect to the server
Description: Users get Error 002, 2046/RSL errors
Possible solution: See: http://getsatisfaction.com/chesscube/... and http://getsatisfaction.com/chesscube/...

Disconnecting from games
Description: Users get disconnected from the server and cannot make it back into games they were playing in time
Possible solution: No solution for now; if you have a choice over a wired versus wireless connection, connecting to the wired connection will likely result in less packet loss, and a more stable connection (at least from your side)

Games not starting
Description: Sometimes games take too long to initialize and then error out.
Possible solution: log on again, this could be a temporary problem

Research not showing my recent games
Description: Games research does not have users recent games and was last updated in March.
Possible solution: No solution for now; we have all of the games stored, just have not uploaded them. They should all be uploaded by the next build.

Display issues
Description: Users are missing sections of screen, buttons, have inconvenient scroll bars,
Possible solution: See: http://getsatisfaction.com/chesscube/...

Latency meter missing
Description: Users used to see a latency meter from every chat room, this can now only be seen in a game.
Possible solution: Start a game and scroll over the coloured bar to the right of your name in the game window. We removed the latency bar in the chat rooms because the game servers are now totally different servers from the chat servers and the two latency readings (games versus chat) are now very different, and would be confusing to users. To avoid this confusion, we opted for the game latency readings (where latency matters more). We will be thinking of ways to bring back a latency meter into chat.

Losing when it is not your move
Description: Sometimes either your opponent appears to lose on time or you get an “opponent has disconnected” message, and you still lose rating points.
Possible solution: Users will have to wait for a future build. Basically, the server (and your opponent) thinks it is your turn to move, because your opponent has moved and you never received the move, and then you lose on time for not moving. We are working one ways to ensure moves are received.

Special characters and keyboards not supported
Description: Users can’t use Russian Cyrillic (for example) or German keyboards.
Possible solution: Users will have to wait for a future build.

960 Castling bug
Description: Happens very rarely (twice reported, but maybe more have seen it): after castling, one rook disappears and a bishop is moved.
Possible solution: If you see this, ask your opponent for a takeback, then try to castle again or do a different move, or just abort. Also see: http://getsatisfaction.com/chesscube/...