As pointed out elsewhere I noticed the buggy behaviour of Arena randomly changing the configured hash table size.
After I stopped the tournament and looked at the uci settings of the 2 engines that were playing (Rubichess and Ethereal) I could not believe my eyes. Total garbage.
90% of coding is debugging, the other 10% is writing bugs.
Rebel wrote: ↑Fri Sep 03, 2021 9:39 am
As pointed out elsewhere I noticed the buggy behaviour of Arena randomly changing the configured hash table size.
After I stopped the tournament and looked at the uci settings of the 2 engines that were playing (Rubichess and Ethereal) I could not believe my eyes. Total garbage.
I always adjusted the hash in the Engine Management window (always for UCI engines & sometimes for WB engines-here I prefer the initialization files). And it works absolutely perfectly. For decades.
Did some further tests. It seems that playing pure eng-eng matches Arena 3.0 performs as expected, it keeps the 4Gb hash and after aborting the tournament the uci configurations of both engines are OK.
However as soon as you add a third engine to a (gauntlet or robin) tournament the trouble starts, Arena changing hash table sizes of engines and showing corrupt uci configurations.
90% of coding is debugging, the other 10% is writing bugs.
Rebel wrote: ↑Fri Sep 03, 2021 9:39 am
As pointed out elsewhere I noticed the buggy behaviour of Arena randomly changing the configured hash table size.
After I stopped the tournament and looked at the uci settings of the 2 engines that were playing (Rubichess and Ethereal) I could not believe my eyes. Total garbage.
I always adjusted the hash in the Engine Management window (always for UCI engines & sometimes for WB engines-here I prefer the initialization files). And it works absolutely perfectly. For decades.
Try a tournament with more than 2 engines.
90% of coding is debugging, the other 10% is writing bugs.