Repository navigation
fastchess-gui v0.6.3
The Board page rebuilt to read a game: a graph of the game, an analysis that refines itself pass after pass with one
engine or several, what each move was and what it should have been, variations, and a review of the game.
The game graph
- Under the moves, a graph of the game: the judging analysis as a white and black area, each engine that played as a
curve of its colour at its own moves, the marked moves on the curve, the book hatched, the phases (opening,
middlegame, endgame, as lichess divides a game), the zone the tablebases know, and under the axis the time of each
move, White's up and Black's down. - Tabs for win chances (from the engines' WDL when they give it), WDL, time, depth, nodes, speed, tablebase hits, how
far apart the evaluations are, and PV agreement. Hover tells the move and what each engine said; a click or a drag
goes there; the legend shows or hides each curve; the graph folds. - The Games tab and the Live view draw the same graph.
The continuous analysis
- Analyse the game (G) gives the graph in a second or two, then searches every position again four times longer at
each pass, up to the time per position chosen beside the button (0.3 s to 20 s, or until stopped). The graph's
header tells where it is. - The positions go from the last to the first, the position on the board first. Measured against long searches with
Gaia and Stockfish, this is about 16 % closer than from the first to the last for the same time
(tools/analysis_bench.py). - It runs on a thread of its own with its own engine, counted in the core budget; the board's analysis pauses it. Each
complete pass is kept with the game, and the analysis goes on from there. - Several engines can analyse the same game (+ Engine in the graph's legend), Gaia and Stockfish side by side for
example, each with its curve and its colour, pass by pass together. One judges the moves; a mark is hollow when the
analyses disagree or the last pass changed it.
This move, the board and the moves
- Under the moves: what the engine that played the move said, the line it expected, and each analysis's verdict and
best move; Show lays a line on the board without touching the game. On the board, the judgement as a badge on the
move's square and the expected reply as a dashed arrow. N and Shift+N go from one marked move to the next. - The analysis card: its settings folded into one button, the search as tiles, the lines on two lines with
figurines; hovering a move of a line shows it on the board, a click plays the line up to it. Threat (X): the
opponent's best move were it to move again, as a red arrow. - The moves as flowing text with figurines from the board's piece set (a setting in Appearance), the end of the book
marked. Moves played on the board are kept as variations, in brackets, which can be promoted, deleted or copied;
the variations of a PGN file are read, and Copy PGN writes them. - A Table tab lists each move with its engine's score, depth and time.
- The players above and below the board, with their engine's evaluation, the time of their last move and their clock
(from[%clk], or rebuilt from the time control). The page's subtitle gives the time control, the opening and how
the game ended.
The review
- A Review tab: each side's accuracy (lichess' formula), its inaccuracies, mistakes and blunders, its average loss,
how often the analysis would have played its move, its depth and time, its accuracy in each phase; the key
moments, each a click away; and who saw the turning point first, among the engines that played and the analyses. - Copy PGN with the analysis writes each position's evaluation as
[%eval], the judgements as NAGs and the line the
analysis preferred; Copy as BBCode gives the review for a forum.
Tablebases
- With the Syzygy folders of the setup, the Board page tells the tablebase result after each move and whether the
move kept or spoiled it, and the graph shows the zone the tables know.
Other changes
- A match can give engine A or B White in every game, the colours of every pair locked (odds games, an opening tried
from one side); each game of a pair then plays an opening of its own. - The analysis's arrows are chosen in Settings > Appearance, beside the boards' buttons.
- The engine console writes down what is sent before it is sent.
- The release archives hold the application, its licenses and the README, nothing else.
- The guide describes the new Board page in every language.
Downloads
| File | Contents |
|---|---|
fastchess-gui-v0.6.3-linux-x86_64.tar.gz |
fastchess-gui, x86-64 Linux (glibc 2.35 or newer). Needs X11 or Wayland. |
fastchess-gui-v0.6.3-windows-x86_64.zip |
fastchess-gui.exe, 64-bit Windows 10 version 1903 or newer. No installer, nothing else to install. |
fastchess-gui-v0.6.3-macos-universal.zip |
fastchess-gui.app, macOS 13.3 or newer, Apple silicon and Intel. Not signed: Control-click it and choose Open the first time. |
SHA256SUMS.txt |
Checksums of the three archives. |
The binaries are built by this repository's GitHub Actions workflow; the tests run on Linux, Windows and macOS. The
archives carry the licenses of the libraries built in, of the piece sets and of the 3D board's pieces and tone mapping
(see ATTRIBUTION.md).
Known limitations
They are tracked as issues labelled known limitation.