Re: Sedat Canbaz
Posted: Tue Nov 12, 2024 9:37 pm
Hi. I use cutechess 1.2 portable version for years, it's working fine on my AMD (windows 7) and on my Ryzen (windows 10). For your tournaments, do you use batch command file, or you writing commands manually (via the GUI)? I'm doing everything manually, batch file didn't work for me because I'm missing some .dll files, plus it taking too long to write every engine's names, paths to books & syzygy etc. In your case I think it's a GUI's bug.Sedat Canbaz wrote: ↑Tue Nov 12, 2024 11:37 am
Hello Aleks,
1st of all,
Thanks for pointing this out...
Btw, can you inform Me please,
Which Cutechess GUI ver do you use?
And that's true...I am aware..even if settings are at 30s+0.5s
On my system, Cutechess records all Bullet games at 30 sec
Only if running at Blitz, such as 2m+1s then its records as it is
[TimeControl "120+1"]
I wonder, is this can be as a GUI bug on my system or..?!
Because I used several different Cutechess GUI vers and
And each time this issue happens..sure I refer if Bullet
But if Blitz, Rapid etc it is all right ! no any issue !!
E.g for references you can checl at Rapid 15m+3s:
https://sites.google.com/site/computers ... s-sf-pb-sc
For Blitz (2m+1s), where you will see again is all right:
https://sites.google.com/site/computers ... k-nn-cs-26
But anyhow, be aware also of that
I am sure that all latest games played with increment (30sec+0.5sec)!
But I agree here and very strange that games are recorded at 30sec
https://sites.google.com/site/computers ... k-nn-cs-37
One thing more,
I prefer Cutechess v1.2.0, since on newer beta versions,
Many of the SF-based engines forfeits on time, but under
Cutechess 1.2.0, it is stable e.g no games lost on time !
But this is also true, you will never know until you try,
Sure I refer running tours on my tournament machine!
Greetings
Regarding your tests with increment 1 sec or more, everything is fine. Often times, engine's losses (by time forfeit) are caused by the lack of increments, it's normal for cutechess, I had same problem in the beginning.