Go to Settings -> Move, and select None for Computing info

Moderator: Ras
Go to Settings -> Move, and select None for Computing info
criko wrote: ↑Sun Nov 27, 2022 2:45 pm Unusable ouput
[Event "4m2s 001"]
[Date "2022.11.27"]
[Round "3"]
[White "A"]
[Black "B"]
[Result "1/2-1/2"]
[TimeControl "240+2"]
[Time "14:15:43"]
[Board "30"]
[Termination "repetition"]
[FEN "rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 2"]
[SetUp "1"]
[ECO "D31"]
[Opening "QGD"]
1. 2.
3. 4. {D31: QGD, semi-Slav}
5. 6.
7. 8. {End of opening}
9.Bxc4 {+0.03/31 16112 12935575} b5 {+0.24/37 10 2} 10.Bb3 {+0.08/34 8045 7443442} Kh8 {+0.31/36 10 1}
11.e4 {+0.03/32 7303 6610220} e5 {+0.09/35 10 1} 12.Bg5 {+0.08/31 7743 6943357} a5 {+0.16/37 10 1}
13.exf5 {+0.08/30 5840 5274343} Qe7 {+0.34/34 10 1} 14.O-O {+0.07/30 5581 5201681} a4 {+0.12/33 10 1}
15.Be6 {+0.08/32 6010 5708417} Bxe6 {+0.15/34 10 1} 16.fxe6 {+0.05/33 13482 12159766} Qxe6 {+0.19/33 10 1}
17.Rae1 {+0.03/33 14538 13398326} Nbd7 {+0.13/26 5966 5115768} 18.Ng3 {+0.03/33 3719 3681881} Qc4 {+0.00/32 5971 3990799}
19.b3 {+0.00/35 6679 6263298} Qxd4+ {+0.02/31 6581 5470676} 20.Be3 {+0.02/33 7177 6870322} axb3 {+0.00/32 6663 5820389}
21.axb3 {+0.00/33 4772 4213032} Qb4 {+0.07/33 7379 6406745} 22.Nce4 {+0.00/35 7688 6794540} Nxe4 {+0.06/35 5968 5259133}
23.Nxe4 {+0.00/37 5862 5185788} Be7 {+0.00/40 8381 6761424} 24.Qxc6 {+0.00/41 11552 9562124} Nf6 {+0.00/40 16414 12532383}
25.Nxf6 {+0.00/41 12526 11793080} Rac8 {+0.00/37 7079 5606592} 26.Qe4 {+0.00/41 11253 9684239} gxf6 {+0.00/38 11618 7826717}
27.Qb7 {+0.00/43 9978 8533126} Rb8 {+0.00/41 7190 5023286} 28.Qa7 {+0.00/40 9971 8494510} Ra8 {+0.00/39 8015 6143798}
29.Qb7 {+0.00/43 9816 8870593} Rab8 {+0.00/41 13539 10971304} 30.Qa7 {+0.00/45 5831 4590058} Ra8 {+0.00/45 7119 5854830}
31.Qb7 {+0.00/47 7020 6427984} Rab8 {+0.00/49 6166 5298660} 1/2-1/2
This version (0.56) started supporting viewing variations only. Wait for me for the next version (not today's sub-version) for having more features/functions with variations.
I can't reproduce the bug even after running a lot of tests/games, with and without the engine you mentioned. BTW, I have checked and improved some code in the hope it could fix some potential bugs. Please download today's version and help us to test it. Thanksadnoh wrote: ↑Mon Nov 28, 2022 5:27 pm I am having a new problem with 0.56c.
In engine matches one engine would simply run past its time allocation and it never stops running. This did not happen with 0.55 and prior versions as sometime engines do timeout and Banksia will catch that but here it just runs forever until I manually stop it. I have tried a few engines and all seem to eventually happen.
In the following example it is Senpai 1.0 that has run on.
![]()
I have tried it with 0.56d but still the same problem. These are the time control I am using in case that is related. I will do more testing on my own with various tournament settings to see if I can isolate it. Thanks for the Chess GUI,phhnguyen wrote: ↑Tue Nov 29, 2022 10:01 amI can't reproduce the bug even after running a lot of tests/games, with and without the engine you mentioned. BTW, I have checked and improved some code in the hope it could fix some potential bugs. Please download today's version and help us to test it. Thanksadnoh wrote: ↑Mon Nov 28, 2022 5:27 pm I am having a new problem with 0.56c.
In engine matches one engine would simply run past its time allocation and it never stops running. This did not happen with 0.55 and prior versions as sometime engines do timeout and Banksia will catch that but here it just runs forever until I manually stop it. I have tried a few engines and all seem to eventually happen.
In the following example it is Senpai 1.0 that has run on.
![]()
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.
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