Fields of Mistria Troubleshooting: Crashes, Saves, Performance, and Controls

Start with a clean baseline

1. Confirm Steam has finished updating the game and that the title screen reports at least version 1.0.1.
2. Close the game normally, restart Steam, and launch again.
3. Use Steam's installed-files verification if the game still fails to launch or behaves inconsistently.
4. Test once without third-party modifications or injected overlays.
5. Change one setting at a time so you know which action affected the result.

Back up important saves before manually moving, replacing, or editing any save data.

Problems addressed by 1.0.1

The 1.0.1 hotfix specifically addressed multiple crash paths after the full release. The archived official notes include Friday saves, Mistmare Ranching UI, a secret-bachelor Harvest Festival route, a Mines arena room, the Fire Seal scene, Journal and Town Rank UI, Rock Stack, mod wallpaper, monsters, town shadows, and a Russian-dialogue case.

It also corrected Crown Request letter text, seasonal date-photo display, and the Mines Crate Chair preview. If your symptom matches one of these, updating is more appropriate than applying an old workaround.

Save and Steam Cloud checks

Steam Cloud was listed as supported on August 6, 2026. The same Steam metadata snapshot lists these local save locations:

• Windows: %USERPROFILE%/AppData/Local/FieldsOfMistria/saves
• Linux: $XDG_DATA_HOME/FieldsOfMistria/saves

Before copying files, exit the game and allow Steam synchronization to finish. Make a separate backup copy rather than editing the only save. If local and cloud timestamps disagree, identify the newer file before accepting an overwrite prompt.

Performance and display

Version 1.0 included developer-reported performance improvements and more than a 50 percent reduction in VRAM use compared with the previous update. That claim does not guarantee identical results on every device.

For stutter or display problems, restart after the update, close unnecessary overlays, reduce one graphics option at a time, and check whether the issue appears in a new test session as well as the main save. Do not copy the archived Linux API requirements: their memory and storage units contain obvious metadata errors.

Controls are not responding as expected

Open Controls and check for conflicts. Many actions can be assigned two inputs. If a rebound input behaves unexpectedly, restore that action, apply the change, and bind it again. On a controller, test the Steam input state and the game's own bindings separately rather than changing both at once.

A quest or event looks stuck

Check the exact Journal objective, mail, Request Board, Donation Box, current time, and named character. Some quests turn in through a box while others require conversation. If the issue involves Town Rank UI, a Crown Request letter, Friday saving, or a 1.0 story scene, confirm 1.0.1 before further diagnosis.

When to report a bug

If the issue persists on the current build after a clean-file test, record the game version, operating system, input type, exact location, quest or event name, steps that reproduce it, and whether it also happens in another save. This creates a useful report without exposing or deleting your only save.