How To Disable Depth of Field in Grounded 2

Just like the first game, Grounded 2 uses an aggressive depth of field effect to obscure environments and objects in the distance. This is part of the game’s presentation, but it can be a bit distracting, especially if you don’t like the post-processing effect in general.

While the in-game settings let you turn it down a bit, here is how you can completely disable depth of field in Grounded 2.

Disable Depth of Field in Grounded 2

Like other Unreal Engine 5 games, you can disable depth of field fully by editing the configuration file of Grounded 2, but that isn’t available in the usual path. Here is how you can manually create that and disable the effect completely.

• First, head over to the following location:

C:\Users\[Windows Username]\AppData\Local\Augusta\Saved\Config\WinGRTS

• Here, create a new text file and rename it to Engine.ini while making sure you modify the file extension as well.
• Open the file and enter the following lines:

[SystemSettings]
r.DepthOfFieldQuality=0

• It should look like this:

• Save the file (Ctrl + S) and exit.
• Important: Now, right-click on the newly created Engine.ini file and select properties. Check “Read Only” next to Attributes. This will ensure that the game doesn’t delete the Engine.ini file once it’s launched, because it will otherwise.

After that, you’re done. The next time you launch Grounded 2, depth of field will be completely disabled.

Comparison Screenshots

Here is what the game looks like with the lowest value of in-game depth of field versus the effect completely disabled after the Engine.ini file edit.

As you can see, even though my character is focusing on the device, the background isn’t out of focus anymore.

If, for whatever reason, you want to enable depth of field again, simply delete the Engine.ini file.

I think that extra detail brings the world to life, and while I understand the intent behind the heavy depth of field, there should be an in-game option to disable it completely. Since Grounded 2 is in early access, developers are constantly looking for feedback, and it’s possible they’ll add the option down the line. They never did in the first one, but it could happen here.