protonscr

[d3d9] Final Fantasy XIII (dxvk 2.3.1 regression?)

dxvkclosed bugd3d9
doitsujin/dxvk#3919 · opened 2024-03-21 by dlshinobi · updated 2024-05-23 · 10 comments · github
Ddlshinobi 2024-03-21 github

Going from DXVK version 2.3 to 2.3.1 artifacts / vertex explosion appeared. I think it's from 2d (font, hud,...) elements.

v.2.3
ff13-dxvk-v 2 3

v.2.3.1
ff13-dxvk-v 2 3 1

v.2.3
ff13-dxvk-v 2 3-ingame

v.2.3.1
ff13-dxvk-v 2 3 1-ingame

P.S.: Yes, DXVK HUD appears with DXVK_HUD=full , so it's using DXVK. In screenshots I only was using MANGOHUD.

Software information

Final Fantasy XIII

System information

  • GPU: RTX 4080
  • Driver: 550
  • Wine version: proton-8.0-5, proton-9-exp
  • DXVK version: 2.3 - 2.3.1

Apitrace file(s)

https://drive.google.com/file/d/1kkeu1T3xLKVRgudiKBhJW1WZKkYNgBfg/view?usp=sharing
(made in linux/wine, I hope it's OK)

Log files

game.log

KK0bin maintainer 2024-03-21 github

Thanks for the bug report.

Ddlshinobi 2024-03-21 github

Hi, so I tried fix from your "finalfantasy-fix" branch and it didn't fixed anything! 2D elements still broken.

Main menu missing text
ff13-menu

Option menu
ff13-options

In game, pause menu
ff13-save

KK0bin maintainer 2024-03-21 github

Are you sure you used the correct build? It fixes the issue for me with the apitrace.

It fixes the vertex explosions in-game at least. I cannot reproduce the issue in the menu.

Ddlshinobi 2024-03-21 github
BBlisto91 2024-03-22 github

Did you check the hud or logs to make sure it is using that build

Ddlshinobi 2024-03-22 github

Did you check the hud or logs to make sure it is using that build

Yes, I've been using DXVK for years since 0.5.x version or so, I think I know what I'm doing.

This is the proof from "finalfantasy-fix" branch artifact .
Now with DXVK_HUD and MANGOHUD=off.

f13-proof-v3

If I put dxvk 2.3 (stable) back in, everything is alright.

JJohnnYDeveloperAHK 2024-03-25 github

If you're using dxvk.config, For me, this same issue has been happening in lots of games with the command dxvk.enableGraphicsPipelineLibrary=true , change it to false and see if that helps, It fixed the bug for me at least, on even older versions.

KK0bin maintainer 2024-03-25 github

@JohnnYDeveloperAHK If enableGraphicsPipelineLibrary=true causes these issues, your GPU driver is broken. That's not the case on Nvidia version 550 though.

KK0bin maintainer 2024-03-27 github

The updated PR fixes the remaining issues when trying to play the modded game with DXVK.

Ddlshinobi 2024-03-27 github

Tested new PR fix and it's working without a problem, thanks.

Proton versions

Launch options