lichess.org
Donate

"GO DEEPER"

When the local engine reaches a certain depth (for me it's 22, I think it differs though), a little button appears with the text "GO DEEPER." Clicking this allows to reach all the way up to depth 99. My question is, why isn't this disabled by default? Why do I have to click it to reach depth 99? It's all local, after all, so I don't think the servers benefit from it either.
I have only 18 depth max, how can I change it?
Depending on how many kn/s your machine can reach the max appears differently.
My point is, there is no max. If we're able to reach depth 99 anyway, by clicking on "Go deeper," why doesn't it just do that automatically?

Also, in @kreedz ' case, he might not have the required technology. I'm no expert, but I believe there's something required called PNACL (Portable NAtive CLient) and kreedz might not have that.
I just tested the same thing on Mozilla Firefox (I usually use Google Chrome) and I noticed a couple of differences. Firstly, I could only reach up to depth 18. Secondly, there was no "Go deeper" button when depth 18 was reached. And finally, it said "ASMJS" where it says "NATIVE" for me.

Anyway, I still think that for people who do have the required technology, like me, the whole "Go deeper" button shouldn't be necessary. It's a tiny thing, but one I think would improve the site.
So it doesn't use your cpu constantly?
I bet the number of people who would want it on at all times is far smaller than the number of people who don't
I can't find the "Go Deeper" bottum. Can you tell my were it is?
@jimj12 You bring up a good point, though I still feel like there could be an improvement. I'm mainly talking about endgames, where the tablebases are not activated yet. Stockfish usually reaches depth 22 within a few seconds, and the evaluation it gives still cannot always be trusted (endgames are often surprisingly complicated). Maybe instead of a maximum depth there should be a maximum amount of time the engine spends, like thirty seconds for example. This way, endgames can be analysed more effectifely and CPU drainage is still not a big problem.

This topic has been archived and can no longer be replied to.