Minecraft Dungeons II renders at a low native resolution, and that soft, blurry look comes with flickering on top of it. I put together this fix to clean both problems up at once. It was written for Windows, but it should also work on Linux, since Wine runs a stripped-down version of Windows underneath. The file path may just look a little different on your system.
Why the Game Looks Blurry
The root cause is the low native rendering resolution. Raising it is the main fix, but it comes at a cost. You render the game at a higher resolution, so expect a performance drop somewhere between 15% and 50%. That tradeoff is worth knowing before you start, because you can dial the value up or down to match your hardware.
Step 1: Open the Config Folder
Press Win+R, then paste the line below and hit OK.
powershell explorer.exe “C:\Users\your_user\AppData\Local\Dungeons2\Saved\Config\Windows”
Replace your_user with your actual Windows user name. This opens the game’s config directory directly. If the folder doesn’t open for some reason, navigate there manually instead. When you land in the right place, you should see a file called GameUserSettings.ini. That file is your sign you’re in the correct directory.
Step 2: Create Engine.ini
In that same folder, create a new file named Engine.ini. Open it and add the following:
[SystemSettings]
r.ScreenPercentage=125
You can set the value anywhere from 110 to 150, depending on your preference and how much performance you can spare. Just remember the higher you go, the bigger the framerate hit.
Step 3: Switch Anti-Aliasing to TSR
Here’s the part I had to think through. Once you raise the render resolution, the game’s flickering issue gets more noticeable. To counter it, you need to change the anti-aliasing method from TAA to TSR and adjust a few TSR values. Skip this and motion clarity gets bad enough that you’ll start seeing afterimages.
Add these lines to the end of the file:
r.AntiAliasingMethod=4
r.TSR.History.ScreenPercentage=125
r.TSR.Velocity.WeightClampingSampleCount=1
Watch the r.TSR.History.ScreenPercentage value closely. It should match your r.ScreenPercentage value, or sit slightly below it. If you set it higher, you take a large performance hit for no visible gain.
Step 4: Check Your Values and Save
Save the file and close it. When you’re done, the contents should look exactly like this:
[SystemSettings]
r.AntiAliasingMethod=4
r.ScreenPercentage=125
r.TSR.History.ScreenPercentage=125
r.TSR.Velocity.WeightClampingSampleCount=1
Step 5: Make the File Read-Only
Right-click Engine.ini and choose Properties. At the bottom, tick the Read-only checkbox, then click save. This keeps the game from overwriting your changes later. That step is easy to forget, and it matters.
Step 6: Launch the Game
That’s it. Start the game and the blur and flickering should be gone.
If You Don’t Like TSR
TSR won’t appeal to everyone. If it looks off to you, keep r.ScreenPercentage between 125 and 150 and simply accept the flickering. It’s honestly not that noticeable if you don’t focus on it, and at night it’s almost gone entirely.
