DOSBox Pure Settings Not Saving? Save Per-Game Core Options in RetroArch

Short Answer

If a DOSBox Pure setting disappears after relaunch, save it through RetroArch’s Core Options system:

Launch the DOS game with DOSBox Pure.
Change the required Core Option.
Open Quick Menu → Core Options → Manage Core Options.
Select Save Game Options.
Confirm that RetroArch reports success.
Check Active Options File. It should show a game-named .opt file.
Close the content normally, then relaunch the same content entry with the same core.
Check both the active filename and the saved option value.

This route is for DOSBox Pure Core Options. A RetroArch configuration override uses .cfg, while an input remap uses .rmp. Neither replaces a game-specific .opt file.

If the game file is not selected after relaunch, check that Load Content-Specific Core Options Automatically is enabled.

Problem: What “Not Saving” Can Mean

“Not saving” can describe several different problems:

No game-specific Core Options file was created.
A game file exists, but content-specific Core Options loading is disabled.
A folder or base file is active when a game file was expected.
A broader scope makes the same setting affect multiple games.
The game is launched under a different effective basename or with a different core.
RetroArch reported a write error.
Values were edited after the game file was created, then the frontend ended before those later changes reached disk.
The value persisted but the setting requires a restart before its effect is visible.

The last case is not a persistence failure. Verify the selected value after relaunch instead of judging only by its immediate effect.

Version and Evidence Scope

This guide is based on official tagged source for RetroArch 1.19.1 and DOSBox Pure 0.9.9, plus official Libretro documentation. It describes externally researched behavior, not an owner device trial.

RetroArch 1.19.1’s English interface uses labels including Core Options, Manage Core Options, Save Game Options, Save Content Directory Options, Active Options File, and Flush Options to Disk. Newer releases, translations, menu drivers, Quick Menu visibility settings, and distribution customizations may use different wording or hide entries.

DOSBox Pure supplies its settings through Libretro’s Core Options API. RetroArch manages the active options file, its scope, and the per-game save workflow.

Cause: Core Options Have Different Scopes

Choose the narrowest scope that matches the change.

Game scope

Use Save Game Options when only the loaded game should use the settings.

RetroArch 1.19.1 constructs a game path from the loaded core’s library name and RetroArch’s effective content basename:

<Config>/<core>/<effective-content-basename>.opt

The content extension is removed. Renaming the loaded content or using a differently named launch entry can therefore select a different game .opt. Two entries with the same effective basename under the same core resolve to the same game-options path.

Content-directory scope

Use Save Content Directory Options when relevant games in one content directory should share the settings. The folder-specific filename is based on the parent content-directory name, so moving content can change which folder file is selected.

Moving content without changing its effective basename does not, by itself, change its game-specific .opt path. Directory changes matter directly to content-directory scope.

Core or global base scope

When no game or folder file is active, RetroArch uses a base Core Options store:

With Use Global Core Options File disabled, RetroArch uses per-core storage constructed as <Config>/<core>/<core>.opt.
With it enabled, RetroArch uses the shared retroarch-core-options.cfg.

retroarch-core-options.cfg is a special Core Options backing file. Its .cfg suffix does not make it an ordinary frontend configuration override.

Which scope wins?

RetroArch 1.19.1 selects Core Options in this order:

Game-specific .opt
Content-directory .opt
Base per-core .opt or shared retroarch-core-options.cfg

A game or folder .opt is selected instead of the broader store. These Core Options files do not stack or merge over the base. A game file can therefore mask a folder or base change, while a folder file can make a setting appear across several games.

Solution: Save DOSBox Pure Settings for One Game

Launch the intended content entry with the intended DOSBox Pure core.
Open Quick Menu → Core Options.
Change the desired DOSBox Pure setting.
Open Manage Core Options.
Select Save Game Options.
Confirm that RetroArch reports success rather than an error.
Reopen Manage Core Options.
Record the filename shown beside Active Options File.
If you change more values after creating the game file, use Flush Options to Disk when visible. Otherwise, close the content normally.
Relaunch the same content entry with the same DOSBox Pure core.
Recheck both the active filename and the option value.

In RetroArch 1.19.1, Save Game Options writes the current option set immediately and activates the resulting game file. A write failure produces an error rather than successful activation.

Later edits to an active game or folder file are written when Core Options are deinitialized, including during normal core shutdown. Flush Options to Disk forces current values into the active file, but visibility settings may hide this entry. It is useful when available, not mandatory.

If Manage Core Options is missing, confirm that content is running, Core Options are available, and Load Content-Specific Core Options Automatically is enabled.

For an example of a DOSBox Pure adjustment that may be isolated per game, see KNULLI DOSBox Pure Mouse Too Fast on RG CubeXX? Firefly Settings.

