@Thomastpetzke wrote:Hi,
have you tried to disable the transposition table. If the research gets confused it might encounter some rubbish there.
Thomas...
Good idea.
Transposition tables in context with mates scores are
always worth a _first_ look. Especially the relative mate score computation.
@Matthew
Another thing should be to localize where the "phantom" occures in the
search for the first time, maybe identified by nodecount or hashcode.
Many things can be spotted following the search, like buggy mate distance
pruning, wrong initialization of data and so on, and just following with the
debugger, if you know where to start.
If you catch a return value, you have to identify the successor of course, and start debugging from there.
The harder the bug is too find, the more important it gets to switch
of complete code parts, like Thomas mentioned already with the TT.
A simple point to check is of course if you are always returning valid scores in the search, and not an uninitialized best Value maybe, which will be returned because all moves are pruned somehow.
Better, have a closer look at bestValue handling immediatelly.
Just my 2 cents, hopefully it guides you in the right direction.
Michael