Closed fonkap closed 7 years ago
This is in fact expected behavior. In timed games texel does not spend time on things that do not improve its winning chances. It is possible (but unlikely) that looking up a very long PV in the tablebases could make texel lose on time in very fast games.
Thanks for your response Peter, I agree with you but there is yet somthing I don't fully understand. If you want just the strongest move, you could simply set MultiPV = 1 or AnalyseMode = false, am I missing something?
I'm not sure I understand your question, but a chess GUI will typically set MultiPV = 1 and AnalyseMode = false when playing a game, which in texel's case causes the TB PV lookup to be disabled.
Sorry it is my fault, I wrote the issue some time ago and I mixed my mind... Now I understand your first response, I think this issue is fully answered and can be closed. Thank you :)
But if you use instead go depth, full pv is printed. Is this the expected behaviour? I am using Texel 1.06
Minimal example (only kqkr.gtb.cp4 is needed):
using movetime
using depth
Thanks in advance.