user25161: I'm going through the 100 endgames you must know book on Chessable and stumbled upon something I don't understand. This position with white to move is described as a draw starting with 1. Kh1. I figured well why wouldn't 1. Kf1 be a draw and I put the exercise into Lichess analyses, which evaluates the position as -2,5, no matter which move white plays.
Why isn't Stockfish able to evaluate this position as 0.0? It says 'depth 64'. Wouldn't it only need to calculate 50 moves to establish that this is a fortress and thereby a draw?
[FEN "8/8/1n6/8/8/5k1p/7P/6K1 w - - 0 1"]



user825: This is an easy position for Stockfish with tablebase, but very hard without it. The only way Stockfish can work out it's a draw is search all the way through 50-move draw. Otherwise, it'd think the position is winning for Black because Black has a knight up.
Your browser may not have the capability to search such high depth. That's exactly the reason why we need tablebase in high quality analysis.

user924: Depth 64 means 64 half moves, it includes moves both by white and black. It isn't close to being able detect draws by means of the 50 move rule (100 plies). Especially since that is only the depth of the deepest line in the search, and to conclude it was certainly a draw, Stockfish would have to look at a huge number of lines that all eventually draw by the 50 move rule.
Endgame draws like this are notoriously difficult for engines, they have no good way to judge "progress" in their calculations. There are some attempts being tried out but they aren't at the level of Stockfish yet.
This is why tablebases were invented -- huge databases of all positions with up to some number of pieces (7 at the moment I think). They give an immediate answer. This is a five-piece position and a Stockfish configured to use tablebases would immediately know it is a draw.

25161: <p>I'm going through the <em>100 endgames you must know</em> book on Chessable and stumbled upon something I don't understand. This position with white to move is described as a draw starting with 1. Kh1. I figured well why wouldn't 1. Kf1 be a draw and I put the exercise into Lichess analyses, which evaluates the position as -2,5, no matter which move white plays.</p>
<p>Why isn't Stockfish able to evaluate this position as 0.0? It says 'depth 64'. Wouldn't it only need to calculate 50 moves to establish that this is a fortress and thereby a draw?</p>
<pre><code>[FEN &quot;8/8/1n6/8/8/5k1p/7P/6K1 w - - 0 1&quot;]
</code></pre>
<p><a href="https://i.stack.imgur.com/Pcdjk.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Pcdjk.png" alt="enter image description here" /></a></p>
 825: <p>This is an easy position for Stockfish with tablebase, but very hard without it. The only way Stockfish can work out it's a draw is search all the way through 50-move draw. Otherwise, it'd think the position is winning for Black because Black has a knight up.</p>
<p>Your browser may not have the capability to search such high depth. That's exactly the reason why we need tablebase in high quality analysis.</p>
 924: <p>Depth 64 means 64 <em>half moves</em>, it includes moves both by white and black. It isn't close to being able detect draws by means of the 50 move rule (100 plies). Especially since that is only the depth of the deepest line in the search, and to conclude it was certainly a draw, Stockfish would have to look at a huge number of lines that all eventually draw by the 50 move rule.</p>
<p>Endgame draws like this are notoriously difficult for engines, they have no good way to judge &quot;progress&quot; in their calculations. There are some attempts being tried out but they aren't at the level of Stockfish yet.</p>
<p>This is why <em>tablebases</em> were invented -- huge databases of all positions with up to some number of pieces (7 at the moment I think). They give an immediate answer. This is a five-piece position and a Stockfish configured to use tablebases would immediately know it is a draw.</p>
