Welcome to this post This Evil Dead: The Game – Low End PC Optimization Guide was written to be helpful to you, and we genuinely hope that you do.

How to play the game on a relatively weak PC while maintaining a steady FPS and a non-blurred or pixelated visual.

 

 

Foreword

When the devs say: “No optimization for older (or new, lol) hardware!”, I answer: “OK, but I still want to play the game!” Fortunately, games on Unreal Engine 4 can be configured quite simply and intuitively through configuration files that can be opened in notepad. And these are my PC specs (sorry, no money for an upgrade):

• Windows 10 Pro 64-bit
• i5-4430 3.0GHz
• RAM 24GB DDR3
• GTX 660 Ti
• No SSD, only HDD.

P.S. I’m not usually one for triple-A projects, but thanks to UE4 settings I can still play games such as: Grounded, Ghostbusters: Spirits Unleashed and Tales of Arise comfortably thanks to its settings; while with Epic Evil Dead The Game it took quite some effort as I added many parameters at once. Bear in mind these settings may not suit your PC exactly; simply adjust basic parameters accordingly if need be.

Game Settings

Launch the game and go to Video settings. I would recommend to set the Gamma to at least Medium, as some weather conditions can make the game incredibly dark. Also, this video card is already quite old, so I don’t have DLSS settings, so I’ll skip this point.

• Display Mode: Full screen (It really works better in this one).
• Resolution: Of your monitor, for me it’s 1920×1080 (lowering absolutely didn’t change the difference in performance, even tried 720p).
• Resolution Scale & View Distance: Can be ignored, because will still be configured via config files, but in case you’re wondering, distance is the most favorable setting for this game, so it’s definitely desirable to be on high or medium.
• ALL other parameters can be lowered to the minimum possible value (of course, it’s low specs, but don’t be sad, the graphics will be much better than vanilla low ones).

Also uncheck Motion Blur (bleh) and Tessellation, but with Vertical Synchronization — it’s your personal decision. This eats up a piece of FPS, but if you don’t have a COOL GAMING sync monitor, then recommend turning it on, since this game has a console FOV and tears with it look terrible. That’s all, don’t forget to save!

GameUserSettings.ini

This important file for this game is located at:

C:\Users\<User_name>\AppData\Local\EvilDead\Saved\Config\WindowsNoEditor

(AppData is hidden in Windows, but I guess if you have looked at this guide, you know how to make it visible or just open). All parameters in the configuration files must be changed after the game is closed, otherwise they aren’t applied. If any settings have been changed, the game also needs to be restarted. Open GameUserSettings.ini with a standard notepad and look for:

bUseVSync=True or False — is responsible for all the same Vertical Synchronization (just in case).

FrameRateLimit=0.000000 — change the FPS limit to 60.000000 or 30.000000, depending on your preference.

At the end of the file you will see this section, replace it with a new one:

[ScalabilityGroups]

sg.ResolutionQuality=100.000000

sg.ViewDistanceQuality=2

sg.AntiAliasingQuality=0

sg.ShadowQuality=0

sg.PostProcessQuality=0

sg.TextureQuality=0

sg.EffectsQuality=0

sg.FoliageQuality=0

sg.ShadingQuality=0

These settings mirror those found within the game itself, yet can be modified here to lower ones. An interesting quirk of epic settings is that ResolutionQuality cannot reach 100 (but can reach 95), which makes this particular setting impossible to use 100%. On more powerful PCs you may also change various settings from 1 to 3 in order to test performance and save the file by right-clicking, going into Properties, checking Read-only box, then Apply. Doing this prevents changes back into vanilla mode by accident.

Engine.ini

In the same folder is an equally important file Engine.ini and this is the place where most of the game’s graphics were configured (didn’t have to mess around like that with other games).

Open it with notepad and add this at the very end:

[SystemSettings]

bSmoothFrameRate=False

r.ScreenPercentage=100

r.SceneColorFringeQuality=0

r.PostProcessAAQuality=1

r.DefaultFeature.AntiAliasing=2

r.DefaultFeature.MotionBlur=False

r.MotionBlurQuality=0

r.MotionBlur.Max=0

r.BlurGBuffer=0

r.AmbientOcclusionLevels=0

r.AmbientOcclusionRadiusScale=1.7

r.DepthOfFieldQuality=0

r.RenderTargetPoolMin=300

r.LensFlareQuality=0

r.EyeAdaptationQuality=1

r.DefaultFeature.Bloom=0

r.BloomQuality=4

r.LightShaftQuality=0

r.FastBlurThreshold=0

r.Upscale.Quality=1

r.Tonemapper.GrainQuantization=0

