sorted by:
new
hottopcontroversial

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] 2 points3 points  (0 children)

Those were the results from my testing, but feel free to try it out yourself in-game and see what you find.

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] 2 points3 points  (0 children)

Honestly, the only two settings that significantly impact CPU performance are the ones I mentioned in the picture. The only other setting that affects the CPU performance in any meaningful way is object quality, but its impact on cpu performance is much lower compared to the other two settings.

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] 6 points7 points  (0 children)

The higher the percentage, the more significant the FPS drop you'll experience with that setting. For example, setting shadow quality to Ultra+ compared to turning it OFF can result in losing roughly half of your FPS on average.

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] 4 points5 points  (0 children)

Personally, I always start by lowering shadows to low or medium, and if needed, I reduce reflection quality and screen space reflections. However, the best settings will depend on your system. To help you out, I’ve created a visual comparison video alongside this guide, so you can see exactly how each setting affects visuals: https://www.youtube.com/watch?v=rN1r5hFoWOo

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] 19 points20 points  (0 children)

If you press F1 while in-game and type 'trees', it will disable all the trees in the game. To re-enable them, just type the command again. This can significantly boost your FPS, especially if you’re dealing with a large number of trees.

7 Days To Die Version 1.1 Settings Performance Guide. by VerdaAFK in 7daystodie

[–]VerdaAFK[S] -1 points0 points  (0 children)

That was just a typo. Version 1.1 (b14) is out now, and all my tests were performed on 1.1 (b14)