Unfortunately this does not work for me using Arena. I installed it via copying version 0.8.2 with which I had no problem. Now after each book move it restarts then does not move.
Once I had the same problem with Eubos and the author (Chris Bolt) fixed it.
Unfortunately this does not work for me using Arena. I installed it via copying version 0.8.2 with which I had no problem. Now after each book move it restarts then does not move.
Once I had the same problem with Eubos and the author (Chris Bolt) fixed it.
Unfortunately this does not work for me using Arena. I installed it via copying version 0.8.2 with which I had no problem. Now after each book move it restarts then does not move.
Once I had the same problem with Eubos and the author (Chris Bolt) fixed it.
Nope, the author wants to remain anonymous (= no entry in the chronology).
See my issue #1 at github, because I was following it (and Lunatic) already for months.
Nope, the author wants to remain anonymous (= no entry in the chronology).
See my issue #1 at github, because I was following it (and Lunatic) already for months.
Thanks. I'm going to treat it as a private engine then.
Hi Yves, the repo compiles into Belofte 2.1.6 (u). I guess that is not the same as 2.1.5.
Hi Gabor,
It is almost the same, except for the version number. I actually made 3 distinct errors. 1) I merged the belofte-next into the master branch, 2) I gave the wrong comment (version bump to 2.1.5 instead of 2.1.6), 3) I deleted the next branch....
You can get the release by checking out the release-2.1.5 tag but you can just continue to use the 2.1.6 version. It should be exactly the same as 2.1.5 except for the version number and some updated version references in the documentation and test scripts.
Question, I compiled the windows 64 binaries with gcc 11.2.1 and published it in the files section. Except if you use clang 12 or up, it should be a pretty fast release. How is your compile running with the --bench parameter compared to my published exe?
ydebilloez wrote: ↑Tue Dec 28, 2021 5:52 pmQuestion, I compiled the windows 64 binaries with gcc 11.2.1 and published it in the files section. Except if you use clang 12 or up, it should be a pretty fast release. How is your compile running with the --bench parameter compared to my published exe?
Your 2.1.5(u): bench Perft Time: 2.982 Nodes: 8470712 Total N.: 8870156 NPS: 2973887
My 2.1.6(u): bench Perft Time: 2.976 Nodes: 8470712 Total N.: 8870156 NPS: 2980059
So practically the same. BTW, I use gcc 11.2.0.
If you'd like to continue this discussion please open a dedicated thread so as not to pollute this one.