Fields of Mistria 1.0 Troubleshooting

Version 1.0.6: memory, capture and display checks

• If memory or VRAM still grows abnormally and causes instability or a crash, record the version, hardware and reproduction steps, then use the Bug Report Form linked in the official notes. The developer’s qualified statement is not a guarantee that all crashes are fixed.
• If an OBS stream shows an in-game cursor that the streamer cannot see, the official temporary workaround is to turn off Native Cursor under the game’s Settings → Graphics.
• OBS Display Capture and Discord screen sharing still have some issues under investigation. Do not treat restored Game Capture and Window Capture as a fix for every capture method.
• Returning to the main menu no longer produces the reported black screen; Fullscreen and Borderless modes are no longer swapped.

Source: NPC Studio v1.0.6 patch notes. See the current performance checks and safe crash-reporting guide.

Earlier fixes confirmed in version 1.0.5

• Greatly reduced stuttering and improved frame pacing.
• Better high-refresh-rate and low-frame-rate behavior.
• Targeted crash, achievement and Museum-interface fixes.
• The player’s pet appearing during the wedding scene.

These performance improvements belong to v1.0.5, not v1.0.6.

Read the historical v1.0.5 player-impact guide · Official v1.0.5 source

Last checked

October 2, 2026

Patch covered

v1.0.6

Fixes confirmed in version 1.0.4

• Stillwell quests now track defeated monsters correctly.
• Stillwell objectives display the intended monster names instead of “MISSING.”
• Missing portraits appear in the final Mines cutscene.

High-impact version 1.0.3 fixes

• Wedding dates can no longer be selected on Spring 14, Fall 7 or Winter 7, avoiding festival setup conflicts.
• The letter sent after Museum completion correctly arrives with its reward.
• Song Crystals linked to late-game content stay unavailable until that content has been seen.
• True Love, Parent and several other achievements unlock more reliably.

Fixes confirmed in version 1.0.2

Gameplay and progression

• The Shooting Star Festival softlock is fixed.
• Players can no longer glitch into the Bell Tower before it is unlocked.
• A full inventory no longer makes the Mystical Feather drop in Dragonsworn Glade instead of the player’s home.
• The Time Flies achievement now works as intended.
• The new home-exterior letter arrives at the correct progression point: both the Carpenter’s Shop and player home must be fully upgraded.

Crash fixes

• Certain home configurations no longer crash at the start of the wedding cutscene.
• Rapid Bell Tower ladder interactions no longer crash the game.
• Rare startup crashes and file-access error crashes were addressed.
• Additional fixes cover animal sounds, mana use, mount-menu interaction, Mines boundary cases and rapid Dragonshrine-menu navigation.

Performance and localization

Version 1.0.2 improves performance when proprietary AMD or Nvidia overlays render in the same window. It also adds and corrects beta-localization text, including a crash involving some localized Friday Night at the Inn dialogue.

Non-destructive troubleshooting order

1. Confirm the installed game version. Compare the title-screen or platform version with v1.0.6 before relying on a launch-day workaround.
2. Restart the game after updating. This ensures the current executable and data are loaded for the next test.
3. Reproduce the problem once with external overlays closed. NPC Studio specifically notes overlay-related performance improvements, making overlays a relevant comparison point for performance—not a universal cause.
4. Update the graphics driver and operating system for performance problems. NPC Studio identifies this as an appropriate step in the v1.0.2 known-issues note.
5. Preserve save data. Do not delete or overwrite a file to test a community theory.
6. Use NPC Studio’s bug-report resource. The current patch-note pages link the active form and are the best escalation path for a reproducible issue.

Save visibility and Steam Deck reports

NPC Studio’s 1.0 FAQ says existing saves carry into the update. The launch research also records player reports of save visibility issues around the transition on Steam Deck. Those reports do not establish an official universal fix.

Treat any file-moving or profile-editing workaround as community-reported. Preserve the original data, avoid destructive changes and include the platform, installed version and exact symptom when reporting the problem.

Problem-specific checks

Stillwell counter stays at zero or objective says “MISSING”

Update to v1.0.4 or later, confirm that the matching Mission Quest is active and defeat the named target once. If it still fails, record the quest name, installed version and exact enemy for a reproducible bug report rather than altering save flags.

Wedding date conflicts with a festival

Version 1.0.3 prevents Spring 14, Fall 7 and Winter 7 from being selected because those dates are needed for festival setup. If an older build already accepted one of those dates, update before rescheduling or testing community workarounds.

Mystical Feather appeared in the wrong place

Update to v1.0.2. The documented bug involved a full inventory and an incorrect Dragonsworn Glade drop instead of the player’s home.

Wedding cutscene crashes

Version 1.0.2 fixes crashes tied to certain home configurations at the start of the wedding cutscene. Update and retest before changing the home solely to follow older advice.

Bell Tower crash or early entry

Both the rapid ladder crash and the pre-unlock entry glitch are addressed in v1.0.2. Follow normal quest access and avoid using a glitch as part of progression.

Time Flies does not unlock

The achievement was fixed in v1.0.2. Confirm the patch, load the intended save and compare the requirement with Steam’s current official description.

Version 1.0.1 context

The first post-launch patch fixes several separate crashes involving Friday saves, Mines rooms, a skipped Fire Seal cutscene, the Town Rank Guide, monsters, mods and rare town shadows. If a report says it was fixed in 1.0.1, verify that it matches those notes rather than assuming every launch crash shares one cause.