[PATCH 3/5] wined3d: Don't set WINED3DUSAGE_RENDERTARGET on the front buffer.

Henri Verbeet hverbeet at gmail.com
Wed Sep 4 16:29:40 CDT 2013

On 4 September 2013 23:18, Stefan Dösinger <stefandoesinger at gmail.com> wrote:
> We set the frontbuffer as render target in wined3d_device_init_3d if
> there's no backbuffer, i.e., when ddraw is used. In theory this
> doesn't matter because we're not rendering to it, just blitting.
> Similarly, dlls/ddraw/device.c calls set_render_target to set the
> ddraw frontbuffer on release. The call fails now, but that doesn't
> cause any visible problems yet. There is a zombie wined3d surface
> left, but it goes away on ddraw shutdown or when a new ddraw
> IDirect3DDevice is created.
Right. I had noticed the FIXME, but didn't quite realize we already
enforced it. My long term plan for fixing that FIXME was to get rid of
the restriction on setting render target 0 to NULL, since afaik that's
valid in d3d10 anyway.

More information about the wine-devel mailing list