You’ve already lowered the graphics preset. You’ve updated your drivers. But in CONTROL Resonant, the moment a Dancer pulls up, your frame rate tanks. That’s because combat performance isn’t about raw resolution or texture quality — it’s about how the engine handles shader compilation, memory pressure, and API overhead. Here are six fixes that actually target those bottlenecks.
1. Force a Specific DirectX Version
The game defaults to whatever your system picks. That’s often the wrong choice. By adding a launch option, you can force the rendering API that works best for your hardware.
Combat performance isn't about raw resolution or texture quality — it's about how the engine handles shader compilation, memory pressure, and API overhead.
Open Steam, right-click CONTROL Resonant → Properties → General. In the launch options field, type one of these:
-dx11codecodecodecodecodecode — Most stable. Lower peak FPS but fewer hitches.-dx12codecodecodecodecodecode — Higher frame-rate ceiling, but can introduce stutter on systems with weaker CPUs or memory bandwidth.-d3d11codecodecodecodecodecode — Fallback. Forces an older API path. Use only if the other two crash.
Test each one in a combat-heavy area. DX11 usually wins for smoothness, even if it caps FPS slightly below DX12. The table below shows the tradeoffs clearly.
| Launch Option | Typical FPS (Combat) | Stutter Risk | Best For |
|---|---|---|---|
| -dx11 | Stable 60–90 | Low | Older GPUs (GTX 1060, RX 580) |
| -dx12 | 80–120+ | Medium | Newer GPUs with good CPU (RTX 3060+) |
| -d3d11 | 50–70 | Very low | Crashing with the other two |
Expected outcome: If you were seeing micro-stutter only during combat, switching to DX11 often resolves it entirely.
2. Clear the DirectX Shader Cache
Stale or corrupted shader cache is the #1 cause of combat stutter that looks like a GPU bottleneck. The game recompiles shaders on the fly if it finds bad cached data.
Search Windows for Disk Cleanup. Select your game drive (usually C:). In the list, check only DirectX Shader Cache. Uncheck everything else. Click OK → Delete Files.
Why it works: Each time you enter a new combat zone with different enemy types or particle effects, the engine pulls from the cache. If that cache is corrupted, it stalls. Clearing forces a clean rebuild — one-time cost, permanent gain.
Expected outcome: The first load after clearing will be longer. After that, combat FPS dips by 30% or more should disappear.
3. Increase Virtual Memory
“Out of video memory” errors aside, VRAM pressure causes severe frame drops when the card runs out of dedicated memory. The game spills into system RAM, but the default paging file is often too small.
Search View advanced system settings → Settings (under Performance) → Advanced → Change. Uncheck Automatically manage paging file size for all drives. Select the drive where the game is installed. Choose Custom size and enter:
- Initial size: 12288 MB (12 GB)
- Maximum size: 24576 MB (24 GB)
Click Set → OK. Restart your PC.
Expected outcome: If your GPU has 6 GB or less VRAM and you play at 1440p or above, this alone can eliminate the sudden FPS halving that happens when textures stream in during combat.
4. Disable All Rendering Hooks (Overlays)
Steam overlay, Discord overlay, Nvidia GeForce Overlay, Xbox Game Bar, MSI Afterburner, RivaTuner — these hook directly into the rendering pipeline. In CONTROL Resonant, the anti-cheat layer (if present) or the renderer itself can conflict with these hooks, especially during combat when draw calls spike.
Disable every overlay you can find. For Steam: right-click the game → Properties → uncheck Enable Steam Overlay while in-game. For Discord: go to Settings → Overlay and disable. For Nvidia: open the Nvidia app → Settings → turn off overlay. Also close MSI Afterburner and RivaTuner entirely.
Why combat specifically: Boss fights with multiple effects (The Former, Dancer) push the renderer into high-gear. Overlays add driver-level latency that manifests as sudden FPS drops.
Expected outcome: Gains of 10–20 FPS in hectic scenes are common. If you see no difference, you can re-enable one by one.
5. Turn Off Hardware-Accelerated GPU Scheduling
Windows 10/11 feature HAGS, which lets the GPU manage its own video memory. Sounds good, but in some DX12 titles — CONTROL Resonant included — it introduces frame-time spikes under load.
Search Graphics settings in Windows. Click Change default graphics settings. Toggle Hardware-accelerated GPU scheduling to Off. Restart your PC.
Expected outcome: Smoother frame times, especially in fights with lots of particle effects. You may lose 3–5 FPS on average, but the stutter that made those FPS feel unplayable goes away.
6. Roll Back to an Older GPU Driver
Newer drivers are not always better for a specific game. A driver that launched after CONTROL Resonant might have added features that hurt performance. Or the driver you updated to last week caused the problem.
Go to your GPU vendor’s website (Nvidia, AMD) and download the previous driver version. Use clean installation (Nvidia) or factory reset (AMD) options during install. For Nvidia: select Custom → check Perform a clean installation. For AMD: the checkbox appears in the installer.
Expected outcome: If combat FPS started dropping after a driver update two weeks ago, rolling back should restore the old behavior. This is trial-and-error, but it costs only a few minutes.
These six adjustments skip the obvious checklist and target the engine-level causes of combat stutter. One caveat: if you’re running on an HDD instead of an SSD, none of these will fix texture streaming delays. Move the game to an SSD first, then revisit this list.
