Fix FPS Drops in Ready or Not

Ready or Not delivers intense tactical shooters with high-fidelity graphics, but many players face frustrating FPS drops and stuttering that disrupt immersion. These issues often stem from unoptimized settings, outdated drivers, conflicting software, or hardware limitations. This guide provides a step-by-step approach to diagnose and resolve performance problems, drawing from community-tested methods and official recommendations to achieve stable frame rates.

Understanding FPS Drops in Ready or Not

Frame per second (FPS) drops occur when your system struggles to render frames consistently, leading to laggy movement and unresponsive controls. In Ready or Not, common culprits include heavy particle effects, complex lighting, AI calculations, and upscaling technologies like DLSS or FSR that can introduce instability. Hardware like mid-range GPUs (e.g., RTX 3060) may dip below 60 FPS on low settings during intense raids. Identifying whether the issue is CPU-bound, GPU-bound, or software-related is key to targeted fixes.

• CPU-bound drops: High AI or physics loads spike usage.
• GPU-bound drops: Textures, shadows, or reflections overload the graphics card.
• Software issues: Overlays, mods, or background processes interfere.

Essential System Preparations

Before diving into game-specific tweaks, ensure your PC is primed for optimal performance. Start with basic maintenance to rule out simple bottlenecks.

Update Graphics Drivers

Outdated or corrupted drivers are a primary cause of stuttering. Perform a clean installation using official tools from NVIDIA or AMD. For NVIDIA, download from their site and select ‘Clean Install’ during setup; AMD users should use the AMD Software to wipe old drivers first. This removes residual files that cause conflicts. Roll back drivers if a recent update introduced issues, as some Ready or Not patches interact poorly with new versions.

Restart and Verify Game Files

Restart Steam and your PC to clear temporary caches. In Steam, right-click Ready or Not, select Properties > Installed Files > Verify Integrity of Game Files. This replaces corrupted files without affecting saves. Avoid running the game immediately after updates—wait for full indexing.

Run as Administrator and Disable Optimizations

Right-click the executable (ReadyOrNot-Win64-Shipping.exe in the Binaries/Win64 folder) and set ‘Run as administrator’. Disable full-screen optimizations via Properties > Compatibility tab. Launch directly from the install folder for better stability.

Optimizing Graphics and In-Game Settings

Ready or Not’s Unreal Engine 4 demands careful balancing of visuals and performance. Prioritize low-to-medium presets while testing changes in a demanding map like Club or Hospital.

Enable NVIDIA Reflex if available to reduce latency. Switch to DirectX 12 via launch options (-dx12) for better multi-threading, but test DX11 if crashes occur.

Advanced Config File Edits

Access config files at %LOCALAPPDATA%\ReadyOrNot\Saved\Config\Windows\GameUserSettings.ini. Edit with Notepad++ for safety—backup first. Key tweaks:

• Set ResolutionQuality=50-67 to downscale rendering.
• DlssQualitySetting=0, FSRQualitySetting=0, FrameGenerationSetting=0 to disable unstable features.
• Under [/Script/Engine.RendererSettings], set r.MotionBlurQuality=0 and r.VSync=0.

Save, set the file to read-only, and restart the game. These changes persist across sessions and can double FPS in bottleneck scenarios.

Eliminating Software Conflicts

Background apps devour resources. Close overlays like Discord, GeForce Experience, or MSI Afterburner—NVIDIA users, disable in-app overlay.

Windows Game Mode and Xbox DVR

Go to Windows Settings > Gaming > Game Mode (off), Captures (disable background recording). This frees CPU cycles previously allocated to recording.

Antivirus and Firewall Exceptions

Add ReadyOrNot-Win64-Shipping.exe to exclusions in Windows Defender (Controlled Folder Access & Firewall) or third-party tools like Norton. Mods cause crashes—delete non-essential files, keeping only pakchunk*.pak (except pakchunk20).

Disable Replays and Demos

Replays generate heavy I/O. Navigate to ReadyOrNot\Content\Movies\Demos, right-click folders > Properties > Security > Deny write access to SYSTEM subfolders.

Hardware-Specific Optimizations

NVIDIA Control Panel Tweaks

Open NVIDIA Control Panel > Manage 3D Settings > Program Settings > Add ReadyOrNot-Win64-Shipping.exe. Set Power Management to ‘Prefer Maximum Performance’, Texture Filtering to ‘High Performance’, and Image Sharpening preview to Performance.

AMD Radeon Software

In Radeon Software, enable Radeon Chill (60-120 FPS cap) and Anti-Lag. Profile the game for custom tuning.

RAM and Storage Check

Ensure 16GB+ RAM; close browser tabs. Move the game to an SSD if on HDD—load times and stutters improve significantly.

Launch Options and Mod Management

In Steam Properties > General > Launch Options, try: -dx12 -USEALLAVAILABLECORES -sm4. Remove mods entirely; delete Mod.io folder and extras. For low-end PCs, add -lowmemory.

Monitoring and Benchmarking

Use MSI Afterburner + RTSS to track FPS, GPU/CPU usage. Aim for <90% usage per core. If GPU maxes at 100% with low FPS, lower settings; if CPU spikes, cap FPS at 60 via RivaTuner.

Common Pitfalls and Troubleshooting

Post-Patch Drops: Wait 24 hours for Steam to propagate fixes, then verify files.
Dedicated GPU: Plug monitor into discrete GPU port; set high-performance plan in Windows Power Options.
Overheating: Monitor temps (<80°C); undervolt or repaste if needed.

Frequently Asked Questions (FAQ)

Why does Ready or Not stutter on high-end PCs?

Unoptimized upscalers or replays; disable DLSS/FSR and demos first.

Does deleting config reset progress?

Yes, but only graphics—reapply tweaks. Backs up manually.

Best settings for RTX 3060?

Medium preset, DX12, Reflex on, upscalers off—expect 80-120 FPS.

Will these fixes work on laptops?

Yes, but plug in charger, use high-performance mode, and ensure discrete GPU.

How to fix crashes with FPS fixes?

Verify files, clean driver install, remove pakchunk20.

Conclusion

Combining these steps—driver updates, config edits, software disables, and targeted settings—can transform Ready or Not from choppy to buttery smooth. Test incrementally, benchmark changes, and report persistent issues to VOID Interactive forums. Stable 60+ FPS awaits for precise SWAT operations.