For fields of mistria screen stuttering, start by naming the symptom, recording the game and platform state, and testing one reversible change at a time. Use the same short route for every comparison so frame pacing, sustained low FPS, and screen tearing stay separate. If local settings do not help, keep the clean record for NPC Studio's bug form.
Name the symptom before changing anything
Use one short, repeatable route in the same save and record where the problem begins. Write down the version shown at the lower left of the title screen, Windows or Linux platform, desktop or laptop hardware, monitor refresh rate, display settings, and every installed mod. Keep the old value beside each setting you change so the next comparison has a baseline.
| Symptom | What to record |
|---|---|
| Stutter | Where it occurs, including weather, menus, or scene changes |
| Sustained low FPS | Average FPS and elapsed time for the whole test route |
| Screen tearing | The VSync state when a horizontal seam appears |
Establish a supported 1.0.2 baseline
The developer's bug form asks players to include the title-screen version and suggests Steam file verification when the installation is behind. Version 1.0 added Graphics options and reported reduced VRAM use, while version 1.0.2 addressed performance with AMD or NVIDIA overlays. Record the installed version before comparing settings.
Compare the machine with the Steam requirements before treating a setting as a fix. Steam publishes separate Windows and SteamOS plus Linux rows, so use the row for the installed platform and retain any configuration gap in the report. The requirements are comparison thresholds, not a promised frame-rate target.
- Let Steam finish the current game update and confirm
v1.0.2on the title screen. - Record the platform, CPU, GPU, RAM, display mode, resolution, refresh rate, mod and overlay state, average FPS, and repeatable route.
- If the machine falls below a published requirement, keep that limitation in the report; the requirements do not promise a fixed FPS target.
Remove mod and file uncertainty safely
Close the game and copy the save you will use for testing before changing a modded installation. For MOMI-managed mods, use the v0.15.2 installer documentation and its Uninstall control, then test a temporary or copied save; another loader or individual mod must follow its own author's removal instructions. Record the installed versions first, because restoring the test means reinstalling those same compatible versions rather than guessing which folder to put back.
After the documented mod rollback, restart the computer and open Steam. In the Library, open Fields of Mistria Properties, choose Installed Files, and run Verify integrity of game files, then let the process finish without another system-intensive job running. Verification checks the installation and does not restore a save or remove data that a mod has already written into one.
Run the same route with the unmodded, verified installation. If the symptom disappears, add the recorded mods back one at a time and stop at the first repeatable return; undo that test by using the same documented Uninstall action again. If it remains, leave mods out while testing official display settings so two variables do not move together.
Test only the published graphics combinations
NPC Studio's troubleshooting page gives a specific sequence, and each trial is reversible through the values recorded at the start. On Windows, first open Graphics Settings, add the Fields of Mistria executable if needed, choose Options, and select High performance so a laptop does not choose a power-saving GPU. If the result is worse or unchanged, restore the previous Windows preference before moving on.
Use the in-game Graphics menu for the next tests. Apply one complete combination, relaunch if the game asks, and repeat the same route before trying the next combination. Restore the original group when a trial fails, because mixing half of one preset with half of another gives no useful comparison.
- Turn VSync On or Adaptive and use Fullscreen. Adaptive appears only when the graphics hardware supports it.
- If that fails, set VSync Off, Frame Rate Cap 60 FPS On, Snap Frame Rate Off, and keep Fullscreen.
- Return Brightness and Saturation to the middle default values, then test again.
- Test the maximum In-Game Scale allowed at the current resolution.
- Lower resolution or use a smaller window as a later test; NPC Studio also suggests Smooth Camera Tracking Off with that lower-resolution trial.
NPC Studio also publishes a last-resort group with VSync Off, Snap Frame Rate Off, and Frame Rate Cap Off, while warning that it will generally be very stuttery. Leave that group for the end because it can make the symptom worse. For the two earlier groups, record a new horizontal seam as tearing and restore the complete original group instead of calling it a successful stutter fix.
Update through official channels and report the result
Install operating-system updates through the platform vendor and obtain the graphics driver from the GPU or computer manufacturer's official support channel. NPC Studio names an up-to-date computer and graphics driver as the first performance check, and the 1.0.2 known-issues note repeats that advice. Keep the previous driver installer or the vendor's documented rollback route available, reboot when required, and rerun the same clean baseline before changing another setting.
If the problem remains, open Steam Help and copy System Information as the developer form requests. Submit the platform, CPU, GPU, RAM, controller scheme, title-screen version, mod state, average FPS, exact symptom, and repeatable steps; mention rain, menus, scene changes, overlays, or a particular save only when the same test reproduces that link. Attach only the files requested by the current form.
Stop after the documented checks and keep the clean test record. Registry edits, disabled security software, random launch flags, process priority or affinity changes, save or configuration deletion, driver-cleaner utilities, overclocking, pirated replacement files, and unlisted Proton tweaks have no place in this path. They add risk while making the developer's requested reproduction harder to interpret.