-
Notifications
You must be signed in to change notification settings - Fork 776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[d3d9] Final Fantasy XIII (dxvk 2.3.1 regression?) #3919
Comments
Thanks for the bug report. |
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. |
Well, I used artifact from there |
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 . If I put dxvk 2.3 (stable) back in, everything is alright. |
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. |
@JohnnYDeveloperAHK If enableGraphicsPipelineLibrary=true causes these issues, your GPU driver is broken. That's not the case on Nvidia version 550 though. |
The updated PR fixes the remaining issues when trying to play the modded game with DXVK. |
Tested new PR fix and it's working without a problem, thanks. |
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
v.2.3.1
v.2.3
v.2.3.1
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
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
The text was updated successfully, but these errors were encountered: