https://bugs.winehq.org/show_bug.cgi?id=56012
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zeb Figura z.figura12@gmail.com --- (In reply to Grigory Vasilyev from comment #2)
How can there be a dxvk error if everything works fine in Wine 8? I specifically checked different versions of wine many times, even tried staging patches. This is exactly the regression of wine.
Because changes in one part of Wine can expose bugs in another part, or in third-party components. In fact many regressions fall into this category.
Moreover, nothing prevents from analyzing the logs, and if the logs show that the problem is dxvk, then redirect it to them.
Well, the major thing that prevents this is that debugging takes time, and that time is extremely scarce to begin with.
If it's truly a Wine bug, it should be reproducible with only builtin Wine components. If not, it's unreasonable to expect Wine developers to waste their time debugging someone else's bug.
This isn't to say that third-party components are absolutely forbidden in this bug tracker, if there's good enough reason for me to believe that the component isn't related. [A bisect may very likely end up being a good enough reason, and would be appreciated regardless.] But when all we have to work with is "FPS is lower", it's hard to be sure it's not DXVK's problem, and critically, it shouldn't be difficult to just test without DXVK.
Somewhat relatedly, I also just now notice you mention fsync. That's not a part of wine or even wine-staging, and could similarly easily be responsible for the problem. Please test with upstream "vanilla" wine, without *any* external patches or components.