Skip to content
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

Final Fantasy XVI performance & vertex explosion issues [AMD][RADV] #2131

Open
DistantThunder opened this issue Sep 23, 2024 · 2 comments
Open

Comments

@DistantThunder
Copy link

DistantThunder commented Sep 23, 2024

Final Fantasy XVI performance & vertex explosion issues [AMD][RADV]

Software information

  • Final Fantasy XVI
  • High/Medium mix (Dynamic Resolution enabled / Intel XESS or FSR3)
  • Framegen disabled

System information

  • Operating System: Arch Linux
  • KDE Plasma Version: 6.1.4
  • Kernel Version: 6.10.9-zen1-1-zen (64-bit)
  • Graphics Platform: Wayland
  • Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
  • Memory: 62.7 Gio of RAM
  • Graphics Processor: AMD Radeon RX 7900 XTX
  • Mesa 24.2.2-arch1.1
  • Proton Experimental - experimental-9.0-20240918

Problem description

  • The framerate appears to be particularly inconsistent trough Proton, compared to Windows (even if the game isn't perfect there), there's a heavy amount of stutter in many areas (can provide saves if necessary).
  • Sometimes, some black artifact spreads over the scene:
    image
  • GFXRecon capture attempts ends up in OoM

Log files

Please attach Proton or Wine logs as a text file:

@runar-work
Copy link
Contributor

Does the glitch appear often? It looks similar to the one reported in this Mesa issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11550. If it's the same one, it should be fixed if you try with mesa-git.

@DistantThunder
Copy link
Author

Does the glitch appear often? It looks similar to the one reported in this Mesa issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11550. If it's the same one, it should be fixed if you try with mesa-git.

Depends really, some sessions it is, some others it's nigh non-existent, I'll wait for a release upstream to cover this since it may not be VKD3D's faulting here.

Performance problems remain pregnant though, even though I've taken notice of :

But the problems persist even beyond the fixes present of that thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants