-
Notifications
You must be signed in to change notification settings - Fork 37
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
If this is an improvement to DXVK, why doesn't the author of DXVK implement it? #61
Comments
After the initial controversy where it got pulled from official dxvk (tho it's debated whether there even was any legit anti cheat issues related to dxvk, but he didn't want to deal with any shitfall legit or not) the dev decided that he didn't think it was the correct way to handle the shader stutter issue anyway. It is a bit of a hack and can cause graphical issues while shaders compile because the game might try to render something before a background shader thread is done. I don't know how much it happens in practice though. Tho note i was not around back then myself nor am i familiar with the technical inners of any of this so i might get some details wrong. |
Heh, except the fact that even dxvk GIT is crap stutter-wise |
Do you know what exactly might be the new thing in v2.0? I just tried it and the stutters are horrible. Is there any other setting that might help with this? |
https://github.com/doitsujin/dxvk/releases/tag/v2.0 Currently only Nvidia have the required extension in a stable release. |
AMD has the extension in Git, enabled by an environment variable. Intel has it unmerged, in limbo or something. And async is still better on Windows, for Arc cards, where Intel is also unlikely to implement Graphics Pipeline Library extension unless it becomes a mandatory part of some spec they intend to support. |
If this is an improvement to DXVK, why doesn't the author of DXVK implement it? What's the catch?
The text was updated successfully, but these errors were encountered: