ART/GTO
Buy ART/GTO →↓ Download
Reference

Troubleshooting & FAQ

This page covers common problems, where to find logs, how to report bugs, and answers to frequently asked questions.

Out-of-memory errors

The most common issue. The solver builds large data structures in RAM, and a spot that exceeds your available memory will be refused by the pre-solve memory guard rather than freezing your machine.

If you see a memory error, try these in order:

  1. Enable 16-bit compress. Found in the Bet Sizing panel (single solve) or the Game config (Multi Job). This cuts memory use roughly in half with minimal accuracy cost.
  2. Enable Low-memory fallback. On by default. When even 16-bit does not fit, the solver groups similar river hands into buckets. Flop and turn stay full detail. The result is labeled river-bucketed @ N.
  3. Reduce the raise cap. Fewer allowed raises means a smaller game tree. If you are using raise cap 3 or higher, try 2.
  4. Reduce stack depth. Shallower stacks produce smaller trees. Consider whether you really need 200bb+ for the spot you are studying.
  5. Close other applications. The memory guard checks free RAM at solve time. Closing browsers, other solvers, or large applications frees headroom.
  6. Add more RAM. If you routinely solve deep-stack, high-raise-cap spots, 32 GB or 64 GB makes a real difference.
Warning
Do not disable the memory guard. It exists to prevent your machine from freezing. If a spot does not fit, the solver tells you up front — that is better than a 20-minute freeze followed by a crash.

The app log

ARTGTO writes a log file to:

%APPDATA%\artgto\artgto.log

This file contains diagnostic messages, error details, and memory-guard estimates. If something goes wrong, check here first. The log is capped at a reasonable size and overwritten each session.

The Multi Job run log (per-board solve outcomes) lives in a separate folder: %APPDATA%\artgto\job-logs\. See The run log for details.

Reporting a problem

Use Report a problem in Settings → About. This opens a form where you write a short description of what happened. The report automatically attaches:

  • Your app version
  • Operating system, CPU, and RAM
  • License fingerprint

If you check Include my recent app log (recommended), the tail of artgto.log is attached too, giving the team the context needed to diagnose the issue without back-and-forth.

Tip
Include steps to reproduce the problem if you can. "I loaded a 150bb SRP on Ks7d2c, clicked solve with 16-bit on, and it failed after 3 seconds" is much more useful than "it crashed."

File compatibility

.art files are forward-compatible: newer versions of ARTGTO read files saved by older versions.

One specific case worth knowing: versions 0.9.9-beta and 0.9.10-beta accidentally wrote .art files with a slightly different internal layout. Version 0.9.11-beta added a built-in compatibility reader for them. If you have files saved on 0.9.9 or 0.9.10, they load fine on 0.9.11 and later. Nothing needs re-solving, and no files were damaged.

If an old file fails to open, update to the latest version first. The compatibility reader is only available in 0.9.11+.

Frequently asked questions

Why does solving take so long?

The solver iterates toward a Nash equilibrium by repeatedly traversing the entire game tree. Larger trees (deeper stacks, more raise sizes, wider ranges) take longer per iteration and need more iterations to converge. Enabling 16-bit compress can help with memory but is slightly slower per iteration. The HS-DCFR algorithm (the default) converges in fewer iterations than legacy DCFR — make sure it is selected in Settings → Solver.

What does exploitability mean?

Exploitability measures how far the current strategy is from a perfect Nash equilibrium, expressed as a percentage of the pot. Lower is better. A value of 0.3% means that a perfect opponent could gain at most 0.3% of the pot by deviating from the equilibrium response. For practical study, anything below about 0.5% is more than sufficient.

Can I use my old .art files?

Yes. ARTGTO reads .art files from all previous versions. Files from 0.9.9/0.9.10 are handled by a compatibility reader added in 0.9.11. Always stay on the latest version to make sure you have the most up-to-date readers.

Can I resume a partially solved spot?

No. The solver's internal state (regrets) is not saved in the .art file. If you need a more refined result, run the spot again with a lower exploitability target or more iterations.

Where to go next