Open tpoppins opened 5 years ago
Another example: RataAerospacial 0.2.1 (link).
Cute Chess 1.1.0 (master as of July 8) shows this on startup:
<RataAeroespacial 0.2.1(1): feature myname="RataAeroespacial-0.2.1"
>RataAeroespacial 0.2.1(1): accepted myname
<RataAeroespacial 0.2.1(1): feature sigint=0 sigterm=0 setboard=1 ping=1 san=0 colors=0 variants="normal,fischerandom" done=1
>RataAeroespacial 0.2.1(1): rejected sigint
>RataAeroespacial 0.2.1(1): rejected sigterm
>RataAeroespacial 0.2.1(1): accepted setboard
>RataAeroespacial 0.2.1(1): accepted ping
>RataAeroespacial 0.2.1(1): accepted san
>RataAeroespacial 0.2.1(1): rejected colors
>RataAeroespacial 0.2.1(1): accepted variants
>RataAeroespacial 0.2.1(1): accepted done
Current master (as of Jan 18) shows nothing at all, although for a split second while the new game tab is opening something appears to flash in the debug log dock window.
I just built master dated July 8 (v1.1.0) and got the same problem. The only difference between the archived v1.1.0 exec used in the previous post and this new one is QT version. The archived exec shows "5.10.1" and the new one "5.12.2".
Looks like current code needs to be corrected to work with the latest QT packages.
Possibly we have two problems here, one with new versions of Qt, and one as described in #142
No, this one is a separate issue. The exec built with QT 5.10.1 shows a lot more of the log info than that one built with later QT versions, although some info from the very beginning is still missing occasionally (which is #142), esp. with concurrency>1.
This is what I meant.
With reference to http://talkchess.com/forum3/viewtopic.php?f=2&t=66430&p=797169#p797169
They either ran out of chess variants to add or consider CC already good enough not to need any more changes.
I already have five variants in (quasi) PR-ready state for more than a year. And at least five additional far-evolved variant implementations. So no shortage of variants.
Personally I do think CuteChess will improve further on. My own list of topics (only overlapping in part with the issues listed in this repository) comprises of 40 items, and (only/after all) 10 have been solved and added to the project. I guess the half-value time for solution of the topics on my list is about 2 to 3 years, and 3 to 5 years for the cutechess issue list. This goes under the assumption that the contributors and maintainers are able(!) to sustain the average effort of the last (about 5) years.
Well, if it comes to worst, it shouldn't be too hard to sustain the average effort of the past three months at least.
You cannot see our local repositories, can you?
No, but I can see something tall and sleek, towering beyond the clouds, imposing and aloof, gleaming in the sunlight. It it ivory?
Nah, this does not help - invoking images of slaughtered elephants.
For my part i can't actually complain much really. Majority of my suggestion and few variants have already been implemented into the GUI and i'm very happy about that. Thanks to alwey and ilaripih. I tend to check github if any recent cutechess patches is made. Unfortunately not many the last months. I bet alwey and ilaripih have been quite busy lately.
Example exec: SF10 (stockfish_10_x64_popcnt.exe) New Game -> SF10 plays Black
If SF10 is set up to run via the InBetween adapter CC displays the entire initialization sequence:
CC debug log when SF10 is run directly:
A lot of information is missing from the debug log when the engine is run directly -- everything from "id name" till "isready".