MSII Guide
Menu
Performance

Mortal Shell II Frame Drops & Stutter Fix – PC Performance Guide (2026)

Published 2026-08-20 · Updated 2026-09-02

Fix Mortal Shell II traversal stutter, low FPS, cutscene crashes, and input delay with tested settings, NVIDIA/AMD tweaks, Windows optimizations, Steam launch options, and a copyable support report.

Accuracy note: Source-backed and checked 2026-09-02. Patch-sensitive values are excluded unless verified.

Interactive diagnostic

Start with the symptom, not a random settings list

Choose what actually happens. The tool produces a safe first-pass test order and a report you can paste into Steam or support.

Your safest test order

  1. Repeat the route twice and note whether only the first traversal or camera turn hitches.
  2. If a driver was changed immediately before the issue, compare the current stable driver with the previously stable version; do not change several variables together.
  3. Record resolution, display mode, preset, frame cap, upscaler, driver, and the exact test route.
  4. Restart once, verify Steam files, close nonessential overlays, and repeat the same route before changing more settings.
Open the copyable bug-report template
Mortal Shell II performance report
Game version: not recorded
Hardware: not recorded
Symptom: Traversal stutter
Occurs: Entering a new area
Resolution / display mode:
Preset / upscaler / frame generation:
Frame cap / V-Sync / VRR:
Driver version:
Repeatable route or cutscene:
Expected result:
Observed result:
Changes tested one at a time:

Sources

Checked on 2026-09-02. Store details and balance may change after patches.

Quick Wins: Settings That Help Most Players

These adjustments are reported by the community and early testers as the most reliable first steps. Change them one at a time and retest in the same scene. 1. Lower Shadow Quality to Medium or Low — shadows are consistently the most expensive setting in Unreal Engine 5 titles, and reducing them often yields 10–20 FPS gains depending on GPU. 2. Disable Motion Blur and Depth of Field — both add GPU cost and reduce clarity during fast camera movement, making stutter feel worse even when the frame rate is stable. 3. Set Frame Rate Limit to 60 (or your monitor refresh rate) — an uncapped frame rate causes uneven frame pacing on many systems. A stable 60 FPS feels smoother than an erratic 45–90 range. 4. Turn off Film Grain and Chromatic Aberration — these are post-processing effects that add noise without improving gameplay readability. 5. Set View Distance to Medium — in Mortal Shell II's compact open world, high view distance rarely provides tactical benefit but increases CPU and GPU load during traversal. 6. Use Fullscreen (not Borderless Windowed) if you are on a single-monitor PC setup — exclusive fullscreen reduces input latency and overhead on most DirectX 12 titles. After each change, test the same route: load a save, sprint through a populated outdoor area for 30 seconds, and note whether stutter, hitches, or FPS drops persist. Do not change multiple settings simultaneously or you will not know which one mattered.

Week 1 and PC Hotfix 3: Frame Generation and Shader Checks

Checked on 2026-09-02. The official Week 1 Update says frame generation was reworked so it applies after a reload instead of conflicting in real time, and that NVIDIA frame generation should be selectable on a wider range of cards. The same notes say a significant hitch shortly after the shader compilation screen was fixed by moving that work into the menu. The September 1 PC Hotfix 3 then names a narrower fix for bugs involving FSR frame generation and opening the menu map. If performance became worse after either update, first remove third-party mods, verify the game files, restart, and retest with frame generation off. A developer Steam post also says engine.ini must not be read-only when updating, because a locked file can prevent the update from writing required settings. Treat frame generation as a reversible test, not a required fix.

Recommended Settings by Hardware Tier

