Ready or Not Boiling Point Performance Drop Fix: Optimization Guide for Update 1.4

So, you’ve jumped into Ready or Not after the much-anticipated Boiling Point update (v1.4) and… things are a little rough? The new content and changes, including the intense “No Good Deed” mission and revamped systems, have injected fresh life into the game. But for many players, this “life” came with a significant performance hit. If your FPS has dropped, you’re seeing stutters, or worse—your game is running like a slideshow, you’re not alone. Let’s dive into why this is happening and, more importantly, how you can fix it.

I’m a long-time fan of Ready or Not and know how frustrating it can be when a patch that’s supposed to improve the game ends up causing performance headaches. So here’s my personal guide to getting your game back to its smooth, tactical glory. I’ve combed through Reddit threads, Steam Community discussions, and tech analysis to bring you a complete solution.

Why is Boiling Point Killing Your FPS?

Before jumping into the fixes, it’s worth understanding why Update 1.4 might be putting so much strain on your system. The patch didn’t just bring new content; it overhauled several core systems:

• AI Overhaul – The new suspect AI now calculates morale and tactical retreats, which uses more CPU power.
• Multi-Rail System – The new attachment system increases the number of draw calls, which, in turn, hits your GPU harder.
• Shader Cache Reset – Every major update wipes the old shader cache, leading to stuttery gameplay at first.
• Legacy Configuration Issues – 1.4 changed some core .ini settings, potentially breaking old optimization mods and custom config files.

All of this can combine to create a perfect storm of performance problems, especially if your PC is a bit older or you’re running mods.

Ready or Not Boiling Point: How to Fix SWAT AI Freezing and Pathfinding Issues

Step 1: Clean Slate Method (Best Fix!)

The first step to solving your performance woes is probably the simplest, but also the most effective. Clearing out the junk left over from the old version.

Here’s how:

1. Press Windows Key + R
2. Type %localappdata% and hit Enter
3. Navigate to the ReadyOrNot folder
4. Before deleting, copy the Saved\SaveGames folder to your desktop if you want to keep your campaign progress.
5. Delete the entire ReadyOrNot folder (Yes, delete it!).
6. Launch the game again—Steam will automatically recreate the essential files with the optimized default settings for v1.4.

Why does this work? The update process sometimes leaves old, corrupted files behind, and this includes shader caches and configuration files that didn’t get replaced properly. This clean slate removes those headaches.

Step 2: DX11 vs DX12 – Which is Better for You?

The debate between DirectX 11 and DirectX 12 is one that I’ve seen a lot of players struggle with in 1.4. Here’s the scoop:

• Use DX12 if you have a modern GPU (RTX 30/40 series or AMD’s RX 6000/7000 series) and a multi-core CPU (6 cores or more). DX12 has been optimized for modern hardware, and it performs much better in Boiling Point’s more complex maps.
• Stick with DX11 if you’re on older hardware (GTX 10-series or earlier) or if DX12 keeps crashing your game.

To Switch:
– Right-click on Ready or Not in Steam > Properties > General > Launch Options.
– Add -dx12 or -dx11 to specify the DirectX version you want to use.

Ready or Not Boiling Point Guide: Mastering Shield Melee, Blocks, and 2026 Meta

Step 3: Critical Windows & Driver Optimizations

This one is key—Windows settings and driver versions play a huge role in performance. Here’s what you need to do:

Disable Control Flow Guard (CFG)

CFG is a security feature that can negatively impact performance, especially with DX12. Follow these steps:

1. Open Windows Search and type Exploit Protection.
2. Go to Program Settings.
3. Add ReadyOrNot-Win64-Shipping.exe from your game directory.
4. Find Control Flow Guard and disable it (uncheck “Override system settings”).
5. Restart your PC.

Update Your Drivers

Both NVIDIA and AMD released game-ready drivers for Ready or Not 1.4. If you haven’t updated in a while, make sure you’re on the latest drivers. They address specific issues with shader compilation, which could be the culprit behind your performance drops.

Step 4: Optimize In-Game Settings for v1.4

A lot of players make the mistake of cranking everything down to low in an attempt to get better performance. But here’s the thing—this often shifts the load from your GPU to your CPU, and if your CPU is the bottleneck, this will make the stuttering worse. Here’s my optimized list:

• Resolution Scale: 100% (Use DLSS/FSR instead of lowering this).
• Texture Quality: High (If you have 8GB+ VRAM).
• Shadow Quality: Medium (Shadows can kill FPS in 1.4).
• Post Processing: Low (Reduces blur and improves clarity).
• Anti-Aliasing: High (Important for spotting suspects from afar).
• Mirrorwand/Helmetcam FPS: 30 FPS (Capping this helps save resources).
• Bounce Light: Off.
• World Decals: Medium (Helps with performance without losing too much detail).

Step 5: Dealing with Mods Breaking Performance

If you’re using mods, especially from Nexus Mods or Mod.io, the 1.4 update may have broken them. Even simple cosmetic mods can cause performance hits due to script errors running in the background. Here’s how to clean up:

1. Go to your Paks folder.
2. Delete any files that don’t start with WindowsNoEditor.
3. If you’re running old “Better Performance” mods from 2024-2025, delete them. They’re outdated and no longer effective with the new engine.

Step 6: Advanced Engine.ini Tweaks (For Enthusiasts)

If you’re a bit of a tech-savvy player, here are some manual tweaks that can help push performance further.

1. Navigate to:
%localappdata%\ReadyOrNot\Saved\Config\WindowsNoEditor\Engine.ini
2. Add these lines at the bottom:

[/Script/Engine.RendererSettings]  
r.SceneColorFringeQuality=0  
r.MaxAnisotropy=8  
r.GrainQuantization=0  
r.VariableRateShading.Type=1

Note: The r.VariableRateShading.Type=1 line can give a 10-15% FPS boost on compatible GPUs by reducing shading detail in less important areas of the screen.

Performance Comparison: Before vs. After

Here’s how the fixes stack up (using an RTX 3070 / Ryzen 5600X):

Final Thoughts

The Ready or Not Boiling Point update is one of the most exciting changes to the game, but it comes with some technical growing pains. By following this guide, you can optimize your system and reclaim lost performance. And with VOID Interactive releasing regular hotfixes, it’s worth keeping an eye out for additional patches that might fix specific hardware issues.

Good luck, and I hope you can get back to tactical gameplay without those annoying stutters!

Ready or Not: Max FPS on Low-End PCs – It’s Possible!