4 Jun
2014
4 Jun
'14
4:35 p.m.
Am 04.06.2014 um 16:02 schrieb Henri Verbeet hverbeet@gmail.com:
On 3 June 2014 09:41, Stefan Dösinger stefan@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.