To avoid engines creating log files in many different directories, I recommend starting engines in the directory of the Scid User files (this is where the scid.exe file is located on Windows, or ~/.scid/ on Unix) there is a button in the dialog box for editing engine details marked scid.exe dir on Windows or ~/.scid on Unix that lets you set the engine to start in this directory. So if an engine that should work fine in Scid does not start, try changing its directory setting. If the directory setting for an engine is ".", Scid will just start the engine in the current directory. Other engines (like Crafty) write log files to the directory they start in, so you will need to run them in a directory where you have write access. Some engines require an initialization or opening book file in their start directory to run properly. The most likely cause of engine starting problems is the choice of which directory the engine should run in. Engine commands and directoriesįor each engine, you must specify the executable file to run and which directory Scid should run it in. Select the New or Edit buttons to add a new engine to the list or edit the details for an existing entry. You can sort the engine list by name, Elo rating, or date. SCID maintains a list of the engines you have used, along with an estimated Elo rating (if you guess one additionally some pages on the Internet offer these values as results from large engine-engine tournaments) and the date when each engine was last used.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |