Banksia GUI released

[CMCanavessi]

...

Well, I just wanted to test without the info string to see if that fixed the problem. If it indeed was fixed, then we know for sure that THAT was the problem, and then we can discuss if it was banksia's fault or minic's and how to move forward.

[CMCanavessi]

Well, I have found another engine that behaves like Minic (that is, sending info strings after the stop command and before the "bestmove"), so I would advice to make Banksia adjust to that and fix this (regardless of what the protocol says), because I've so far found only 2 engines (Minic and Vajolet), but there may be many more.

Here's a log for Vajolet that shows the same behaviour:

Code: Select all

1.13:29:33 Vajolet2 2.8.0> bestmove d8c6 ponder g2g3
1.13:29:33 Vajolet2 2.8.0< position fen rnknrbbq/pppppppp/8/8/8/8/PPPPPPPP/RNKNRBBQ w EAea - 0 1 moves h2h4 f7f5 e2e4 f5e4 e1e4 e7e5 f2f4 b8c6 b1c3 g8f7 f4e5 f7g6 e4e1 h7h5 d1e3 c6e5 c1a1 d8c6 g2g3
1.13:29:33 Vajolet2 2.8.0< go ponder wtime 50614 btime 41163 winc 1000 binc 1000
1.13:29:33 Senpai 2.0< ponderhit
1.13:29:33 Senpai 2.0> info depth 18 seldepth 29 nodes 1577984 time 2170 nps 727137
1.13:29:33 Senpai 2.0> bestmove e3d5 ponder h8h7
1.13:29:33 Senpai 2.0< position fen rnknrbbq/pppppppp/8/8/8/8/PPPPPPPP/RNKNRBBQ w EAea - 0 1 moves h2h4 f7f5 e2e4 f5e4 e1e4 e7e5 f2f4 b8c6 b1c3 g8f7 f4e5 f7g6 e4e1 h7h5 d1e3 c6e5 c1a1 d8c6 e3d5 h8h7
1.13:29:33 Senpai 2.0< go ponder wtime 50604 btime 42163 winc 1000 binc 1000
1.13:29:33 Vajolet2 2.8.0< stop
1.13:29:33 Senpai 2.0> info depth 1 score cp 55 nodes 165 pv d2d3
1.13:29:33 Senpai 2.0> info depth 2 score cp 55 nodes 179 pv d2d3 g6f7
1.13:29:33 Senpai 2.0> info depth 3 score cp 55 nodes 216 pv d2d3 g6f7 a2a3
1.13:29:33 Senpai 2.0> info depth 4 seldepth 6 score cp 55 nodes 312 pv d2d3 g6f7 a2a3 c8a8
1.13:29:33 Senpai 2.0> info depth 5 seldepth 10 score cp 55 nodes 478 pv d2d3 g6f7 a2a3 c8a8 c1b1
1.13:29:33 Senpai 2.0> info depth 6 seldepth 10 score cp 55 nodes 712 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6
1.13:29:33 Senpai 2.0> info depth 7 seldepth 10 score cp 55 nodes 1022 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3
1.13:29:33 Senpai 2.0> info depth 8 seldepth 10 score cp 55 nodes 1420 time 1 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4
1.13:29:33 Senpai 2.0> info depth 9 seldepth 13 score cp 53 nodes 2582 time 2 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 f8d6 h1g2
1.13:29:33 Senpai 2.0> info depth 10 seldepth 13 score cp 55 nodes 3939 time 3 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5
1.13:29:33 Senpai 2.0> info depth 11 seldepth 16 score cp 55 nodes 5535 time 4 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2
1.13:29:33 Senpai 2.0> info depth 12 seldepth 17 score cp 55 nodes 7927 time 7 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6
1.13:29:33 Senpai 2.0> info depth 13 seldepth 18 score cp 55 nodes 11555 time 10 nps 1129201 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6 d5f4
1.13:29:33 Senpai 2.0> info depth 14 seldepth 19 score cp 55 nodes 16701 time 16 nps 1043689 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6 d5f4 e5c6
1.13:29:33 Vajolet2 2.8.0> info depth 1
1.13:29:33 Vajolet2 2.8.0> info hashfull 0 tbhits 0 nodes 76 time 0 nps 76000
1.13:29:33 Vajolet2 2.8.0> bestmove 0000 ponder c1b1
1.13:29:33 Senpai 2.0> info depth 15 seldepth 22 score cp 55 nodes 42091 time 52 nps 815276 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6 d5f4 e5c6 c3d5
1.13:29:34 Senpai 2.0> info depth 16 seldepth 20 score cp 55 nodes 71882 time 92 nps 785430 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6 d5f4 e5c6 c3d5 f7d5
1.13:29:34 Senpai 2.0> info depth 17 seldepth 25 score cp 45 upperbound nodes 273907 time 365 nps 749409 pv d2d3 g6f7 a2a3 c8a8 c1b1 a7a6 g2g3 e5g4 h1f3 c6e5 f3g2 h7h6 d5f4 e5c6 d3d4 f8d6 f1d3
1.13:29:34 Senpai 2.0> info depth 17 seldepth 26 currmove d2d3 currmovenumber 1 nodes 735744 time 1000 nps 735639
1.13:29:34 Senpai 2.0> info depth 17 seldepth 26 score cp 53 nodes 758211 time 1028 nps 737490 pv d2d3 g6f7 a2a3 c8a8 c1b1 f8d6 f1e2 a7a6 e1f1 h7g6 d3d4 f7d5 c3d5 e5g4 e2d3 g6e6 f1f5 e6h6
1.13:29:35 Senpai 2.0> info depth 18 seldepth 27 currmove d2d3 currmovenumber 1 nodes 1470720 time 2000 nps 735266
1.13:29:36 Senpai 2.0> info depth 18 seldepth 27 score cp 48 nodes 1555953 time 2115 nps 735841 pv d2d3 g6f7 a2a3 c8a8 c1b1 f8d6 f1e2 a7a6 e1f1 h7g6 d3d4 f7d5 c3d5 e5g4 e2d3 g6e6 f1f5 e6h6 f5g5 c8b8
1.13:29:36 Senpai 2.0> info depth 19 seldepth 28 currmove d2d3 currmovenumber 1 nodes 2234112 time 3000 nps 744659
1.13:29:37 Senpai 2.0> info depth 19 seldepth 28 score cp 46 nodes 2499399 time 3348 nps 746588 pv d2d3 g6f7 a2a3 c8a8 c1b1 f8d6 g2g3 e5g4 h1f3 h7g6 d3d4 e8e1 d1e1 f7d5 c3d5 d8f8 d5f4 d6f4 g3f4 g6d6 d4d5 f8f4 e1e8 c6d8
1.13:29:37 Senpai 2.0> info depth 20 seldepth 28 currmove d2d3 currmovenumber 1 nodes 3032064 time 4000 nps 758003
1.13:29:38 Senpai 2.0> info depth 20 seldepth 28 currmove d2d3 currmovenumber 1 nodes 3726592 time 5000 nps 745286
1.13:29:39 Senpai 2.0> info depth 20 seldepth 28 currmove d2d3 currmovenumber 1 nodes 4406784 time 6000 nps 734420
1.13:29:40 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 5130240 time 7000 nps 732891
1.13:29:41 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 5881088 time 8000 nps 735106
1.13:29:42 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 6585600 time 9000 nps 731708
1.13:29:43 Senpai 2.0> info depth 20 seldepth 34 score cp 56 lowerbound nodes 6911659 time 9430 nps 732980 pv d2d3 g6f7 g1h2 c8a8 d3d4 e5g4 f1d3 h7g8 e1e8 d8e8 d5c7 g4f2 h1g1 f2d1 c1d1 e8e7 d4d5 a7a6 d5c6 d7c6 g1a7 e7c7 a7a8 c8d7 h2c7 d7c7
1.13:29:43 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 7394048 time 10000 nps 739377
1.13:29:44 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 8071168 time 11000 nps 733729
1.13:29:45 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 8737792 time 12000 nps 728143
1.13:29:46 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 9389568 time 13000 nps 722271
1.13:29:47 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 10052608 time 14000 nps 718036
1.13:29:48 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 10717184 time 15000 nps 714470
1.13:29:49 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 11437312 time 16000 nps 714815
1.13:29:50 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 12137728 time 17000 nps 713967
1.13:29:51 Senpai 2.0> info depth 20 seldepth 34 currmove d2d3 currmovenumber 1 nodes 12829440 time 18000 nps 712734
1.13:29:52 Senpai 2.0> info depth 20 seldepth 34 score cp 66 lowerbound nodes 13169836 time 18455 nps 713627 pv d2d3 g6f7 g1h2 c8a8 d3d4 e5g4 f1d3 h7g8 e1e8 d8e8 d5c7 g4f2 h1g1 f2d1 c1d1 e8e7 d4d5 g7g5 d5c6 g5h4 c6d7 e7d7 g1a7 g8g2
1.13:29:52 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 13626624 time 19000 nps 717177
1.13:29:53 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 14335744 time 20000 nps 716779
1.13:29:54 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 14998528 time 21000 nps 714215
1.13:29:55 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 15692800 time 22000 nps 713299
1.13:29:56 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 16434688 time 23000 nps 714548
1.13:29:57 Senpai 2.0> info depth 20 seldepth 37 score cp 36 upperbound nodes 16994679 time 23783 nps 714567 pv d2d3 c8a8 g1h2 f8d6 c1b1 g6f7 d3d4 e5g4 h2d6 c7d6 f1d3 h7g8 e1e8 d8e8 c3e4 f7d5 e4c3
1.13:29:57 Senpai 2.0> info depth 20 seldepth 37 currmove d2d4 currmovenumber 2 nodes 17158144 time 24000 nps 714920
1.13:29:58 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 17954560 time 25000 nps 718175
1.13:29:59 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 18674944 time 26000 nps 718266
1.13:30:00 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 19358464 time 27000 nps 716970
1.13:30:01 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 20034048 time 28000 nps 715493
1.13:30:02 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 20731904 time 29000 nps 714893
1.13:30:03 Vajolet2 2.8.0< isready
1.13:30:03 Vajolet2 2.8.0> readyok
1.13:30:03 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 21394432 time 30000 nps 713146
1.13:30:04 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 22081536 time 31000 nps 712299
1.13:30:05 Senpai 2.0> info depth 20 seldepth 37 currmove d2d3 currmovenumber 1 nodes 22788352 time 32000 nps 712129
1.13:30:05 Senpai 2.0> info depth 20 seldepth 37 score cp 37 nodes 22809731 time 32026 nps 712218 pv d2d3 c8a8 c1b1 a7a6 a2a3 g6f5 f1e2 f8d6 e1f1 f5g4 e2g4 e5g4 h1h3 d6e5 h3f3 h7h6 d3d4 e5d6 f1e1 e8f8 f3e4
1.13:30:06 Senpai 2.0> info depth 21 seldepth 31 currmove d2d3 currmovenumber 1 nodes 23477760 time 33000 nps 711438
1.13:30:07 Senpai 2.0> info depth 21 seldepth 31 currmove d2d3 currmovenumber 1 nodes 24175360 time 34000 nps 711035
1.13:30:08 Senpai 2.0> info depth 21 seldepth 31 currmove d2d3 currmovenumber 1 nodes 24902656 time 35000 nps 711501
1.13:30:09 Senpai 2.0> info depth 21 seldepth 32 currmove d2d3 currmovenumber 1 nodes 25639680 time 36000 nps 712209
1.13:30:10 Senpai 2.0> info depth 21 seldepth 33 currmove d2d3 currmovenumber 1 nodes 26341888 time 37000 nps 711939
1.13:30:11 Senpai 2.0> info depth 21 seldepth 33 score cp 35 nodes 26995765 time 37864 nps 712966 pv d2d3 c8a8 c1b1 a7a6 f1e2 g6f7 g2g3 e5g4 e1f1 h7g6 h1f3 f7g8 d5f4 g6h7 c3d5 h7h6 f3g2 f8d6 e2f3 c6e5 f3e4
1.13:30:11 Senpai 2.0> info depth 21 seldepth 33 currmove d2d4 currmovenumber 2 nodes 27100928 time 38000 nps 713180
1.13:30:12 Senpai 2.0> info depth 22 seldepth 30 currmove d2d3 currmovenumber 1 nodes 27945728 time 39000 nps 716553
1.13:30:13 Senpai 2.0> info depth 22 seldepth 30 currmove d2d3 currmovenumber 1 nodes 28691200 time 40000 nps 717277
1.13:30:14 Senpai 2.0> info depth 22 seldepth 30 currmove d2d3 currmovenumber 1 nodes 29486080 time 41000 nps 719172
1.13:30:15 Senpai 2.0> info depth 22 seldepth 30 currmove d2d3 currmovenumber 1 nodes 30266624 time 42000 nps 720632
1.13:30:16 banksia> Timeleft for Senpai 2.0: 50.60, Vajolet2 2.8.0: 42.16, used: 42.31
1.13:30:16 Senpai 2.0< stop
1.13:30:16 banksia> 1) Senpai 2.0 vs Vajolet2 2.8.0, #19, 1-0 (timeout)
1.13:30:16 Senpai 2.0> info depth 22 seldepth 30 nodes 30506240 time 42306 nps 721083
1.13:30:16 Senpai 2.0> bestmove d2d3 ponder c8a8
1.13:30:18 Vajolet2 2.8.0< quit
1.13:30:18 Senpai 2.0< quit
2.13:30:18 banksia>