How to Check the Active `.opt` File

Open Quick Menu → Core Options → Manage Core Options and find Active Options File.

In RetroArch 1.19.1, this field shows the basename of the selected Core Options file. A game-named .opt indicates that RetroArch selected a game-specific file for the current content.

It does not show the full filesystem path or prove which keys and values are stored inside the file. A filename proves selection, not that a later edit was written. Verify the option value after relaunch as well.

`.opt` vs `.cfg` vs `.rmp`

These RetroArch workflows solve different problems:

File/system	Stores	RetroArch 1.19.1 route
Game/folder `.opt`	Core-provided settings, including DOSBox Pure Core Options	Quick Menu → Core Options → Manage Core Options
Frontend `.cfg` override	Supported RetroArch frontend configuration differences	Quick Menu → Overrides
Input `.rmp` remap	Control remapping	Quick Menu → Controls → Manage Remap Files

Use Save Game Options for a DOSBox Pure Core Option. Save Game Overrides creates a frontend .cfg override, while Save Game Remap File creates an input .rmp file. For the input-layer workflow, see DOSBox Pure keyboard and control mapping.

The shared retroarch-core-options.cfg is the naming exception: it is a Core Options base store despite its extension, not an ordinary frontend override.

Troubleshooting When Settings Appear to Reset

The following are evidence-based diagnostic checks, not confirmed causes on a specific device.

Check the workflow

A .cfg override or .rmp remap does not save DOSBox Pure Core Option values. Use Core Options → Manage Core Options → Save Game Options.

Enable content-specific loading

When Load Content-Specific Core Options Automatically is off, RetroArch 1.19.1 skips game and folder .opt files during loading.

Confirm the same content identity and core

A renamed or differently launched entry can use a different effective basename. A different core selects a different core directory.

Check the active scope

A game file takes priority over folder and base stores. If a broader change appears ignored, inspect Active Options File for a game .opt. If settings affect too many games, a folder or base scope may be active instead.

Treat directory changes carefully

Directory changes matter directly to content-directory options. They do not automatically change a game .opt when the effective basename and core remain the same.

Read write errors before diagnosing them

RetroArch reports an error if Save Game Options cannot write the file. Check the notification and relevant log. An unwritable Config path is one possible explanation, but official source does not establish permissions as the only cause.

Close normally after later edits

Creating the game file writes current values immediately. Later edits normally reach disk when Core Options are deinitialized. If the frontend ends improperly, those later edits may not be written. Use Flush Options to Disk when visible, or close content normally.

Separate persistence from restart behavior

A saved value may require a core or content restart before its effect appears. Check whether the value itself remains selected after relaunch.

Verification After Relaunch

Close the content normally.
Relaunch the same content entry with DOSBox Pure.
Open Quick Menu → Core Options → Manage Core Options.
Confirm that Active Options File shows the expected game .opt.
Return to the relevant Core Option.
Confirm that the chosen value remains selected.
If behavior is unchanged but the value persisted, check whether that option has a documented restart or other condition.

The filename answers “Which file did RetroArch select?” The value answers “Did the intended setting reload?” Both checks are required for reliable verification.

When This Guide May Not Match Your Setup

Menus may differ with another RetroArch or DOSBox Pure version, language, menu driver, distribution customization, or visibility setting. Current documentation may use Quick Menu → Options rather than the exact RetroArch 1.19.1 wording.

This guide does not establish one universal Config directory for every device or installation. Use RetroArch’s configured paths and logs when investigating a write error.

FAQ

Does a game `.opt` merge with folder or core options?

No. In RetroArch 1.19.1, the game file is selected instead of the folder or base Core Options store.

Does Active Options File prove that my value was saved?

No. It identifies the selected filename. Check the option value after relaunch to verify that the intended setting reloaded.

Is `retroarch-core-options.cfg` a frontend override?

No. It is RetroArch’s special shared Core Options base store when Use Global Core Options File is enabled.

Should I always use Flush Options to Disk?

No. Save Game Options writes the current set immediately. Flush is useful for later edits when visible; a normal content close is the standard alternative.

What if RetroArch reports a save error?

Check the notification, log, and configured Config directory. Do not assume permissions are responsible without supporting evidence.

Sources

RetroArch 1.19.1 labels and menu availability

RetroArch 1.19.1 save, load, naming, and scope

`.opt`, `.cfg`, and `.rmp` workflows

DOSBox Pure 0.9.9 and current documentation

Documentation scope note: Current Libretro pages explain the concepts but are not exact RetroArch 1.19.1 UI snapshots. Tagged source controls where wording or behavior differs.