How is the position after 35.h5 not a draw? Computer says -3.6?
*32.h5
The computer just doesn't understand that there's no way black can win. It just thinks "Oh, black is up a piece - Therefore winning"
White could be extremely careless and let the bishop sneak into their base. Then, the bishop could take the white pawn in front of the king at move 32 and continue nabbing pawns if White is careless.
Although idk why Stockfish says that black is winning when there is no way to win unless white is careless
Although idk why Stockfish says that black is winning when there is no way to win unless white is careless
@dtoledo It is. Stockfish is wrong. Sometimes it doesn't understand endgames like this.
Good to know that I was not losing my grip on reality...
@Schachspieler102 said in #3:
> The computer just doesn't understand that there's no way black can win. It just thinks "Oh, black is up a piece - Therefore winning"
WHAT
> The computer just doesn't understand that there's no way black can win. It just thinks "Oh, black is up a piece - Therefore winning"
WHAT
@Dean_Summer Stockfish is not perfect at chess. It can't even see the board. It really has no clue what is going on except for the eval function that has been given to it by humans. Sometimes that function is wrong, and this is one such case.
This kind of thing happens a lot with engines.
stockfish doesn't have a good understanding of unbreakable fortresses. for example : lichess.org/analysis/1k6/3r4/8/p1p1p1p1/PpPpPpPp/1P1P1P1P/2R5/2R1K3_w_-_-_0_1
this is dead drawn. it's very very obvious to the human eye. but since white is up a rook, they get an "advantage", or so says stockfish. unless black takes a rook that white offers, its a draw.
this is dead drawn. it's very very obvious to the human eye. but since white is up a rook, they get an "advantage", or so says stockfish. unless black takes a rook that white offers, its a draw.
This topic has been archived and can no longer be replied to.