r.TonemapperQuality=0

r.LightFunctionQuality=0

r.ShadowQuality=0

r.Shadow.CSM.MaxCascades=1

r.Shadow.MaxResolution=512

r.Shadow.RadiusThreshold=0.1

r.Shadow.DistanceScale=0.6

r.Shadow.CSM.TransitionScale=0

r.DistanceFieldShadowing=0

r.DistanceFieldAO=1

r.TranslucencyLightingVolumeDim=24

r.RefractionQuality=0

r.SSR.Quality=0

r.SSS.SampleSet=0

r.SSS.Scale=1

r.SceneColorFormat=3

r.TranslucencyVolumeBlur=0

r.MaterialQualityLevel=1

r.EmitterSpawnRateScale=0.75

➤ Delete the line bSmoothFrameRate=False if you set FPS to 30 or 60 in the previous file.

It’s also recommended to add this at the end (for more precise mouse control):

[/script/engine.inputsettings]

bEnableMouseSmoothing=False

Just save the file, don’t need to set Properties for it. And yes, it’s a LOT. Please comment if you find anything unnecessary or incorrect. It’ll always be helpful to know, thanks!

Additional Parameters

We have come to the Final. It remains only to set an Additional Launch Parameters in Steam (located in the Properties of the game). And that’s -dx11 . . . (yeah, but with it really less friezes!)

The game is ready for testing! Thanks to this, I was able to play the game with stable and smooth FPS on my aging PC. Even the Castle Kandar map runs without problems (unlike the vanilla minimals). The only FPS drops occur with a large number of deadlines and effects on the screen (usually when protecting a book), but this isn’t critical. And here’s what the game looks like with these settings:

Yeah, not the best graphics, but it works! You can also slightly adjust the image through your graphics card control panel, but it can also eat up some FPS (for some reason, my usual settings doesn’t work correctly with UE4 projects, it’s more for Unity, Ubisoft and some other triple-A games, so I didn’t include it in this guide). Also a few sections on known errors / bugs:

Err: Blurred Textures

This bug is quite rare, but it still happens to people even with fairly powerful PCs (in «RDR2» for example). Textures won’t load, turning the world into a soapy plastic mess. The most compressed textures is used instead of standard resolution and it doesn’t disappear. This may be due to a lack of video memory, or rather its inability to unload the cache (at least, it’s written on various forums).

In my case (and with this game), the textures aren’t loaded immediately, I have to wait at least 5-10 seconds, but this doesn’t prevent from starting to play. All thanks to the above -dx11 parameter. However, if this doesn’t help, you can add: -NOTEXTURESTREAMING. This option forces all textures to be loaded all the time, however, this increases the load time of both the game itself and matches.

People also use this two optional variants for more performance: -norhithread (ONLY when -dx11 is enabled). Disable multi-threaded rendering commands affecting FPS stability. For owners of more than 8GB of RAM: -NoVerifyGC (disable dynamic RAM allocation and reduces the number of friezes).

Err: Albino Characters

This is a problem of this particular configuration, but it’s happens only in the characters models viewing in the asymmetry upgrade menu (and only with a standard frontal pose). The r.ShadowQuality line in Engine.ini is responsible for this and is cured by changing the parameter from 0 to 1, however, this returns some of the lags to Castle Kandar. If you know another solution, suggest it in the comments! And this funny bug looks like this:

Err: UE4 0x887A0006 Crash

“Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 – ‘HUNG’)” — is a common error in games on this engine. It’s also independent of PC specs, but it’s happened to me in at least in a couple of games, including this one. Causes a full stop to the client, which needs a solution.

Lowering my video card’s core clock was helpful (yes, this may sound strange). There are different software from manufacturers for doing this; I will use MSI Afterburner as many people use it to monitor game FPS and overall performance.

Start the program, lower Core Clock (MHz) by -30, and click Apply (this way, I was able to play without issues for hours!). Additionally, this profile could also be saved as one of five profiles but if program autorun isn’t enabled and if your desired game’s profile wasn’t already set as one of your default profiles; otherwise you will need to manually activate it each time when turning on PC (it doesn’t matter! as activating manually doesn’t matter).

Share your comments on our most recent post, Evil Dead: The Game – Low End PC Optimization Guide, and let us know if we can do anything to improve it or if you notice an error. We’ll make the required modifications as soon as we can. We appreciate you so much and wish you a wonderful rest of the day. To give credit where credit is due, I’d like to mention that an article written by ❥ SexySexyLover inspired this guide. Don’t forget to add us to your bookmarks if you enjoyed the post; we update regularly with fresh stuff.