Mortal Shell 2 Low FPS & Stuttering Fix: PC Performance Guide

I love games that punish you for making mistakes. I do not love games that punish me because the frame rate suddenly decides to fall off a cliff.

That was basically my experience with Mortal Shell 2 on PC. The game looks incredible, and that is part of the problem. Its dark fantasy world is packed with dense environments, atmospheric fog, heavy lighting, detailed enemies, and all the visual tricks you expect from an Unreal Engine 5 game. When everything is running properly, it can look fantastic. When the engine starts streaming assets or compiling something in the background, though, the experience can become noticeably rough.

And in a Soulslike, that matters.

A random hitch during exploration is annoying. A random hitch when you’re trying to dodge a boss attack is something else entirely.

After messing around with graphics settings, shader caches, synchronization options, Windows settings, and the usual PC troubleshooting tricks, I’ve put together the changes that make the biggest difference. This isn’t about blindly turning every setting to Low and making the game look like it came from 2012. The goal is stable frame delivery without destroying the visual quality that makes Mortal Shell 2 worth playing.

Why Mortal Shell 2 Can Stutter So Badly on PC

Before changing everything at once, it helps to understand what is actually happening.

Mortal Shell 2 relies heavily on Unreal Engine 5 technology. UE5 can produce some spectacular environments, but modern rendering features also put serious pressure on both the GPU and CPU. Asset streaming, shader compilation, lighting effects, volumetric effects, and dense environments can all contribute to inconsistent frame times.

The important word here is frame time.

You can have a counter showing 100 FPS and still feel stutter if individual frames are arriving unevenly. For a game built around dodging, blocking, Harden timing, and precise attacks, smooth frame delivery is much more important than chasing some ridiculous maximum FPS number.

The good news is that you don’t need to change everything here to get a better experience.

1. Start With the Shader Cache

If I had to pick one place to start, this would be it.

Shader compilation is one of those things that can make an otherwise powerful gaming PC feel broken. You can have a high-end RTX card, plenty of RAM, and a modern CPU, yet still experience a nasty hitch when the game encounters an effect it hasn’t prepared properly.

For NVIDIA users, open the NVIDIA Control Panel and head into Manage 3D Settings. Look for Shader Cache Size and, if the option is available on your driver setup, increase the allocation rather than leaving it unnecessarily restricted.

After a major driver update or game update, I also recommend clearing the old DirectX shader cache.

In Windows, search for Disk Cleanup, select your system drive, and look for DirectX Shader Cache. Clear it, reboot the PC, and let the game rebuild what it needs.

Don’t panic if the first launch after doing this isn’t perfect. The cache has to be rebuilt. Give the game some time before deciding whether the change worked.

For AMD hardware, check the shader-cache options inside AMD Software: Adrenalin Edition and use the recommended/optimized setting available for your driver.

2. Don’t Chase FPS at the Expense of Frame Pacing

This is probably the biggest mistake I see with PC optimization.

People see a benchmark going from 80 FPS to 105 FPS and assume the game must feel better. Not necessarily.

For Mortal Shell 2, I would much rather have a consistent 75–80 FPS than bounce between 110 FPS and 48 FPS every time I walk through a new area.

That means you should use a sensible frame-rate target based on your hardware and monitor.

If you’re playing on a 144Hz display, for example, you don’t have to force the game to sit at 144 FPS at all times. A stable cap below the maximum refresh rate can produce a much cleaner experience.

Stability first. Maximum FPS second.

That’s especially true if you’re using VRR technology such as G-SYNC or FreeSync.

3. Be Careful With V-Sync and Frame Generation

This is where things can get messy.

Frame Generation is useful when you already have a solid base frame rate. It is much less impressive when the underlying game is struggling.

My preferred approach is simple: get the native or upscaled base FPS stable first.

If your system is rendering the game at 35–40 FPS and you turn on Frame Generation to make the counter display something much higher, you’re not magically turning those original frames into a high-refresh competitive experience. You’re adding generated frames on top of an already weak foundation. That can mean increased latency, strange visual artifacts, and inconsistent responsiveness.

For a combat-heavy game, I would prioritize responsiveness over benchmark screenshots.

If you’re using Frame Generation, test it only after you’ve established a stable base frame rate.

And don’t automatically stack every synchronization feature together. In-game V-Sync, driver-level V-Sync, Frame Generation, VRR, and an external frame limiter can interact in ways that are different from system to system.

Test one configuration at a time.

4. The Graphics Settings I Actually Recommend

I wouldn’t recommend putting everything on Low.

That’s the lazy optimization method.

Instead, attack the settings that are expensive without providing a huge visual improvement during actual gameplay.

My Starting Preset

• Display Mode: Fullscreen or the most stable fullscreen option available
• Shadows: Medium/High
• Volumetric Fog & Lighting: Medium
• Post-Processing: Medium
• Foliage: Medium
• Motion Blur: Off
• Chromatic Aberration: Off
• Textures: High or Ultra if VRAM allows
• Upscaling: DLSS/FSR Quality as a starting point

The setting I’d experiment with first is Volumetric Fog and Lighting.

It can look beautiful, especially in dark and misty locations, but volumetric effects are exactly the sort of feature that can hammer your GPU when the scene gets complicated.

Lowering it doesn’t suddenly turn the game ugly. In my experience, it is one of those compromises that makes far more sense than destroying texture quality.

Keep Texture Quality High If You Have Enough VRAM

Texture quality is another setting people lower way too quickly.

If your GPU has enough VRAM, high-quality textures can usually be retained while you reduce more expensive effects elsewhere. There’s no reason to turn every visual option down simply because you’re trying to fix a GPU bottleneck.

I’d rather run:

High textures + Medium volumetrics + Medium shadows

than:

Low textures + Ultra volumetrics + Ultra shadows.

The second configuration wastes performance where it matters.

5. DLSS, FSR and TSR: Pick Quality Before Performance

Upscaling is extremely useful here, but I wouldn’t immediately select the most aggressive performance mode.

Start with Quality.

If performance still isn’t where you want it, move to Balanced and compare the difference.

The idea is to reduce the internal rendering workload while keeping the image sharp enough that you don’t constantly notice the reconstruction.

Personally, I’d rather play at a stable 70–80 FPS with a clean Quality upscaling preset than chase 120 FPS with an extremely low internal resolution.

Also keep an eye on thin geometry, distant foliage, and particle effects. Those are often the first places where temporal upscaling starts showing its weaknesses.

6. I Would Avoid Random Engine.ini Tweaks Unless You Know What You’re Changing

This is where PC optimization guides can become dangerous.

Yes, Unreal Engine configuration files contain a huge number of options. Yes, some community tweaks can help specific systems.

But copying a massive block of commands from a random post without understanding what they do is not something I’d recommend.

If you’re editing Engine.ini, make a backup first.

Seriously.

Create a copy of the original file before changing anything. Then make one change at a time. If performance gets worse, you can immediately revert.

This is particularly important with settings related to rendering, shader compilation, streaming, latency, and synchronization. A tweak that fixes one PC can make another PC behave worse.

And don’t assume that a configuration file is automatically “better” simply because it contains more commands.

7. Don’t Ignore Your SSD

This one sounds boring, but it matters.

Modern UE5 games stream enormous amounts of data while you move through the world. If the game is installed on a slow mechanical hard drive, you’re creating another potential bottleneck.

If possible, install Mortal Shell 2 on an NVMe SSD or another fast SSD with plenty of free space.

It won’t magically fix every performance issue. It can, however, remove storage performance from the list of suspects when you’re dealing with asset-streaming hitches.

And honestly, in 2026, there’s little reason to put a demanding UE5 game on an old HDD if you have a modern SSD available.

8. Windows Cleanup Is Worth Doing

Before blaming the game, make sure Windows isn’t creating unnecessary background activity.

• Disable unnecessary Xbox Game Bar recording features if you don’t use them.
• Close browser tabs and applications consuming large amounts of RAM or CPU.
• Disable unnecessary overlays.
• Make sure your GPU driver is current.
• Confirm the game is using your dedicated GPU.
• Enable Hardware-Accelerated GPU Scheduling if it behaves well on your system.
• Restart the PC after major driver or graphics changes.

I would not start randomly disabling Windows security features just because somebody online claims they gained 5 FPS.

Security settings exist for a reason.

If you’re experimenting with something like Control Flow Guard or other exploit-protection options, understand exactly what you’re changing and reverse the setting if it doesn’t help. A tiny theoretical performance gain isn’t worth weakening system protections without a very good reason.

Mortal Shell 2 Weapons Guide: All Melee Weapons and Sidearms Locations

My Recommended Mortal Shell 2 PC Setup

If you don’t want to spend an entire evening benchmarking every individual option, this is where I’d start:

Then play for 15–20 minutes.

Don’t just stand in the same room staring at a wall. Move through different environments, fight enemies, enter areas with heavy effects, and pay attention to the frametime consistency.

That’s where you’ll actually discover whether the changes worked.

Mortal Shell 2 Fast Gold Farming Guide: Best Ways to Get Coins (2026)

The Fix That Made the Biggest Difference for Me

If I had to strip this entire guide down to the essentials, I’d start with the shader cache, lower volumetric effects, use a sensible frame cap, and get the base frame rate stable before touching Frame Generation.

Those changes address the problems I care about most: random hitches, inconsistent frame pacing, and sudden drops during combat.

And that’s really the point.

Mortal Shell 2 doesn’t need to run at an absurd 200 FPS to feel good. It needs to respond when you press the button.

When you’re standing in front of a boss and waiting for the exact moment to Harden, dodge, or counter, you don’t care that your GPU produced a beautiful screenshot at 4K Ultra. You care that the next frame arrives when you expect it to.

That’s why I’d take stable performance over maximum graphics every single time.

Start with the easy changes. Fix the shader cache. Reduce volumetric effects. Use sensible upscaling. Keep textures high if your VRAM can handle them. Avoid relying on Frame Generation to hide a weak base frame rate. Install the game on an SSD. And most importantly, change settings one at a time.

Once you find that sweet spot, stop tweaking.

Go back into the game.

There are monsters to kill.

Mortal Shell 2 DLSS 4.5 Tested | DLAA vs Quality vs Performance on RTX 5090