Bug in Chess960 game viewer

Sort:
glider1001
Does anyone know if this bug with Chess960 castling in the game viewer is also in V3 version of the Chess.com game viewer? I can't tell because I am a non-paying member on the old version.
 
Here is a castling test of SP955 with castling on both wings. Take note of black's castling O-O. The king should sit on g8 and rook on f8 but instead the king sits on d8 and rook on c8.
 
 
Thanks
friscodelrosario
It's OK in v.3. 
 
friscodelrosario

Did you remember to include the [Variant "chess960"] tag?

glider1001

Thank you Frisco for your help. Yes if you take a look at the pgn for your version and mine, both have the identical Chess960 tag. Thanks for letting me know that it is fixed in v3.

glider1001

I just noticed that there is a bug in V3 as well. When I look at the FEN for your version Frisco, it does not follow the Chess960 standard.

FEN adjustment for chess variants like Chess960[edit]

FEN is critical for recording games in chess variants such as Chess960 (also known as Fischer Random Chess), where the initial position is not necessarily the traditional initial position. However, the FEN castling availability encoding (KQkq) is inadequate for positions in which there are two Rooks on the same side of the King on the back rank, which should never happen according to the game's rules. It is ambiguous which Rook is still available for castling without knowing their initial positions.

The solution implemented by chess engines like Shredder and Fritz_9 is to use the letters of the columns on which the rooks began the game. This scheme is sometimes called Shredder-FEN.[citation needed] For the traditional setup, Shredder-FEN would use AHah instead of KQkq.

Another solution is offered by X-FEN, which offers more backward compatibility than does Shredder-FEN, but at the cost of more complexity.

https://en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation