[PATCH 2/4] wined3d: Keep track of renderbuffer capabilities.

Henri Verbeet hverbeet at gmail.com
Mon May 4 07:44:45 CDT 2015


On 4 May 2015 at 13:42, Stefan Dösinger <stefandoesinger at gmail.com> wrote:
> Am 2015-04-30 um 22:33 schrieb Henri Verbeet:
>> I think WINED3DFMT_FLAG_FBO_ATTACHABLE mostly does what we want as
>> long as FBO ORM is used, perhaps it should be generalized to e.g.
>> WINED3DFMT_FLAG_RENDERABLE.
> I'm inclined to keep it called WINED3DFMT_FLAG_FBO_ATTACHABLE and just
> not check it when we're using backbuffer ORM. We already have
> WINED3DFMT_FLAG_RENDERTARGET that more or less mirrors
> WINED3DFMT_FLAG_FBO_ATTACHABLE for color buffers. Having a
> FLAG_RENDERABLE in addition would be confusing IMO.
>
It wouldn't really be in addition, since
WINED3DFMT_FLAG_FBO_ATTACHABLE can go away then, but sticking with
WINED3DFMT_FLAG_FBO_ATTACHABLE is probably ok in the short term.
Ideally WINED3DFMT_FLAG_RENDERTARGET would just go away as well, but
there are some tricky bits wrt. formats that never should be available
for render targets on the one hand and formats that always should be
available on the other hand.



More information about the wine-devel mailing list