protonscr

Dishonored 2 - LOD Texture issue

dxvkclosed
doitsujin/dxvk#4198 · opened 2024-08-09 by Ghostbroker · updated 2024-08-20 · 18 comments · github
GGhostbroker 2024-08-09 github

In Dishonored 2, the low quality textures at distance seem to be used up close in some instances as evidenced in the screenshots below. It seems random, as sometimes I can walk away and walk back up close and some of the high quality textures will load, but if I spin around or look away, it goes back to the low quality ones.

Software information

Dishonored 2 on Ultra settings, but it was tested on low, high, and very high as well with the same results. V-Sync and Adaptive resolution is disabled with an FPS Limiter of 120 set. TXAA Sharpness is 20.

System information

  • GPU: 4080 16GB
  • Driver: 555.58.02
  • Wine version: Proton 9/Experimental
  • DXVK version: 2.4

403640_9
403640_8
403640_5

TTiagoquix 2024-08-09 github

Searching for this issue on Steam Forums it seems this is a game problem rather than a DXVK problem, and related to one of the updates Bethesda released to the game.

As far as I can tell, you have to do some things:

  • Disable adaptive resolution in game settings.
  • Disable TXAA and/or TAA where possible (prefer less blurry AA methods), and/or adjust sharpness setting of anti-aliasing.
  • One of the recommendations is to use ReShade with the LumaSharpen filter to add sharpness.

If you want to try ReShade, see https://github.com/kevinlekiller/reshade-steam-proton.
After installing, you should be able to use ReShade as on Windows (press Home to open overlay when in-game).

GGhostbroker 2024-08-10 github

Searching for this issue on Steam Forums it seems this is a game problem rather than a DXVK problem, and related to one of the updates Bethesda released to the game.

As far as I can tell, you have to do some things:

* Disable adaptive resolution in game settings.

* Disable TXAA and/or TAA where possible (prefer less blurry AA methods), and/or adjust sharpness setting of anti-aliasing.

* One of the recommendations is to use ReShade with the LumaSharpen filter to add sharpness.

If you want to try ReShade, see https://github.com/kevinlekiller/reshade-steam-proton. After installing, you should be able to use ReShade as on Windows (press Home to open overlay when in-game).

Adaptive resolution is already disabled and I've tried disabling/renabling TXAA/TAA and it didn't help. The Reshade made the game brighter but didn't fix the texture issue. I noticed no difference with LumaSharpen. If it is a game bug though, I guess I will just have to live with it.

TTiagoquix 2024-08-10 github

You can try to download an old version to see if it fixes the issue.

See https://wiki.fireundubh.com/kingdomcome/steam-console. I believe it's any version prior to patch "1.4" or something. Try to download the first version if possible.

LLord-Nightmare 2024-08-12 github

You can try to download an old version to see if it fixes the issue.

See https://wiki.fireundubh.com/kingdomcome/steam-console. I believe it's any version prior to patch "1.4" or something. Try to download the first version if possible.

The 'download_depot' trick in the steam console no longer works for typical steam clients due to an added security check valve added to steam on 20200212 (and additional checks in 2022). You need to use a different means to download old depot versions instead.

BBlisto91 2024-08-12 github

The 'download_depot' trick in the steam console no longer works for typical steam clients

Worked last time i tried it earlier this year.

Anyway i plan on checking the game out here at some point on Windows to make sure that it behaves the same.

GGhostbroker 2024-08-12 github

Worked last time i tried it earlier this year.

Anyway i plan on checking the game out here at some point on Windows to make sure that it behaves the same.

It doesn't behave the same on Windows. On the same hardware and same graphics settings, the textures load fine for me in Windows.

BBlisto91 2024-08-12 github

Does it break if you use dxvk on Windows?

TTiagoquix 2024-08-12 github

This may be a shader cache issue. How big is your $HOME/.cache/nvidia folder?

Ddoitsujin maintainer 2024-08-12 github

This is almost certainly not a shader cache issue and just the game doing weird things to try and manage its memory usage.

Which isn't uncommon, but there's usually just not a huge amount we can do about it since we can't really look at the code and figure out what's going on.

TTiagoquix 2024-08-12 github

Hmm... this may be related to an old issue: https://github.com/doitsujin/dxvk/issues/1103

GGhostbroker 2024-08-12 github

Does it break if you use dxvk on Windows?

The issue didn't happen on windows with dxvk.

Hmm... this may be related to an old issue: #1103

I don't think that's my issue. I have 16GB of VRAM/64GB RAM and the game seems to use between 4 and 9 VRAM on Ultra.

This is almost certainly not a shader cache issue and just the game doing weird things to try and manage its memory usage.

Which isn't uncommon, but there's usually just not a huge amount we can do about it since we can't really look at the code and figure out what's going on.

Outside of downloading an old version of the game, is there anything I can do to fix this on my end?

BBlisto91 2024-08-13 github

Try disabling fsync (and maybe esync) and see if it makes a difference. Apparently it can cause similar issues in some of the BioShock games.

PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%

TTiagoquix 2024-08-13 github

May also be worth to try Dishonored 2 with OpenGL to see if it is DXVK's fault.

PROTON_USE_WINED3D=1 %command% (try with FSYNC+ESYNC OFF then ON too)

LLord-Nightmare 2024-08-13 github

Worked last time i tried it earlier this year.

I will admit I haven't tried it in a while, when I last did in mid 2020 it did not work. YMMV I guess?

BBlisto91 2024-08-14 github

We have managed to track down the high res killer. See nvapi issue above.

BBlisto91 2024-08-17 github

@Ghostbroker Are you able to verify that this looks fine now on Proton Experimental Bleeding Edge

GGhostbroker 2024-08-18 github

@Ghostbroker Are you able to verify that this looks fine now on Proton Experimental Bleeding Edge

Yes, it is working for me now.

KK0bin maintainer 2024-08-20 github

Fixed in DXVK-Nvapi.

Proton versions

Launch options

Launch lines

Upstream links