http://bugs.winehq.org/show_bug.cgi?id=55775 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #38 from Zeb Figura <z.figura12@gmail.com> --- (In reply to Stian Low from comment #36)
WineHQ constantly corrects reporters not to report DXVK tests/bugs but these types of video bugs are the very cause that drives users/reporters to use DXVK vs wine.
If keeping wine behind DXVK is a business strategy then perhaps its considered a waste of time to try to fix these bugs.
As I've told you before, Wine lags behind DXVK because we have had at most one developer working on Direct3D, often less than full time, for the past several years. I'm fully aware that the situation is not ideal, but there's nothing I can do to fix it. Therefore I'd appreciate leaving off the passive-aggressive comments. We ask users to test with upstream Wine rather than DXVK because this is a Wine bug tracker. We have nothing to fix when DXVK bugs are reported. For what it's worth, I only bother asking things like that when it looks like a graphics bug. I'm not about to throw the book at someone who files a sound-related bug while using DXVK.
Perhaps dxvk exists because the dev also had difficulty getting these bugs fixed and decided splitting dxvk as separate effort was more worthwhile which steam also considered worth funding independently. Must be nice to be fed for such hard effort.
No, DXVK exists because Philip wanted to write his own Direct3D implementation. He never had intention of working with upstream. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.