phhnguyen wrote: ↑Wed Nov 30, 2022 12:42 am
Could you post the image of the Adjudication setup dialog (click on the button "setup" next to the text "Adjudication" on your above image)? I am wondering if it is the cause, especially the online adjudication.
Could you do a quick test with that feature off (you may turn off openings, games/logs too)?
Thanks again
I have retested with online adjudication off and there were no instances of this happening. It was a quick 50 game tournament between Senpai 1.0 and 2.0 and it ended fine. I checked the game log and a few did terminate with egtb (local). Same test with online adjudication with either ChessDb or LiChess and yes, when there are only a few pieces on the board, this will happen.
phhnguyen wrote: ↑Wed Nov 30, 2022 12:42 am
Could you post the image of the Adjudication setup dialog (click on the button "setup" next to the text "Adjudication" on your above image)? I am wondering if it is the cause, especially the online adjudication.
Could you do a quick test with that feature off (you may turn off openings, games/logs too)?
Thanks again
I have retested with online adjudication off and there were no instances of this happening. It was a quick 50 game tournament between Senpai 1.0 and 2.0 and it ended fine. I checked the game log and a few did terminate with egtb (local). Same test with online adjudication with either ChessDb or LiChess and yes, when there are only a few pieces on the board, this will happen.
phhnguyen wrote: ↑Wed Nov 30, 2022 12:42 am
Could you post the image of the Adjudication setup dialog (click on the button "setup" next to the text "Adjudication" on your above image)? I am wondering if it is the cause, especially the online adjudication.
Could you do a quick test with that feature off (you may turn off openings, games/logs too)?
Thanks again
I have retested with online adjudication off and there were no instances of this happening. It was a quick 50 game tournament between Senpai 1.0 and 2.0 and it ended fine. I checked the game log and a few did terminate with egtb (local). Same test with online adjudication with either ChessDb or LiChess and yes, when there are only a few pieces on the board, this will happen.
Thanks for the help.
There is a bug in the code for checking timeout when the server does not return results. Fixed for the next release!
https://banksiagui.com
The most features chess GUI, based on opensource Banksia - the chess tournament manager
Wilhelm wrote: ↑Sun Dec 04, 2022 1:20 am
Has anyone a backup of the older v0.54 and v0.55 versions? I deleted them by mistake and the 0.56 doesn't work correct. Please help me. Thank you!
Wilhelm wrote: ↑Sun Dec 04, 2022 1:20 am
Has anyone a backup of the older v0.54 and v0.55 versions? I deleted them by mistake and the 0.56 doesn't work correct. Please help me. Thank you!
Can you tell me what is wrong with 0.56? Thanks!
Note that there is 0.56d (4th release of 0.56), fixed almost all known bugs. Please try if you have not got it.
https://banksiagui.com
The most features chess GUI, based on opensource Banksia - the chess tournament manager
I am confused by those 'mode' captions. Can't they be omitted? Or does 'resign by engine scores' not simply mean resign by engine scores is switched on?
Gabor Szots wrote: ↑Sun Dec 04, 2022 9:49 am
I am confused by those 'mode' captions. Can't they be omitted? Or does 'resign by engine scores' not simply mean resign by engine scores is switched on?
They are just "switches" to turn on/off those features. I don't know which better words should I use for them since I am confused in English too
Perhaps omitting them as your suggestion is better (or any other suggestion)?
https://banksiagui.com
The most features chess GUI, based on opensource Banksia - the chess tournament manager
Wilhelm wrote: ↑Sun Dec 04, 2022 1:20 am
Has anyone a backup of the older v0.54 and v0.55 versions? I deleted them by mistake and the 0.56 doesn't work correct. Please help me. Thank you!
Can you tell me what is wrong with 0.56? Thanks!
Note that there is 0.56d (4th release of 0.56), fixed almost all known bugs. Please try if you have not got it.
Using test positions gives wrong results: using 15sec move time gives an average correct elapse of 27sec?? with Zappa Mexico II as an example (WM-test100).
Chessmaster 10000 with wb2uci adapter doesn't run correct (no or low CPU usage).
Useing standard time control is removed so the time influence of the engine time management couldn't be testet anymore.
GUI crashes often to dektop when aborting a test run and change the enigine or testsuite.
Engine doesn't shut down in tournament (Arasan), regardless what is checked. Happend two times in four test runs.
Many thanks!