Testing shows that using the LittleBlitzer GUI and the same book as used by LS list, the bugfix tested as +2.5 elo over the initial release after 4000 bullet games. Using our own huge private book it was just +1 elo after about 18,000 games. Neither result is near the margin of error, but they seem about right to me for the fix. More important, no more time forfeits!mjlef wrote:I am pleased to announce a revised version of Komodo-TCEC, which we call Komodo-TCECr. It fixes the reported error in fen diagrams followed by castling moves. It also fixes a minor issue of an error message when uses run Komodo in a Windows cmd window and close it using the title bar X instead of using the “quit” command.
Komodo TCEC owners can log into account on the Komodochess.com site (http://komodochess.com/store/secure/log ... /index.php) to download the revised version.
Note that users running matches using “Little Blitzer” will want to get the download, since Little Blitzer apparently converts PGNs to fens during match play. Since the error disallowed castling after many fen positions, Komodo might not find the castling move after a fen, which could hurt play on testers using fens. This is fixed in the TCECr version.
Thanks again for reporting the bug. We want Komodo to be rock solid and really appreciate it when you let us know about problems so we can fix them quickly.
I wish to thank Jeremy Bernstein for making the Windows X close patch.
Mark
If anyone knows of any GUI other than LittleBlitzer in which the initial release was time-forfeiting in engine matches (I'm not talking about server play, that's a whole different problem) please let us know here, so we can post a warning for those who use those GUIs to get the bugfix.
Testers who were using LittleBlitzer or any GUI that was showing time forfeits should retest; for others thaere is no need to do so.