#1175
"you are assuming that Stockfish evaluations represent perfect play"
++ No, engine evaluations are always flawed. There are only 3 possible correct evaluations: draw, win, loss as in a table base. That is why to solve chess the calculation must not stop until the table base is reached. However, the flawed engine evaluation may guide the calculation. Based on the flawed engine evaluation we can select the top 1 move for black. If always selecting the top 1 move for black is good enough to reach a table base draw, then chess is solved. For white the proof must look at more possibilities, e.g. 4 per move. If we can prove black can draw after 1 e4, 1 d4, 1 c4, 1 Nf3 then it becomes trivial to prove that black also can draw after 1 e3, 1 d3, 1 c3, 1 Nh3. It is also unnecessary to look at e.g. 1 e4 e5 2 Ba6. The flawed evaluation helps to guide the calculation towards the true evaluation by the table base.
"engines still get better every release." That is true, but if the top 1 black move per engine software version X on hardware Y is enough to reach a table base draw, then that is good enough. Likewise the top 4 white moves on software version X on hardware Y will more or less correspond to the top 4 white moves on software Z on hardware T. This is clearly shown in TCEC, where evaluations by both engines are shown. In like 98% of cases they concur. The 2% where they disagree are the cases where one engine beats the other. Even then the top 4 moves tend to agree.
"You can't bet better if you are already perfect."
++ No they are not perfect and they are flawed, but they are good enough to select the top 1 move for black and the top 4 moves for white to calculate towards the table base.
"Approaching the tablebase with a set of flawed evaluations doesn't work."
++ It did for checkers: starting from the opening, using Chinook to calculate towards the table base.
"reaching the tablebase 100% of the time still does not solve chess."
++ It does. The table base gives the correct evaluation: draw or not. The huge problem is to calculate that deep and that wide that the calculation hits the table base 100% of the time. Already in TCEC the engines running on poor hardware and with a short time start to hit the 7 men table base around move 10 and more around move 20. A top engine on top hardware like Sesse will hit it more especially when guided by the human assistants.
Lol, again, even using your own numbers and logic...if 2% of the evals will be wrong in your overreaching 10^37 culled positions...that's 2^35 positions you will not cover. So how do you propose to call chess solved with 2^35 positions that might not be forced draws? That's at least 20 orders of magnitude more chess positions than have occurred in all of human history...
All you will be able to say is that chess is very likely to be a forced draw...which is where we were already.
should i upgrade to premium ? you
r thoughtd