-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About the display method when switching engines #785
Comments
Without a rework and adding additional fields for aliases to different engine settings (it would involve saving alias, manu item layout arrangement, even submenus), the easiest way to tell the difference as a temporary fix is to change the |
commit 8bf2209 Author: Hiraoka <[email protected]> Date: Mon Oct 19 21:32:00 2020 +0900 fixup commit 33cb711 Author: Hiraoka <[email protected]> Date: Sun Oct 18 00:05:28 2020 +0900 fixup commit bf96dcc Author: Hiraoka <[email protected]> Date: Sat Oct 17 23:55:27 2020 +0900 Quick hack to support featurecat#785 (<nickname> before the engine command)
You can see the name of the weight file in the pull-down menu on the top menu to switch engines.
When the same weight file "KataGo40b" is used with different engines, KataGo-v1.6.1-OpenCL and KataGo-v1.6.1-CUDA, the pull-down menu shows exactly the same name, "KataGo40b", which is very difficult to distinguish. It is.
It's possible to have two files that are identical and have different filenames, like "KataGo40b-1.6.1-OpenCL" and "KataGo40b-1.6.1-CUDA", but that's a bit tricky.
It would be useful if you decide on an arbitrary nickname that is easy to understand and the nickname appears in the pull-down menu.
Sabaki uses this technique, and I find it useful.
The text was updated successfully, but these errors were encountered: