1. Set the transposition table size to a maximum of 2048 MB (and enforce this, obviously)
2. Fix a few "usize" types to "u64" ("usize" is 32-bit on a 32-bit system, 64-bit on a 64-bit system)
3. Point 2 also fixed an integer wrap-around in the TT percentage used calculation.
Overnight, I'm going to run a match between Alpha 2 64-bit and 32-bit. If everything is OK (= no crashes), I'll make a release tomorrow evening.
I forgot to subtract an overhead from the move time per second. At some point the GUI would realize that the move comes in late (maybe only 0.01 seconds) and forfeit the game. In MoveTime mode, Rustic Alpha 1 was losing all of its games against Belofte 2.1.0. I've decided to also include this fix into Alpha 1. This version, Alpha 1.1, is now playing a 200 game match against Belofte 2.1.0, and after 21 games, it is up 21 - 0, instead of down 0 - 21. The problem seems to be fixed.ydebilloez wrote: ↑Sat Feb 27, 2021 4:21 am Time control in Rustic alpha seems to be problematic if selecting st=5 in cutechess. (5 seconds per move).
Cutechess-cli is very strict and a few ms passed the allotted time causes a timeout.
Will this get fixed in next release or even in a patch release on alpha?
Engines just don't take this mode into account for testing, apparently. (I didn't, either.), I tested 3 other engines (Clueless, Fractal, and Pulse) and they all lose games on time in MoveTime mode.
So, if there are no issues in the overnight matches, I'll be creating an Alpha 1.1 and Alpha 2 release tomorrow.