Notable Changes

The actual thinking time and the number of simuration are now displayed in the status bar at the bottom right of the window.
KataGo now works correctly even if it returns a query response with zero data.
When the KataGo interface is threaded, it no longer sends stop-think queries when KataGo is not thinking.
If your KataGo interface is threaded, you will now receive KataGo query responses in less time.
Thinking time and number of trials can now be obtained for development and testing.

Constraint

For KataGo engine, the first boot after installation may take several minutes.
In the case of KataGo engine, the first step after installation may take more than 10 seconds.
When building from source files with cmake, add -DUSE_GPU=1 to the cmake command arguments to specify GPU usage.
You may need to install zlib1g-dev when using Linux released deb files.
In the case of the Leela engine, the rules of Go are fixed to the Chinese rules. The KataGo engine defaults to Japanese rules. Specify {"rules":"chinese", "whiteHandicapBonus":"N"} in LeelaGUI.ini(or LeelaGUI_OpenCL.ini) to change Japanese rules of KataGo engine. Any rule supported by KataGo can be specified.
Specifying a maximum engine level other than unlimited in the KataGo engine may cause more delays in situations where the time limit specified is large.
Even if Pondering is specified in the settings dialog, this will only work for new games with unlimited maximum engine level. It doesn't work if you don't specify rate game or maximum engine level as unlimited.
The following items are managed independently by Leela engine and KataGo engine.
- Pondering in the settings dialog
- Time for game in the New Game... dialog
- Byo time in the New Game... dialog
- Engine max level in the New Game... dialog