So I was just minding my business, analysing a blitz game and I briefly glanced at the engine depth, just to see that it said 113?! Is this even possible? I'm literally just using my laptop to look at game review, not some super computer. This is a weird glitch.
How is this possible?!
Sort:
For me, it normally says something like 22; has anyone else seen this?
Interesting
When there are very few pieces left in the endgame, the engine can analyze much deeper for the same amount of effort.
that happens to me sometimes
magipi wrote:
When there are very few pieces left in the endgame, the engine can analyze much deeper for the same amount of effort.
ohh that makes sense
Feb 23, 2025
0
#9
in simple terms, the engine has already found mate in most lines so it gets lazy when analyzing deeper
Mikey383 wrote:
in simple terms, the engine has already found mate in most lines so it gets lazy when analyzing deeper
This isn't true, and it does't make any sense.
Feb 24, 2025
0
#11
what do you mean, many engines use a method where when they find a move worse than a previously examined move, then it does not need to examined further. it is literally the entire concept of alpha-beta pruning. (https://en.wikipedia.org/wiki/Alpha%E2%80%93beta_pruning)
Mikey383 wrote:
what do you mean, many engines use a method where when they find a move worse than a previously examined move, then it does not need to examined further. it is literally the entire concept of alpha-beta pruning. (https://en.wikipedia.org/wiki/Alpha%E2%80%93beta_pruning)
Pruning helps the engine analyze deeper the relevant lines. It is the opposite of " it gets lazy when analyzing deeper".