Why is the game report calling this move a blunder?

Sort:
fdsdfg
 
 
I am an amateur player. I was analyzing a game of mine where I was up a pawn in the endgame. The game report puts the score at -53, and all looks well for me. Then I make the move 46 ... Rg1. The engine reports that this is a huge blunder, and now the score is -3.
 
Then the report says White's best move is to move the king, followed by black playing f3. Now the engine reports the score is back to -53. Realistically, black will promote the pawn and win the game without too much difficulty.
 
Why does the engine hate this Rg1 move?

 

notmtwain
fdsdfg wrote:
 
 
I am an amateur player. I was analyzing a game of mine where I was up a pawn in the endgame. The game report puts the score at -53, and all looks well for me. Then I make the move 46 ... Rg1. The engine reports that this is a huge blunder, and now the score is -3.
 
Then the report says White's best move is to move the king, followed by black playing f3. Now the engine reports the score is back to -53. Realistically, black will promote the pawn and win the game without too much difficulty.
 
Why does the engine hate this Rg1 move?

 

 You can't use engines to analyze endgames. Even though they may seem simple to you, the number of possible moves to check out becomes enormous when you have to look out ten moves or more.

I looked up the endgame in a tablebase and found that Rg1 was a perfectly reasonable move leading to a win not quite as fast as Rg8. (24 moves versus 22 moves for Rg8)