Greg Strong wrote on Sun, Jul 7, 2019 07:32 PM UTC:
I have had some more time to test. This is a really an excellent CwDA engine. I think I have found another bug though. In one game, it insisted ChessV made an illegal move when the move was fine. In that game, ChessV was white playing the nutters and KS was black playing the rookies. KS promoted a pawn on g1 and chose to promote to a colonel. ChessV then moved the king to g4 and KS called this an illegal move, presumably thinking that its colonel on g1 attacked it.
So I think the issue is that when KS plays black and promotes a pawn to a piece from white's army, it thinks that the piece moves "forward" as a white piece instead of as a black piece.
Also, good catch about the memory usage. ChessV does not yet offer an xboard engine's configuration options but as a stop-gap I have added settings for the generic "memory" and "cores" options and it will supply them to xboard engines that support those featuers.
I have had some more time to test. This is a really an excellent CwDA engine. I think I have found another bug though. In one game, it insisted ChessV made an illegal move when the move was fine. In that game, ChessV was white playing the nutters and KS was black playing the rookies. KS promoted a pawn on g1 and chose to promote to a colonel. ChessV then moved the king to g4 and KS called this an illegal move, presumably thinking that its colonel on g1 attacked it.
So I think the issue is that when KS plays black and promotes a pawn to a piece from white's army, it thinks that the piece moves "forward" as a white piece instead of as a black piece.
Also, good catch about the memory usage. ChessV does not yet offer an xboard engine's configuration options but as a stop-gap I have added settings for the generic "memory" and "cores" options and it will supply them to xboard engines that support those featuers.