TalkChess.com

That's correct. The Android version of K8 which was shipped with the desktop version will only work on 32-bit ARM devices running KitKat. The version in the Play Store is available for all available platforms (incl. 64-bit) and runs on modern versions of Android (and contains bugfixes which weren't ...

I know you refuse to admit error and won't back down, so I won't argue with you. I'll leave it to you to justify your implementation against the protocol's specification: * hashfull <x> the hash is x permill full, the engine should send this info regularly How does your arbitrary usefulness test in ...

Reporting the entries accessed during the current search and the one directly preceding it, as I described, would have neither of these problems. It won't go to 0, and it won't converge to 100 by indefinite accumulation. That may be so, but I wouldn't hazard to describe that as a reasonable interpr...

But resetting it between moves will make it peg at 0 once the hash is filled. So it's a no-win situation.

Ray, I would think the solution is to limit the windows file system cache. See https://support.microsoft.com/en-us/kb/976618 *** Snipped from the link above *** To work around this issue, use the GetSystemFileCacheSize API function and the SetSystemFileCacheSize API function to set the maximum or m...

Yes, that's a direct result of Mark and Larry's mad mojo.

I really don't think so, I am not aware of other top engines which clear the hash every time they receive a new position. If you examine Stockfish's code, for instance, you'll see that it only clears on 'ucinewgame', when the hash table is resized, or when 'setoption name Clear Hash' is received. Je...

Both SCID-vs-PC and Arena 3.5 show (incorrectly?) that Komodo 9 does not clear hash between moves. The % of hash used continues to grow with each move in a game. Is that what is actually happening or are the two GUIs just not able to accurately report Komodo 9 hash table usage? The Komodo 9 behavio...

It's an Arena "bug". It shows the same for Houdini 4, as well, which also uses #1000.

The TB win/loss scores remain +-#1000 for root TB positions (8/k7/8/4Kn2/8/P7/8/1n6 b - - 0 1 with 5-man bases and 50-move rule disabled, for instance). For positions which involve TB WL hits during search (more pieces than N-man bases), +-250.00 is returned. Looks like the README is incorrect and n...