[Bug 45430] Improve diagnostics of 'D3DxxCreateDevice' failures for warp driver type ( D3D10_DRIVER_TYPE_WARP or D3D_DRIVER_TYPE_WARP)

[wine-bugs at winehq.org]

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

--- Comment #2 from Henri Verbeet <hverbeet at gmail.com> ---
(In reply to Anastasius Focht from comment #0)
> Might be a bit off-topic to this ticket: Is Direct3D 11 WARP driver support
> ever considered in Wine? I guess getting DX11+ feature support with hardware
> drivers to work perfectly (tm) is much higher priority. The MS website
> (https://docs.microsoft.com/en-us/windows/desktop/direct3darticles/directx-
> warp) lists some interesting use-cases though.
> 
I haven't looked much into what would be required to make that work, but I
suspect it would involve adopting the Windows D3D driver model and loading the
WARP driver. That's unlikely to happen.

In the more general sense of explicitly selecting a software renderer, the
GLX_MESA_query_renderer extension in theory has to capability to enumerate and
select software renderers like llvmpipe in addition to hardware GPUs, and I
think using that capability to implement "WARP" would be fine. Last time I
checked that part of the extension wasn't actually implemented in Mesa though,
so that would need to be made to work first.

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