The Dead We Knew Stuttering Fix: How to Optimize Performance on RTX 4060
There is something especially annoying about stuttering in an open-world survival game. A low average FPS is one thing—you can usually lower a few settings and move on. But when THE DEAD WE KNEW: Open World Survival suddenly freezes for a fraction of a second while you are running through a forest, entering a building, or trying to escape a group of zombies, it can completely ruin the experience.
That is particularly noticeable on an RTX 4060. NVIDIA’s card is still a very capable choice for 1080p gaming and can handle plenty of modern titles at 1440p with the right settings. The problem is that large survival games put unusual pressure on both GPU memory and system memory because the world is constantly loading new textures, objects, vegetation, lighting effects, and other assets as you explore.
THE DEAD WE KNEW has exactly the kind of design that can expose those weaknesses. The huge map, hundreds of explorable locations, changing weather, dynamic fog, and zombie encounters mean that your PC is rarely rendering the same scene for very long. In my experience with open-world games, traversal stuttering can be much more distracting than simply having a lower frame rate, so the goal here is not just to chase the biggest FPS number. It is to make frame delivery feel consistently smooth.
Best Graphics Settings for THE DEAD WE KNEW: Open World Survival on GTX 1070
Why THE DEAD WE KNEW Can Stutter on an RTX 4060
Before changing every graphics option in sight, it helps to understand what is actually causing the problem. Stuttering in an open-world survival game is rarely caused by one setting alone. More often, several small bottlenecks appear at the same time when the engine has to stream a large amount of new information into memory.
The first thing I would watch on an RTX 4060 is VRAM usage. The card’s 8GB VRAM is perfectly reasonable for many games, but modern open-world titles can consume it surprisingly quickly when textures, shadows, foliage, and environmental effects are pushed too high. Once memory pressure becomes excessive, you can start seeing inconsistent frame times instead of simply losing a few FPS.
Shader compilation is another common culprit. When the game encounters a particular visual effect or combination of materials for the first time, the engine may need to prepare shaders. That can create a brief hitch, especially when you enter a new area or encounter a new weather effect. If the game is also streaming new world assets from storage at the same moment, the result can be a noticeable micro-stutter.
There is also the CPU side of the equation. A dense survival world has to keep track of vegetation, NPCs, zombies, physics, buildings, loot, and other interactive objects. Even when your GPU isn’t completely maxed out, the processor and storage system can still become part of the frame-time problem.
The Best Graphics Settings for an RTX 4060
I would start with the game’s own graphics settings before touching Windows or NVIDIA Control Panel. This is important because aggressive driver tweaks cannot compensate for unnecessarily high in-game settings. The RTX 4060 performs much better when you give it a sensible workload instead of trying to force every option to Ultra.
| Setting | Recommended Option | Why |
|---|---|---|
| Display Mode | Fullscreen | Can provide more consistent performance and frame pacing. |
| Resolution | 1080p or 1440p with DLSS | Choose based on your monitor and desired FPS. |
| Texture Quality | Medium or High | Helps avoid unnecessary VRAM pressure. |
| Shadow Quality | Medium | Reduces GPU workload without destroying visual quality. |
| Fog Quality | Medium | Useful during demanding weather and fog sequences. |
| Foliage Density | Medium | Can reduce CPU and GPU workload in dense outdoor areas. |
| View Distance | High | Keeps exploration looking good without the cost of Ultra. |
Textures are the setting I would be most careful with. It is tempting to use the highest texture preset because textures often have a relatively small effect on raw FPS. The problem is that they consume VRAM, and VRAM pressure can contribute to traversal stutters. High-quality textures are still possible on an RTX 4060, but I would avoid the maximum preset if you are already experiencing hitching.
Shadows and foliage are also worth lowering. A forest full of trees may look fantastic at maximum settings, but the difference between High and Medium is often much less noticeable while actually playing than it appears in a screenshot. If Medium foliage gives you more consistent frame times when sprinting across the map, that is a trade-off I would happily take.
Don’t Ignore the Fog Setting
Fog deserves special attention because it is not simply another cosmetic effect in a survival game. When weather changes and visibility drops, the game can potentially be dealing with additional lighting, environmental effects, and gameplay activity at the same time. If your system already struggles when moving through dense areas, a very high fog setting can make those moments considerably worse.
Personally, I would rather keep fog at Medium and have stable frame delivery than crank it to Ultra just to make the atmosphere slightly prettier. The atmosphere of THE DEAD WE KNEW comes from much more than one graphics option anyway. Stable performance makes the entire world feel more immersive.
Use DLSS the Right Way
This is where the RTX 4060 has a significant advantage. NVIDIA’s modern features can make a big difference in demanding games, especially when you are trying to play at 1440p. If THE DEAD WE KNEW offers DLSS Super Resolution and Frame Generation, they are worth experimenting with rather than automatically leaving them disabled.
- 1080p: Start with DLSS Quality.
- 1440p: Try DLSS Quality first, then Balanced if you need additional performance.
- Frame Generation: Enable it if the base frame rate is already reasonably stable.
- NVIDIA Reflex: Enable it when available, particularly when using Frame Generation.
There is one important detail here: Frame Generation is not a magic fix for severe stuttering. It can make motion look much smoother, but it does not eliminate every underlying CPU, storage, or asset-streaming problem. If the game repeatedly freezes because it is loading new assets, generating more frames on top of that problem will not necessarily solve the root cause.
For that reason, I would first make sure the game feels reasonably consistent with Frame Generation disabled. Once the base performance is stable, enabling Frame Generation can be an excellent final step for a smoother-looking experience.
NVIDIA Control Panel Settings Worth Trying
If the in-game settings have not solved the issue, it is worth checking the NVIDIA Control Panel. You do not need to change dozens of options. In fact, I would avoid random ‘FPS boost’ configurations that change everything at once because they make troubleshooting much harder.
Open NVIDIA Control Panel → Manage 3D Settings → Program Settings and add the game’s executable. From there, a few settings are worth considering.
Power Management Mode can be set to Prefer Maximum Performance for the game. This can help prevent unnecessary clock-speed fluctuations while playing, although it is not guaranteed to fix stuttering on every system.
The Shader Cache is also important. Giving the driver enough storage for shader data can reduce repeated shader-related work. If the game has recently received an update or you changed GPU drivers, clearing an old cache and allowing it to rebuild can sometimes help more than simply increasing its size.
I would also consider using an FPS cap. For example, if your monitor runs at 144Hz and your PC cannot maintain 144 FPS consistently, locking the game to a realistic target such as 90, 100, 120, or 141 FPS can produce a noticeably smoother experience. A stable 90 FPS often feels much better than bouncing between 65 and 120 FPS every few seconds.
Make Sure the Game Is Installed on an SSD
This is one of those boring recommendations that people often skip, but it matters enormously in open-world games. When the engine constantly streams new buildings, textures and environmental objects, storage speed becomes part of the overall experience.
If THE DEAD WE KNEW is installed on an old mechanical hard drive, moving it to an SSD should be one of the first things you try. You may not suddenly gain a massive amount of average FPS, but asset streaming and loading behavior can improve significantly. In games where the biggest problem happens while traveling through the world, that distinction is extremely important.
Ideally, keep both Windows and the game on a reasonably fast SSD with plenty of free space. I would also avoid filling the drive almost completely because maintaining some free storage gives the operating system and applications more room to work efficiently.
Check Windows Settings Too
Windows can also influence how smoothly a demanding game behaves. One setting worth testing is Hardware-Accelerated GPU Scheduling. You can find it under Windows Graphics settings. If it is available on your system, enable it, restart Windows, and see whether frame pacing improves.
I would also check your virtual memory configuration. Modern survival games can use a surprising amount of system RAM, particularly during long sessions. If Windows has an appropriately configured pagefile on a fast SSD, it has more flexibility when memory usage spikes.
There is no need to obsess over manually assigning an enormous pagefile, though. For most users, allowing Windows to manage virtual memory automatically is perfectly reasonable. The important part is making sure you have enough free storage and that the pagefile is not sitting on an extremely slow drive.
Try Disabling Fullscreen Optimizations
This is another troubleshooting step rather than a guaranteed performance upgrade. Find the game’s executable, right-click it, select Properties, open the Compatibility tab, and look for the option to disable fullscreen optimizations.
Some systems respond positively to this change, while others see no difference at all. That is normal. PC gaming performance is frustratingly hardware-dependent, so I recommend changing one thing at a time and testing the game in the same area afterward.
Clear the DirectX Shader Cache
If stuttering appeared after a graphics driver update or a major game patch, rebuilding the shader cache is definitely worth trying. Corrupted or outdated cached data can sometimes cause strange behavior, especially after the game engine or driver has changed.
Windows includes a simple way to do this. Search for Disk Cleanup, select your system drive, and look for DirectX Shader Cache. Delete that cache and then restart the game.
Do not panic if the first few minutes after clearing the cache are slightly less smooth. The game and driver may need to rebuild shader data again. I would play for a little while before judging the result. If the hitching becomes less frequent after the cache has been rebuilt, you have probably found part of the problem.
What I Would Actually Change First
If I were setting up an RTX 4060 specifically for THE DEAD WE KNEW, I would not spend an hour changing every obscure Windows option before touching the game itself. I would start with the graphics settings, then move outward only if the problem remained.
- Set textures to High rather than Ultra/Epic.
- Drop shadows, fog and foliage to Medium.
- Keep view distance at High.
- Use DLSS Quality at 1080p or 1440p.
- Test Frame Generation after stabilizing base performance.
- Install the game on an SSD.
- Check NVIDIA shader cache and power settings.
- Clear the DirectX Shader Cache if stuttering started after an update.
This approach is much better than blindly lowering everything to Low. Survival games are heavily dependent on atmosphere, and THE DEAD WE KNEW is the kind of game where visual quality is part of the experience. There is usually a sweet spot between maximum graphics and maximum performance, and the RTX 4060 is capable of finding it.
Don’t Chase Average FPS—Watch Frame Times
One of the biggest mistakes I see when people troubleshoot PC gaming performance is focusing exclusively on the FPS counter. Average FPS can look perfectly healthy while the game still feels terrible. If you are getting 80–100 FPS but experience regular half-second hitches, the problem is frame pacing rather than simply a lack of rendering power.
That is why I would pay attention to how the game feels when you move between different areas. Run through a forest, enter a large building, travel toward a town, and play through a foggy encounter. Those situations are much more useful for testing than standing still in one location and watching the FPS number.
Final Thoughts
THE DEAD WE KNEW stuttering on an RTX 4060 does not necessarily mean that your graphics card is incapable of running the game. Open-world survival games are unusually demanding because they constantly combine rendering, asset streaming, AI, physics, weather and gameplay systems. The RTX 4060’s 8GB of VRAM is enough for a good experience when the settings are balanced, but pushing every option to maximum can create unnecessary memory pressure.
The most sensible strategy is to prioritize stable frame times over benchmark screenshots. Medium-to-High settings, sensible DLSS usage, an SSD installation, a healthy shader cache and a reasonable FPS cap can go a long way toward making the game feel smoother. And honestly, when you are trying to survive a zombie attack in thick fog, I would much rather have consistent performance than an extra layer of ultra-detailed shadows that I barely notice while running for my life.
As the game continues to receive updates, performance can also change from one version to another. If a future patch improves shader compilation, asset streaming or memory management, some of these tweaks may become less necessary. Until then, these settings provide a good starting point for RTX 4060 owners who want to explore the world without constantly fighting micro-stutters.








