Settings reference

This page lists every option in the Settings window. Open Settings with the ⚙ button in the top bar. Close it with Esc or the ✕ button.

The window has five sections: Appearance, Performance, Solver, Folders, and About. Every change is saved automatically to config.json under %APPDATA%\artgto\ and survives a restart.

screenshot

Settings window open on the Appearance section

Appearance

Setting	What it does	Default
`Light mode`	Switches the whole app to a light theme. When off, the app uses the dark theme.	Off (dark theme)
`Scale with window size`	Zooms the complete interface to fit the window. See details below.	Off
`Four-color deck`	Draws each suit in its own color, so suits are easier to tell apart at a glance. Display only — it changes nothing about the solve.	On
`BB display`	Shows big-blind labels on amounts.	On
`Fold EV = 0`	Changes how EV numbers are displayed. See details below.	On

Note

All Appearance settings are display preferences. They never change the strategy the solver computes.

Scale with window size

By default the interface uses a fixed scale, like most desktop apps. Turn this checkbox on if you want the whole interface to grow and shrink with the window instead. The in-app hover text explains it like this:

Note

Always show the complete interface, zoomed to fit the window — resizing or maximizing scales everything proportionally, and no panel is ever cut off. The UI scale slider fine-tunes the zoom on top (below 1.00 adds margin, above 1.00 trades the edges for size).

When the checkbox is on, the UI scale slider next to it becomes a fine-tune on that fit. Its range is 0.6 to 2.5, and the Reset button puts it back to 1.0 — the exact fit.

Tip

Turn this on if you work on a large monitor. Maximizing the window then makes everything bigger, instead of leaving empty space around a small layout.

Fold EV = 0

This checkbox controls the EV display convention. The in-app hover text:

Note

Show EVs with already-committed chips added back, so a fold reads 0 (PioSOLVER / SimplePostflop convention). Off shows net EV, where folds are negative. Display only — strategies are identical either way.

In plain words: with the box checked, EV numbers match what PioSOLVER and SimplePostflop show, which makes solutions easy to compare across tools. With the box unchecked, you see net EV — chips you already put in are counted as spent, so a fold shows a negative number. Both views describe the same strategy.

Performance

Setting	What it does	Default
`Solver cores`	How many CPU threads the solver uses. Slider from 1 up to all logical threads of your CPU.	All logical threads
`Progress overlay`	Shows a small always-on-top progress window while the main window is minimized.	Off

Solver cores

The in-app hover text:

Note

20-30% faster with all logical threads (includes SMT); default is all cores

Why this is the default: the solver spends much of its time waiting for data from memory. The second hardware thread on each core (SMT, also called hyper-threading) fills that waiting time with useful work. Measured on real solves, using all logical threads is 20–30% faster than using only the physical cores.

Lower the slider if you want to use your computer for other work during a long solve. The solve gets slower, but the machine stays responsive.

Note

Results are reproducible. The same spot, solved with the same core count, gives the same output every time.

Progress overlay

Off by default. When on, a small window stays visible on top of your desktop while ARTGTO is minimized. It shows live progress for the current solve, Multi Job run, or export, so you can watch a long run without restoring the app. Click the overlay to bring the main window back.

Solver

Setting	What it does	Default
`Algorithm`	Which algorithm runs the solve iterations.	`HS-DCFR (tuned — fewer iterations)`

The dropdown has two options:

Option	Meaning
`HS-DCFR (tuned — fewer iterations)`	The default. A tuned schedule of the DCFR parameters. It reaches the same accuracy target in about 6–13% fewer iterations, so solves finish sooner.
`DCFR (legacy, fixed α/β/γ)`	The earlier algorithm with fixed parameters. Kept available for comparison.

Both options converge to the same equilibrium — the difference is only how fast they get there. See Algorithms for the full explanation.

Folders

ARTGTO keeps its files in six folders. Each row in this section has a Browse button, so you can move any folder to a different location — for example, a larger drive.

Folder	What is stored there	Default location
`Ranges`	Range files (`.range.json`), in one subfolder per position. The range dropdowns on the Solver tab read from here.	`%APPDATA%\artgto\ranges\`
`Bet Sizing`	Bet sizing profiles (`.json`).	`%APPDATA%\artgto\betsizes\`
`Jobs`	Saved jobs (`.json`) shown in the Jobs queue.	`%APPDATA%\artgto\jobs\`
`Library`	The root of your solved `.art` collection. The Library tab scans this folder for batch export, and Multi Job writes finished solves into it.	`%APPDATA%\artgto\library\`
`Game Configs`	Game config files (`.json`): pot, stack, and rake presets per position pair, used by Multi Job.	`%APPDATA%\artgto\gameconfigs\`
`Spots`	Spot templates (`.json`) used by Multi Job batch creation.	`%APPDATA%\artgto\spots\`

Tip

A solved .art file is usually 10–30 MB. If you plan to build a large library, point the Library folder at a drive with enough free space.

screenshot

Folders section with the six path pickers and Browse buttons

About

Item	What it shows
Version	The installed app version, for example `0.9.13-beta`.
License status	Whether this install is licensed. Without a license the app runs as a viewer: you can open and study solutions, but solving, exporting, and batch work are disabled.
`Check for updates`	Checks for a newer version and installs it. See Updates.

If something is not working, the Troubleshooting & FAQ page explains where the logs are and how to send a bug report from inside the app.