That move wins him a pawn.
Because after his knight takes and your knight takes your opponent can play d5 forking your bishop and knight.
How is this a missed win?
Sort:
so missed win only means capturing a piece. I get it. Thought it meant match win
Apr 15, 2021
0
#4
I mean it's not necessarily that
Like a missed mate is also considered a missed win
A missed win is technically any move that misses a chance to "win" (like if black took the pawn he would be winning) but instead plays a move that is "bad" (like if you have mate in 1 but you take their pawns instead)
I would also have guessed that this move is a blunder, because the Knight can be captured by your Queen on h5. If the fork was played like chz3369 explained, it should still be even. Both players lost one pawn and one extra piece after Bxd5 and Qxd5. So I don't fully understand why this is considered a missed win by the engine.
When looking at the game analysis you can also look at the tab which says “Analysis”. There you can trace back, where the recommended move would lead some moves later. If you have enough time you can look at the analysis again. It would be interesting to know what the engine thought here.
Apr 15, 2021
0
#6
VantablackChess wrote:
I would also have guessed that this move is a blunder, because the Knight can be captured by your Queen on h5. If the fork was played like chz3369 explained, it should still be even. Both players lost one pawn and one extra piece after Bxd5 and Qxd5. So I don't fully understand why this is considered a missed win by the engine.
When looking at the game analysis you can also look at the tab which says “Analysis”. There you can trace back, where the recommended move would lead some moves later. If you have enough time you can look at the analysis again. It would be interesting to know what the engine thought here.
After Nxe4 Nxe4 d5 Bxd5 Qxd5 even though the material is even, black would have enormous pressure down the a8-h1 diagonal. After that a move like h6 followed by f5 would win the knight because it is pinned to the rook on h1. Even if black can't win the knight, white would be forced to be very passive in defending the knight, so that would give black lots of chances for attack.
chz3369 hat geschrieben:
VantablackChess wrote:
I would also have guessed that this move is a blunder, because the Knight can be captured by your Queen on h5. If the fork was played like chz3369 explained, it should still be even. Both players lost one pawn and one extra piece after Bxd5 and Qxd5. So I don't fully understand why this is considered a missed win by the engine.
When looking at the game analysis you can also look at the tab which says “Analysis”. There you can trace back, where the recommended move would lead some moves later. If you have enough time you can look at the analysis again. It would be interesting to know what the engine thought here.
After Nxe4 Nxe4 d5 Bxd5 Qxd5 even though the material is even, black would have enormous pressure down the a8-h1 diagonal. After that a move like h6 followed by f5 would win the knight because it is pinned to the rook on h1. Even if black can't win the knight, white would be forced to be very passive in defending the knight, so that would give black lots of chances for attack.
This might be an explanation. My only idea was playing d3 to guard the Knight after Qxd5. Maybe Ng3 could still be played after f5 to cover the Rook with the Knight.
Apr 15, 2021
0
#8
VantablackChess wrote:
chz3369 hat geschrieben:
VantablackChess wrote:
I would also have guessed that this move is a blunder, because the Knight can be captured by your Queen on h5. If the fork was played like chz3369 explained, it should still be even. Both players lost one pawn and one extra piece after Bxd5 and Qxd5. So I don't fully understand why this is considered a missed win by the engine.
When looking at the game analysis you can also look at the tab which says “Analysis”. There you can trace back, where the recommended move would lead some moves later. If you have enough time you can look at the analysis again. It would be interesting to know what the engine thought here.
After Nxe4 Nxe4 d5 Bxd5 Qxd5 even though the material is even, black would have enormous pressure down the a8-h1 diagonal. After that a move like h6 followed by f5 would win the knight because it is pinned to the rook on h1. Even if black can't win the knight, white would be forced to be very passive in defending the knight, so that would give black lots of chances for attack.
This might be an explanation. My only idea was playing d3 to guard the Knight after Qxd5. Maybe Ng3 could still be played after f5 to cover the Rook with the Knight.
Yes, Ng3 does guard the rook and saves the knight, but there's the problem Bd6 and then e4 with pressure on the knight on g3
chz3369 hat geschrieben:
VantablackChess wrote:
chz3369 hat geschrieben:
VantablackChess wrote:
I would also have guessed that this move is a blunder, because the Knight can be captured by your Queen on h5. If the fork was played like chz3369 explained, it should still be even. Both players lost one pawn and one extra piece after Bxd5 and Qxd5. So I don't fully understand why this is considered a missed win by the engine.
When looking at the game analysis you can also look at the tab which says “Analysis”. There you can trace back, where the recommended move would lead some moves later. If you have enough time you can look at the analysis again. It would be interesting to know what the engine thought here.
After Nxe4 Nxe4 d5 Bxd5 Qxd5 even though the material is even, black would have enormous pressure down the a8-h1 diagonal. After that a move like h6 followed by f5 would win the knight because it is pinned to the rook on h1. Even if black can't win the knight, white would be forced to be very passive in defending the knight, so that would give black lots of chances for attack.
This might be an explanation. My only idea was playing d3 to guard the Knight after Qxd5. Maybe Ng3 could still be played after f5 to cover the Rook with the Knight.
Yes, Ng3 does guard the rook and saves the knight, but there's the problem Bd6 and then e4 with pressure on the knight on g3
Okay, so it gets even more complicated. Moving the g1 Knight to e2 does also look very passive. Even if it defends the Knight on g3. It blocks the white Queen so black has an advantage, because the pieces are developed. It is not easy to figure that out from the screenshot shown above.
I did often observe that the engine expects a bit too much from the player. I sometimes had situations where the engine recommended that I should trade a Knight for a Pawn. The moves will make sense after like 10 moves but it is not obvious.
Apr 15, 2021
0
#10
Yes the engine always find the best move, but that usually is under the assumption that the player will always play the best move after the suggestion, but humans (especially ppl lower rated) can't see everything, so what seems like a winning position to a computer will often be losing to a human because they can't find the right continuation. Also, time control is a problem. You can't be expected to find a brilliant queen sac that mates when you only have 10 seconds on the clock.
However, in this case, material will be even, and black will force white to be very passive, so I guess its "winning" for black to play Nxe4
I don't usually look at the game analysis, but I did today and see that my opponent had a "missed win". How is this a missed win? He moves to e4, I take his knight with my knight.
Other times I've looked at the game analysis it showed moves that don't make much sense to me as what I (or my opponent) should have made. I'm no great chess player, but the moves make no sense to me.