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

[feature] Able to set a custom DXVK version #4536

Closed
2 tasks done
ranplayer opened this issue Jan 11, 2021 · 2 comments
Closed
2 tasks done

[feature] Able to set a custom DXVK version #4536

ranplayer opened this issue Jan 11, 2021 · 2 comments

Comments

@ranplayer
Copy link

Feature Request

I confirm:

  • that I haven't found another request for this feature.
  • that I have checked whether there are updates for my system available that
    contain this feature already.

Description

It would be useful if a custom DXVK version could be set per game.

Justification

Some DXVK versions present regressions in some games, like Bayonetta running on Proton 5.13 (other D3D9 games might be facing the same issue). If you just change the Proton build from a previous version, you might loose bug fixes and performance improvements related to Wine.

@kisak-valve
Copy link
Member

Hello @ranplayer, I think the intent for #4201 applies here. Regressions in DXVK or other sub-components of Proton should always be reported and fixed, not avoided. There are methods to swap out the version DXVK in use, but that shouldn't be considered supported.

@ranplayer
Copy link
Author

@kisak-valve , I agree with you. The thing is: fixes may take time to be available for the final users, and in the meantime an easier workaround mechanism would be useful. I've been tracking some Proton regressions that took more than 6 months to get fixed (like this one from Killer Instinct).

Anyway, I just like to express here that I really enjoy this project and all the hard work from people involved.

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