[PATCH 2/5] ddraw: Use offscreen backbuffers.
hverbeet at gmail.com
Thu Sep 15 18:29:21 CDT 2011
On 16 September 2011 01:03, Stefan Dösinger <stefandoesinger at gmx.at> wrote:
> On Thursday 15 September 2011 20:01:50 Henri Verbeet wrote:
>> In principle this allows us to use more than one backbuffer in ddraw. It's
>> also a requirement for the next patch.
> I think this, and the next patch should be implemented in wined3d by handling
> D3DSWAPEFFECT_FLIP in essentially the same way you're handling them in ddraw
> in your patches.
Maybe after 1.4, it's a bit more invasive to do it in wined3d. We
don't want render the frontbuffer offscreen unless the swap effect is
actually flip for performance reasons. However, the swap effect can
potentially change when a reset happens. It's possible to make that
all work, but I'd rather wait a bit to see how this works out for
> In patch 3 I'm not sure what happens when the app draws to the frontbuffer
> directly. Maybe I'm a bit too tired to see it, but doesn't that result in a
> blit of the surface onto itself?
No, the wined3d frontbuffer and ddraw frontbuffer are different surfaces.
More information about the wine-devel