[PATCH 6/6] wined3d: Do not warn about WINED3DUSAGE_WRITEONLY.

Stefan Dösinger stefandoesinger at gmail.com
Wed Jun 4 11:35:48 CDT 2014


Am 04.06.2014 um 16:02 schrieb Henri Verbeet <hverbeet at gmail.com>:

> On 3 June 2014 09:41, Stefan Dösinger <stefan at codeweavers.com> wrote:
>> As the previous tests show, we can't do anything with this flag.
> Sort of. It may make sense to set WINED3D_BUFFER_DOUBLEBUFFER if
> WINED3DUSAGE_WRITEONLY isn't set.
Why would we want to do that? The only thing I can think of is if there's a GL driver where reading back the buffer object has the same performance characteristics as reading back a WRITEONLY resource on Windows. So far I haven't seen an application / driver combination with such an issue, but I didn't really look for one either.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20140604/698784ec/attachment.sig>


More information about the wine-devel mailing list