Hi,
I am interested on working on getting DirectX 12 support into Wine. Is there anyone currently working towards that goal that I can get in contact with?
With that said, what would an appropriate implementation in Wine look like?
DirectX 12 on top of Vulkan seems like an obvious choice. The two APIs are very similar, whereas the DirectX 12 programming model deviates significantly from both OpenGL and DirectX 11.
Another approach is to leverage wined3d (i.e. OpenGL + extensions). I don't know to what extent wined3d can be used or needs to be changed in order to support DirectX 12, or if it'd be useful at all. Can anyone shed some light on whether this would be a feasible approach?
Thanks.
Hi,
On Tue, Jan 24, 2017 at 7:17 AM, Gabríel Arthúr Pétursson gabriel@system.is wrote:
With that said, what would an appropriate implementation in Wine look like?
DirectX 12 on top of Vulkan seems like an obvious choice. The two APIs are very similar, whereas the DirectX 12 programming model deviates significantly from both OpenGL and DirectX 11.
Right, Vulkan seems to be the best choice. A hypothetical implementation of D3D12 in Wine is likely to be a separate thing from wined3d.
Another approach is to leverage wined3d (i.e. OpenGL + extensions). I don't know to what extent wined3d can be used or needs to be changed in order to support DirectX 12, or if it'd be useful at all. Can anyone shed some light on whether this would be a feasible approach?
The only thing useful for D3D12 in wined3d seems to be SM5 bytecode parser.
The first step for implementing D3D12 in Wine is adding a support for Vulkan. This is required in order to properly implement DXGI swapchains which are linked to a given HWND. Generally, I recommend to focus on Vulkan support first. Vulkan support in Wine will be immediately beneficial to Vulkan applications, and it is the starting point for further D3D12 work.
Cheers, Józef
On Wed, Jan 25, 2017 at 2:12 PM, Józef Kucia joseph.kucia@gmail.com wrote:
The first step for implementing D3D12 in Wine is adding a support for Vulkan. This is required in order to properly implement DXGI swapchains which are linked to a given HWND. Generally, I recommend to focus on Vulkan support first. Vulkan support in Wine will be immediately beneficial to Vulkan applications, and it is the starting point for further D3D12 work.
That is a win-win situation as Vulkan is already implemented in Staging for almost 1 year, so most likely mature enough.
On Wed, 2017-01-25 at 17:12 +0100, Józef Kucia wrote:
The first step for implementing D3D12 in Wine is adding a support for Vulkan. This is required in order to properly implement DXGI swapchains which are linked to a given HWND. Generally, I recommend to focus on Vulkan support first. Vulkan support in Wine will be immediately beneficial to Vulkan applications, and it is the starting point for further D3D12 work.
Wine Staging has experimental patches for Vulkan support. Are those patches in a state that can be considered for inclusion into Wine? If not, what further work is needed?
There are a number of concerns I have looking at those patches:
The API translation is done in the Vulkan loader. This is pr oblematic because applications may ship their own loader, or statically link one. Applications that do that would not work under Wine.
There does not appear to be support for instance layers. The Steam overlay uses layers for Vulkan games. Vulkan debuggers also rely on them, e.g. RenderDoc.
How about implementing the API translation as a Vulkan ICD and ship the official Khronos Vulkan loader as-is?
-
Bruno Jesus -
Gabríel Arthúr Pétursson -
Józef Kucia