joechess wrote:Engine calculates but doesn’t move when starting a game. Anyone else have this problem with Soberango?
I am experiencing a similar issue, when using a sudden death time control or a time control with an increment. Soberango 0.09.2 seems to work fine if I use a time control of x moves in y number of minutes. I am using Arena as my GUI.
In raw command line mode it behaves as follows with 40 moves in 5 minutes:
- either it moves instantly (and reports 1/2-1/2),
- or it thinks for a short while and then makes its move,
- or it thinks quite a while (until depth 6 or 7) but then does not move.
joechess wrote:Engine calculates but doesn’t move when starting a game. Anyone else have this problem with Soberango?
I am experiencing a similar issue, when using a sudden death time control or a time control with an increment. Soberango 0.09.2 seems to work fine if I use a time control of x moves in y number of minutes. I am using Arena as my GUI.
In raw command line mode it behaves as follows with 40 moves in 5 minutes:
- either it moves instantly (and reports 1/2-1/2),
- or it thinks for a short while and then makes its move,
- or it thinks quite a while (until depth 6 or 7) but then does not move.
Sorry, what is a "raw command line mode"?
Use console without any GUI?
I use "level 40 5 0" for example.
joechess wrote:Engine calculates but doesn’t move when starting a game. Anyone else have this problem with Soberango?
I am experiencing a similar issue, when using a sudden death time control or a time control with an increment. Soberango 0.09.2 seems to work fine if I use a time control of x moves in y number of minutes. I am using Arena as my GUI.
I had a same problem with Isa , when Graham tried to test at TC 40/40 , Isa won't move after the book
It's fixed now but need to tune the gestion of the time
joechess wrote:Engine calculates but doesn’t move when starting a game. Anyone else have this problem with Soberango?
I am experiencing a similar issue, when using a sudden death time control or a time control with an increment. Soberango 0.09.2 seems to work fine if I use a time control of x moves in y number of minutes. I am using Arena as my GUI.
In raw command line mode it behaves as follows with 40 moves in 5 minutes:
- either it moves instantly (and reports 1/2-1/2),
- or it thinks for a short while and then makes its move,
- or it thinks quite a while (until depth 6 or 7) but then does not move.
Sorry, what is a "raw command line mode"?
Use console without any GUI?
I use "level 40 5 0" for example.
Simply start the executable. If I enter the following commands:
then I see the behaviour as described above. If the engine does not work correctly in console mode then it is very likely that there is some GUI under which it fails to work as well. I had already reported some clock management issues a long time ago, and I'm pretty sure that there are other WB protocol issues as well that should be fixed
I decided to turn off quiescence search. The level with it is weaker than without it because the loss of speed doing it.
I need to make a faster captures generator before activate QS again.
I decided to turn off quiescence search. The level with it is weaker than without it because the loss of speed doing it.
I need to make a faster captures generator before activate QS again.
it is often better to fix the search algorithm (i.e. its implementation) than to improve the speed. Even if you make the capture move generator 10 times faster so that it does not need, for instance, 10% but only about 1% of the total time, the engine would still play bad chess if the search does not work well.
If you say that your engine plays weaker with QS than without it then this clearly indicates that the implementation is either not correct or causes a search explosion (i.e., move ordering or other search elements might have issues). This is not due to move generation speed, for sure.
