[Bug 46506] Why are you still not using Vulkan for WineD3D for D3D9, D3D10 , D3D11? Why are you still using OpenGL?

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Jan 24 14:03:29 CST 2019


https://bugs.winehq.org/show_bug.cgi?id=46506

Qwerty Chouskie <asdfghrbljzmkd at outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |asdfghrbljzmkd at outlook.com

--- Comment #6 from Qwerty Chouskie <asdfghrbljzmkd at outlook.com> ---
(In reply to Shmerl from comment #5)
> (In reply to Henri Verbeet from comment #1)
> > We also tried working with the DXVK project; that didn't work out.
> 
> Can you please elaborate on what didn't work out exactly? Is it because you
> don't accept C++ code or some other reasons? DXVK is already very high
> quality, and re-doing all that work would be a major waste of effort.

Agreed, re-implementing DXVK would be a LOT of duplicated effort.  DXVK is
funded by Valve, and is almost perfect as a translation layer.  How hard would
it be to ship DXVK with Wine and auto-switch which implementation is used based
on the devices's capabilities?  I'd hate to see many man hours going toward
re-implementing the wheel when they could be used elsewhere...

AFAIK there are no legal/license compatibility reasons why DXVK couldn't be
shipped with Wine.

-- 
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.



More information about the wine-bugs mailing list