These presets are starting points based on the retail minimum specification (RTX 2060 SUPER / RX 6600) and early community testing. Adjust individual options upward if your hardware is stronger and downward if you are below the minimum. Low-end (GTX 1060 6 GB / RX 580 / equivalent): - Display Mode: Fullscreen - Resolution: 1920×1080 - Frame Rate Limit: 60 - Shadow Quality: Low - Anti-Aliasing: Low or Medium (TSR or FXAA) - Texture Quality: Medium (reduce if VRAM is under 6 GB) - View Distance: Low - Effects Quality: Low - Post-Processing: Low (disable Motion Blur, Film Grain, DoF, Chromatic Aberration) - V-Sync: Off (use a frame-rate cap instead) Mid-range (RTX 2060 SUPER / RTX 3060 / RX 6600 / RX 6650 XT): - Resolution: 1920×1080 or 2560×1440 (test 1080p first if stutter occurs) - Frame Rate Limit: 60 or 120 to match your monitor - Shadow Quality: Medium - Anti-Aliasing: Medium (TSR) - Texture Quality: High - View Distance: Medium - Effects Quality: Medium - Post-Processing: Medium (still disable Motion Blur and Film Grain) - V-Sync: Off High-end (RTX 3070+ / RX 6700 XT+ / RTX 4070+): - Resolution: 2560×1440 or 3840×2160 - Frame Rate Limit: 120 or 144 - Shadow Quality: High or Epic - Anti-Aliasing: High (TSR or DLSS/FSR if available in your build) - Texture Quality: Epic - View Distance: High - Effects Quality: High - Post-Processing: High (disable Motion Blur if you prefer clarity) If your build shows DLSS, FSR, or XeSS options, test them on Quality or Balanced first. These upscalers can recover 15–30% GPU headroom, but the exact option and quality setting depend on which vendor integration exists in your current patch. Record the upscaler name and setting alongside your FPS observation.

NVIDIA Control Panel and AMD Settings

GPU driver settings outside the game can affect latency, pacing, and frame delivery. Apply these one at a time and retest the same scene. For NVIDIA (GeForce 10 series and newer): 1. Open NVIDIA Control Panel → Manage 3D Settings → Program Settings → Add MortalShell2-Win64-Shipping.exe. 2. Set Power Management Mode to Prefer Maximum Performance — prevents the GPU from downclocking during traversal. 3. Set Low Latency Mode to Ultra or On — reduces render queue depth, which can make input feel more responsive. 4. Set Vertical Sync to Off (let the in-game frame cap handle pacing). 5. If you are using DLSS or TSR, leave Image Scaling and Antialiasing settings at Application-controlled. 6. Disable Background Application Max Frame Rate if you stream or capture, as it can interfere with frame pacing. For AMD (RX 500 series and newer): 1. Open AMD Software → Gaming → Mortal Shell II (or add the .exe). 2. Set Radeon Anti-Lag to Enabled — reduces input latency. 3. Set Radeon Chill to Disabled unless you specifically want a temperature cap. 4. Set Radeon Image Sharpening to Off if you are already using an in-game upscaler (FSR or TSR) to avoid double sharpening. 5. Set Tessellation to Override Application Settings and reduce the level to 8× or 16× if you observe GPU-bound stutter in dense areas. After changing driver settings, restart the game. Driver changes often do not apply to a running process.

Windows System Optimizations

Several Windows behaviors compete with the game for CPU, memory, disk, and network bandwidth. Test these changes one at a time rather than applying all at once. 1. Enable Game Mode: Windows Settings → Gaming → Game Mode → On. This prevents Windows Update and some background notifications from stealing focus during gameplay. 2. Set Power Plan to High Performance or Ultimate Performance (desktop PCs): Control Panel → Power Options. On laptops, use the best-available performance plan and ensure the machine is plugged in. 3. Disable Fullscreen Optimizations for the game executable: right-click MortalShell2-Win64-Shipping.exe → Properties → Compatibility → check 'Disable fullscreen optimizations.' This can reduce input latency on Windows 10 and 11. 4. Close unnecessary background applications before playing: browsers with video tabs, RGB software, chat clients, and game launchers other than Steam. Use Task Manager to identify processes consuming CPU, RAM, or disk during gameplay. 5. Ensure the game is installed on an SSD with at least 20 GB of free space beyond the 70 GB requirement. Hard disk drives cause traversal stutter in open-world Unreal Engine 5 games because texture and mesh streaming cannot keep up. 6. Disable Xbox Game Bar if you do not use it: Windows Settings → Gaming → Xbox Game Bar → Off. It runs a background capture process that can interfere with frame pacing. 7. Check Windows Update history for pending restarts or driver updates. A system waiting to finish an update can degrade gaming performance.

Steam Launch Options That Help

Steam launch options are passed to the game executable before it starts. Right-click Mortal Shell II in Steam → Properties → General → Launch Options. Test one at a time. -dx12 Forces DirectX 12 mode explicitly. The retail game already uses DX12 by default, but this option ensures the correct renderer if a fallback ever activates. -USEALLAVAILABLECORES Tells Unreal Engine to use all CPU cores for rendering. This can help on modern multi-core processors, though the benefit varies by CPU architecture. -high Sets the game's process priority to High in Task Manager. This reduces the chance of background tasks preempting the render thread, but it should not be combined with heavy background workloads. -fps 60 An alternative frame cap that applies earlier in the startup sequence than the in-game limiter. Useful if the in-game limiter feels less stable. Do not use -malloc=system or -heapsize unless an official support agent provides them. These memory-related flags can cause instability in Unreal Engine 5 titles when set incorrectly. Remove launch options one at a time if you experience new crashes after adding them.

Fix Common Crash Scenarios

Patch 86328 and Patch 86845 fixed several common crashes, but players still report specific scenarios. Use this symptom-based approach before trying riskier workarounds. Crash on startup or before the menu: - Update to the latest GPU driver (stable branch, not beta). - Verify game files in Steam (right-click → Properties → Installed Files → Verify Integrity). - Temporarily disable all overlays: Steam, Discord, GeForce Experience, MSI Afterburner, and any capture software. - Check whether a specific USB device (controller, headset, RGB peripheral) is connected; disconnect non-essential devices and retest. Crash during cutscenes: - Lower resolution or the in-game upscaler setting (TSR/DLSS/FSR) before the cutscene begins. A developer response in the beta suggested this workaround for one cutscene crash, and players report it still helps in the retail build. - Disable Motion Blur and Film Grain specifically; these post-process effects can trigger driver timeouts during pre-rendered sequences. - Cap the frame rate to 60 before entering the cutscene area. Crash when entering a new area (loading screen freeze or CTD): - Ensure at least 20 GB of free SSD space. Unreal Engine 5's texture streaming requires headroom for temporary files. - Close browser tabs and background applications that use RAM. - Lower Texture Quality by one tier and retest the same transition. - If the crash repeats, capture the exact location, direction of travel, and whether it occurs on the first visit or on return. Crash after extended play (1+ hours): - This is often thermal or memory-related. Check GPU and CPU temperatures with HWiNFO or similar. If either exceeds 85°C, clean dust filters and improve case airflow. - Restart the game every 2–3 hours as a temporary measure while investigating the root cause. - Reduce Texture Quality and Shadow Quality to reduce VRAM pressure over long sessions.

Display and Refresh Rate Setup

A mismatched refresh rate, V-Sync implementation, or frame-cap combination can make a stable frame rate feel stuttery. 1. Set your monitor to its native refresh rate in Windows: Settings → System → Display → Advanced Display → Refresh Rate. 2. In-game, disable V-Sync and use the in-game Frame Rate Limit instead. V-Sync in DirectX 12 titles often adds input latency and can cause uneven pacing when the frame rate drops below the refresh rate. 3. If you have a variable refresh rate monitor (G-Sync or FreeSync), enable it in the NVIDIA/AMD driver and keep the in-game frame cap 3–5 FPS below the monitor's maximum (e.g., cap at 141 for a 144 Hz monitor). This keeps the display in its adaptive range and avoids V-Sync-related latency at the ceiling. 4. If you do not have VRR, cap the frame rate to exactly your refresh rate (60, 120, or 144). An uncapped frame rate that oscillates above and below the refresh rate produces visible tearing and judder. 5. Set the in-game Display Mode to Fullscreen if you are using a single monitor. Borderless Windowed adds one frame of latency on Windows 10/11 due to the DWM compositor.

When to Update vs Roll Back Drivers

GPU driver updates can fix game-specific bugs or introduce new ones. Use this decision framework rather than automatically installing every new driver. Update to the latest stable driver if: - You are experiencing a crash or stutter that the GPU vendor's release notes specifically address for Unreal Engine 5 titles. - Your current driver is more than three months old and you are on a recent GPU architecture (RTX 40 series, RX 7000 series). - The developer (Cold Symmetry) or publisher (Playstack) recommends a specific driver version in an official post. Consider rolling back if: - A new driver introduced the problem immediately after installation. - You see reports on the GPU vendor's forum or Reddit of the same driver causing issues in Mortal Shell II or other UE5 games. - The new driver is labeled 'Game Ready' but is less than one week old; early releases sometimes contain regressions. How to roll back safely: 1. Download the previous known-good driver from NVIDIA or AMD's website (not Windows Update). 2. Use DDU (Display Driver Uninstaller) in Safe Mode to remove the current driver completely. 3. Install the downloaded stable driver. 4. Restart and retest the same scene that was problematic. Always note your driver version in any bug report or community post. A version number is more useful than 'the latest driver' because that phrase changes every few weeks.

Distinguish Low FPS, Stutter, and Input Delay

Low average FPS is different from a short hitch while entering a new area, and both are different from delayed-feeling controls or camera smoothing. Use the same route and describe what you see: a consistently low frame rate, uneven frame delivery, a freeze, audio continuing during a visual stop, or an input that arrives late. If possible, note whether the problem appears only during traversal, combat, a cutscene, or after changing a setting. One precise symptom is easier to test than 'the game runs badly.' - Low FPS: The frame counter shows a number lower than your target in most scenes. Usually GPU-bound. Fix by lowering resolution, shadow quality, or effects. - Stutter / hitching: The frame rate is high but briefly drops to a very low number for a fraction of a second. Usually caused by texture streaming, shader compilation, background processes, or disk contention. Fix by moving to an SSD, closing background apps, or lowering Texture Quality. - Input delay: There is a noticeable gap between pressing a button and seeing the action. Usually caused by V-Sync, Borderless Windowed mode, high render queue depth, or controller polling issues. Fix by disabling V-Sync, using Fullscreen, enabling Low Latency Mode, or testing a wired controller.

Build a Settings Test Matrix

Write down the current resolution, display mode, preset, frame limit, upscaler actually shown by your build, ray-tracing state if present, and any frame-generation option if present. Capture a baseline in one repeatable scene. Change a single option, restart the game if the menu requests it, and repeat the scene. Keep the change only if the symptom improves without creating unacceptable image quality or latency. This process is slower than copying a preset screenshot, but it produces an answer for your hardware and current patch. Example test matrix: Test 1 — Baseline: 1080p, Fullscreen, Medium preset, TSR Medium, 60 FPS cap, Motion Blur OFF. Result: 58 FPS average, stutter on area transition. Test 2 — Changed: Shadow Quality Low (only change). Result: 62 FPS average, same transition stutter. Test 3 — Changed: Texture Quality Low (only change). Result: 64 FPS average, transition stutter reduced. Conclusion: Transition stutter is texture-streaming related, not GPU-render related. Next test: move game to faster SSD or lower View Distance. Keep this matrix in a text file. It makes bug reports more precise and prevents you from retesting the same combination after a patch.

Check Overlays and Background Contention

Recording software, performance overlays, RGB utilities, browser video, game launchers, and update services can compete for CPU, GPU, memory, storage, or hooks into the render path. Close nonessential tools for one controlled test rather than permanently uninstalling everything. If the problem disappears, re-enable one tool at a time. Also confirm the game is installed on an SSD with sufficient free space and that an operating-system or storefront download is not saturating the disk during traversal. Common culprits that cause stutter in UE5 titles: - Discord overlay and its in-game notifications - GeForce Experience Instant Replay and overlay - MSI Afterburner / Rivatuner Statistics Server (RTSS) — frame limiting via RTSS can conflict with in-game limiters - Steam overlay web browsing - Wallpaper Engine or animated desktop backgrounds - Browser tabs playing video or using hardware acceleration - Windows Search indexing running on the same drive as the game - Antivirus real-time scanning during executable loading Test by closing every non-essential application and overlay, then reintroduce them one at a time over several play sessions.

Retest After Every Patch

A patch can fix the original problem or change which setting is expensive. Reproduce the baseline before carrying old workarounds forward. If performance improves, remove one workaround at a time and retest. If it worsens, include the previous and current game versions in the report. Do not compare a quiet indoor scene before the patch with a crowded outdoor fight afterward; performance comparisons require the same route, camera movement, weather, enemies, and settings. After Patch 86845 specifically: - The file reorganization should make future patches smaller, but it does not directly improve frame rate. - Target steering changes may affect CPU load slightly during combat; retest your combat baseline. - Cyclic inventory navigation is a UI change, not a performance change. - Sprint camera shake is a comfort setting, not a GPU setting. After the Week 1 Update: - Rebuild your baseline before keeping old shader-cache or frame-generation workarounds. - Test the new Increased Geometry Budgets option only if you have spare video memory; it is off by default. - If frame generation looks broken, remove mods, make engine.ini writable, verify files, and retest frame generation off before changing driver-wide settings. After PC Hotfix 3: - If the specific failure involved FSR frame generation while opening the menu map, retest that exact sequence after updating. - Record whether the same map-open problem happens with FSR frame generation off. - Do not treat the hotfix as proof of a universal FPS gain or a complete frame-generation repair. If you had a working configuration before a patch and it broke after, preserve the old settings file (if you backed it up) and report the regression with both patch numbers and your test matrix.

Related guides

Frequently Asked Questions