[PATCH 2/5] ddraw: Use offscreen backbuffers.
stefandoesinger at gmx.at
Fri Sep 16 04:17:12 CDT 2011
-----BEGIN PGP SIGNED MESSAGE-----
Am 16.09.2011 um 01:29 schrieb Henri Verbeet:
> 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.
Works for me.
>> 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.
Another thing your second patch breaks is vsync because there won't be any swapbuffer calls. Although arguably that was kinda broken since we replaced flips with blits.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
-----END PGP SIGNATURE-----
More information about the wine-devel