If you’ve been playing Kingdom Come: Deliverance II and have noticed your frame rate dropping significantly over time, you’re not alone. Many players experience a VRAM leak that can cause performance issues, particularly when playing for extended periods. Fortunately, there are a few steps you can take to slow down this leak and extend your gaming sessions before performance starts to deteriorate. In this guide, we’ll break down what causes the VRAM leak, how to slow it down, and some additional tips to improve your overall gaming experience.
How To Fix VRAM Leaks in Kingdom Come: Deliverance 2
What Causes the VRAM Leak in Kingdom Come: Deliverance 2?
The VRAM leak in Kingdom Come: Deliverance II occurs when certain in-game graphics settings are changed, especially when you enter conversations or cutscenes. During these moments, the game automatically activates additional graphics features, such as sharpening and depth of field effects. This counts as a change in the graphics settings and triggers the VRAM leak.
While the game runs smoothly at first, over time, these changes can cause your VRAM usage to increase dramatically. Eventually, this can lead to significant drops in framerate, making the game almost unplayable after a while. Though this issue is far from uncommon, the good news is that there are ways to mitigate the problem and slow down the VRAM leak before it causes too much disruption to your gameplay.
How to Slow Down the VRAM Leak
While there’s no perfect fix that will completely eliminate the VRAM leak, there are a few steps you can take to delay its onset and improve your gaming experience. Here’s a guide to slowing down the leak and maximizing your playtime before the framerate starts to drop.
1. Create a User.cfg File
The first step is to create a user.cfg file in your game’s directory. This simple file will allow you to tweak some settings that prevent your GPU from running at maximum capacity, which in turn helps slow the VRAM leak.
- Go to your game’s installation directory.
- Create a new text document and rename it to
user.cfg. - Open the file with a text editor (like Notepad).
2. Adjust Graphics Settings via the User.cfg File
Once you’ve opened the user.cfg file, you’ll want to add the following commands to disable some of the graphics features that contribute to the VRAM leak. Copy and paste the following lines into the file:
r_DepthOfField=0
r_sharpening=0
r_HDRBloom=0
r_HDRVignetting=0
These settings will turn off depth of field, sharpening, HDR bloom, and vignette effects, which are triggered during cutscenes or conversations. Disabling these effects prevents unnecessary strain on your VRAM and helps keep the game running more smoothly.
3. Enable V-Sync and Limit Your FPS
After saving the user.cfg file, you can further optimize your game by enabling V-Sync in the game’s settings and limiting the frame rate. Running the game at a higher frame rate than your hardware can handle can quickly stress your GPU and contribute to VRAM leaks. By locking the FPS to a lower value, you can help reduce the load on your system.
For example, if your system is capable of running the game at around 60 FPS, try locking it to 48 FPS. This can make a significant difference in how long it takes for VRAM to reach critical levels, slowing down the performance degradation over time.
4. Lower Your Graphics Settings
In addition to the tweaks in the user.cfg file, you can also adjust in-game graphics settings to lower the overall load on your GPU. Reducing the graphics quality will help to free up VRAM and give your system more room to run the game smoothly.
Focus on lowering specific settings such as texture quality, shadow details, and anti-aliasing. These settings are particularly demanding on VRAM and can contribute to the leak. Also, enabling features like FSR (FidelityFX Super Resolution) or playing at a lower resolution can reduce the overall graphical load.
5. Monitor Your VRAM Usage
It’s always a good idea to keep an eye on your system’s VRAM usage while you’re playing. Tools like MSI Afterburner or HWMonitor can help you track VRAM consumption in real-time. If you notice that your VRAM is approaching its maximum capacity, it might be time for a quick restart to prevent further performance issues.
Additional Tips for Improving Performance
Aside from the changes mentioned above, here are a few more tips that can help extend your playtime before the VRAM leak affects your game:
- Play in Shorter Sessions: While the tweaks above can significantly slow down the VRAM leak, it’s still a good idea to take breaks and restart the game every couple of hours. This prevents the VRAM from reaching critical levels and keeps your system performing optimally.
- Optimize System Performance: Make sure that no background processes are consuming excessive CPU or RAM resources while you play. Close unnecessary programs to free up more system resources for Kingdom Come: Deliverance II.
- Update Graphics Drivers: Keeping your GPU drivers up-to-date ensures that you benefit from the latest performance optimizations and bug fixes, which may help reduce the likelihood of VRAM-related issues.
Conclusion
While Kingdom Come: Deliverance II may have an unresolved VRAM leak, the steps outlined in this guide can help mitigate the issue and improve your overall gaming experience. By disabling unnecessary graphics features, enabling V-Sync, lowering your graphical settings, and monitoring your VRAM usage, you can significantly slow down the onset of performance problems. Although this is not a permanent fix, it can extend your gaming sessions from just 20 minutes to up to 80 minutes or more, depending on your system and settings.
Remember that the game will eventually slow down no matter what, but with these adjustments, you’ll have more time to enjoy the world of Kingdom Come: Deliverance II without constantly worrying about framerate drops.
Last Updated on February 27, 2025
An avid listener of music from a number of countries. Writing is his hobby and passion. A follower of all the latest android and PC games. Not to mention his favorite: Mobile Legends!