Here's the relevant part:

Code: Select all

1.13:29:33 Vajolet2 2.8.0> bestmove d8c6 ponder g2g3
1.13:29:33 Vajolet2 2.8.0< position fen rnknrbbq/pppppppp/8/8/8/8/PPPPPPPP/RNKNRBBQ w EAea - 0 1 moves h2h4 f7f5 e2e4 f5e4 e1e4 e7e5 f2f4 b8c6 b1c3 g8f7 f4e5 f7g6 e4e1 h7h5 d1e3 c6e5 c1a1 d8c6 g2g3
1.13:29:33 Vajolet2 2.8.0< go ponder wtime 50614 btime 41163 winc 1000 binc 1000
1.13:29:33 Senpai 2.0< ponderhit
1.13:29:33 Senpai 2.0> info depth 18 seldepth 29 nodes 1577984 time 2170 nps 727137
1.13:29:33 Senpai 2.0> bestmove e3d5 ponder h8h7
1.13:29:33 Senpai 2.0< position fen rnknrbbq/pppppppp/8/8/8/8/PPPPPPPP/RNKNRBBQ w EAea - 0 1 moves h2h4 f7f5 e2e4 f5e4 e1e4 e7e5 f2f4 b8c6 b1c3 g8f7 f4e5 f7g6 e4e1 h7h5 d1e3 c6e5 c1a1 d8c6 e3d5 h8h7
1.13:29:33 Senpai 2.0< go ponder wtime 50604 btime 42163 winc 1000 binc 1000
1.13:29:33 Vajolet2 2.8.0< stop
.
.
.
1.13:29:33 Vajolet2 2.8.0> info depth 1
1.13:29:33 Vajolet2 2.8.0> info hashfull 0 tbhits 0 nodes 76 time 0 nps 76000
1.13:29:33 Vajolet2 2.8.0> bestmove 0000 ponder c1b1
.
.
.
1.13:30:16 Senpai 2.0< stop
1.13:30:16 banksia> 1) Senpai 2.0 vs Vajolet2 2.8.0, #19, 1-0 (timeout)
1.13:30:16 Senpai 2.0> info depth 22 seldepth 30 nodes 30506240 time 42306 nps 721083
1.13:30:16 Senpai 2.0> bestmove d2d3 ponder c8a8
1.13:30:18 Vajolet2 2.8.0< quit
1.13:30:18 Senpai 2.0< quit
2.13:30:18 banksia>

