-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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.
There's an argument to be made that with something that doesn't have FBO in its name we could mark depth formats supported or unsupported in the format table initialization and simplify the non-FBO depth format checks in check_device_format. But that doesn't really work because depth format compatibility depends on the onscreen depth format we end up using with onscreen ORM.