Borderlands 2 / Pre-sequel: Horizontal Scan Lines with DXVK 2.5.2 and 2.5.3 when AO (Ambient Occlusion) enabled

[HittnGaudi]

Please describe your issue as accurately as possible.

Dear DXVK DEV! I want to report a problem which is also in Borderlands 2 without DXVK a general Problem: When using WQHD Resolution, in Borderlands 2 you get these Horizontal Scan lines graphic-issue. Just goes away when disabling AO. With 1920x1080 resolution this bug doesn't exist.

BUT: With DXVK 2.5.1 everything looks fine and there is this bug NOT exisitng! When i tried using 2.5.2 or 2.5.3 i get this issue.
Problem is with 2.5.1 my transparent twitch chat overlay does not work... and there is issue like missing lava which was fixed with 2.5.2.

Can you please look into it? Would be cool if these Horizontal Scan lines would be gone with the newest versions like in 2.5.1.

If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows

Software information

Name of the game, settings used etc.

System information

• GPU: RTX 2070 Super
• Driver: Latest
• Wine version: none / windows 11 Home
• DXVK version: 2.5.3 and 2.5.2

Apitrace file(s)

• Put a link here

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

Please attach Proton or Wine logs as a text file:

• When using Proton, set the Steam launch options for your game to PROTON_LOG=1 %command% and attach the corresponding steam-xxxxx.log file in your home directory.
• When using regular Wine, use wine game.exe > game.log 2>&1 and attach the resulting game.log file.

[Blisto91]

Hi there
Do i understand correctly that it is a game bug (shows with native Windows) that didn't show with dxvk 2.5.1 but does with 2.5.2+ ?

[HittnGaudi]

Hi there Do i understand correctly that it is a game bug (shows with native Windows) that didn't show with dxvk 2.5.1 but does with 2.5.2+ ?

Yes exactly. With 2.5.1 this bug didn't show up at all and from graphic things side i didn't notice any bugs. So it resolved the issue from the game i don't know how the DEV did it at all - but sadly with newer versions 2.5.2+ it's existing like you see on the screenshot.

[Blisto91]

Without having looked at it yet it is likely because of #4471

[qinlili23333]

Can you test this branch? https://github.com/qinlili23333/dxvk/actions/runs/12821855196
I just made a branch that only reverted #4471 based on current master.
If this works then Borderlands 2 is same buggy as FF13.

Maybe we can add a configuration to enable fix for these buggy applications, although I'm not sure whether it's a good choice to add these options just for a few buggy applications.

[Blisto91]

Is this only in specific areas? Haven't spotted the issue yet ingame with AMD or Intel