[phhnguyen]

I have been working on some issues with Minic.

UCI document (http://wbec-ridderkerk.nl/html/UCIProtocol.html) says:

Code: Select all

Move format:
------------

The move format is in long algebraic notation.
A nullmove from the Engine to the GUI should be send as 0000.
Examples:  e2e4, e7e5, e1g1 (white short castling), e7e8q (for promotion)

Thus "bestmove O-O-O" is an illegal move. Minic also uses O-O, O-O-O in PVs too, which is inconsistent with the notation of other moves.

At the moment, BSG detects out illegal moves but just ignores them. In the next release, BSG will add some messages into the engine log then terminate the game immediately with the reason "Illegal move".

I have also been working with "bestmove 0000" which Minic prints out when being stopped because of wrong ponder move. Theory, BSG should work well with that move (accepts and then tells Minic to start computing as usual). Just being struggling to reproduce.

[CMCanavessi]

I have also been working with "bestmove 0000" which Minic prints out when being stopped because of wrong ponder move. Theory, BSG should work well with that move (accepts and then tells Minic to start computing as usual). Just being struggling to reproduce.

I'll just quote this part, because the Minic invalid O-O-O string has already been fixed by the author. Banksia works ok with engines that return "bestmove 0000", I've seen it. I think it's the info strings between the stop command banksia says and the bestmove the engine returns that are the problem. Vajolet2 2.8.0 and Minic 3.10 both have this problem. You can quickly test it by doing a tournament between the 2 engines with ponder on. Vajolet loses on time 7 out of 10 games.

[phhnguyen]

I am in the process of upgrading my Raspberry Pi 4 8GB model with a SSD and a new case. I just installed Ubuntu Mate on it. Then the thought hit me, how difficult would it be to port Banksia over so that it could run on a Arm processor? I am also in the process of installing Picochess on it, so in theory I should be able use all engines created to run on Arm processors in Banksia also if it were ported to Arm. Keep hope alive! This is just a thought, not a request yet ...

That’s doable. Even I was almost going to buy a Raspberry Pi just for testing. However, I postponed that plan later since needed to focus some other tasks, including real life ones. Sure sooner or later I will support directly some ARM hardware (Ras, M1)

Hey buddy, I hope your wife is doing well and feeling better...

Thank you!

I have a bug report:

I have noticed that there is a bug when 1. engines are asked to use a "seconds per move", especially in situations where 2. I am using the multi-time control and giving the human side unlimited time.

I think this bug is more related to the multi-time control feature.

Can you tell me more about that bug? What happen/should we expect?

I have checked but not clear. If that is the timeout of the engine, set the margin to a higher value.

Another feature that would be nice, but also easy to implement, is for the engine's rating to also show up in the exported pgn file. As of now it does not.

Thanks buddy, you're doing excellent work.

Thanks for the idea. It is taken.

[abgursu]

Hi,
I have a bug too and I'm not sure what is causing that. Sometimes when my bot is playing and challenge is on at the same time,(and concurrency is set to 1), GUI actually send the challenge to another bot and if accepted, Banksia GUI crushes till I manually cancel the second game or Lichess automatically cancels the second game. I really checked everything and am sure the bug is Banksia's. I unchecked everything in the accept menu, I manually set "Can other players challenge you?" to never in lichess. Seriously, I have 5 loss and 4 of them is because of time forfeit caused by not-responding Banksia.
I'd be really glad if you can fix this.
Best Regards...

[Eduard]

A lot has gotten much better. We must have patience. For me, the GUI keeps crashing inexplicably during the game or goes offline. However, the game continues on lichess. So that the GUI can go online again, I have to close the browser and then restart the GUI. And then click Go online. If I click on Go online then the GUI crashes again. On average, I have to repeat these steps 5 to 6 times. That sometimes costs bid to 60s time. That's why I play with a high move overhead in order to have a minute more in an emergency.

[phhnguyen]

Version 0.48 beta released

Fixed bugs:
* A crash when turning on/off graphs a few times
* Games of chess 960 tournaments may be truncated when re-loading from files
* Lichess bots can’t remember none-auto timers; they may not obey concurrency number
* Ponder: may not send command “go” to engines after receiving null moves (0000)

Some small improvements/adjustments

New features:
* Lichess bots: auto chat (Fig. 1)
* Graph: a new type line (differ from the previous line-dot); can show all graphs in one panel and all graphs in one space (Fig. 2 & 3)
* Use mouse wheel to scroll moves
* Move list: customizable colours, use figures for pieces (Fig. 4)
* New themes: Dark (Fig. 4), Old paper (Fig. 5), and old magazines
* New safer way to write to JSON files: write to temporary files (.json.tmp) first then rename to main files (.json) when old file renamed to backup ones (.json.bk). That can reduce the risk of being corrupted data because of interruptions when writing
* ECA, tournaments: have multi backups and daily-backup which are fully auto managed/deleted
* Can set two different folders for Syzygy: one for engines, one for GUI’s adjudication
* Some small improvements for ECA: can evaluate internodes (instead of leaf nodes only - the purpose is to create a kind of computing data banks, used for multi-purpose later)


Fig. 1 Libot chat setup. Each message is selected randomly from a list box. That can avoid messages being the same and boring every time, make the chat more natural/humanity


Fig. 2 All graphs are in one panel. That’s not flexible as when they are in separated panels but it is more efficient on space and more tidy


Fig. 3 All graphs share a space. That’s the most compact, save the most space. However, it may look unclear and so complicated. Thus it is suitable only for very small numbers of graphs (e.g., 2). Users may need to try-error to find the best configuration such as the number of graphs, their types, colors, transparency…
Any idea to improve?



Fig. 4 Dark theme


Fig. 5 Old paper theme (designed by Ted Summers)

[AlexChess]

Hi phhnguyen!

Reading the release notes I think that 0.48 still doesn't fix "add new engine"? (Tried with Mac but it says 2000 games added )

No problem, I still have to wait for some new native engines

Thank you,
Statistics are very nice (I will use bars)

Best regards, Alex

[phhnguyen]

Hi phhnguyen!

Reading the release notes I think that 0.48 still doesn't fix "add new engine"? (Tried with Mac but it says 2000 games added )

No problem, I still have to wait for some new native engines

Thank you,
Statistics are very nice (I will use bars)

Best regards, Alex

It’s fixed. However, if you use an old tournament which has been added games and/or removed games/engines before, the engines in the internal list may be not consistent, affect the new number.

You may try with a new tournament to see the difference