On Mon, 13 May 2019 at 23:05, Matteo Bruni mbruni@codeweavers.com wrote:
D3d9 is very lax WRT map access to buffers and there isn't really much of a reason for us to restrict read access to non-DEFAULT resources.
On the other hand, we'd still really like to be able to ensure that DEFAULT, DYNAMIC | WRITEONLY buffers get allocated in the proper memory region and get efficient data uploads, so keep the restriction for DEFAULT resources.
So another, perhaps clearer, way to frame this is that we ignore D3DUSAGE_WRITEONLY for pools other than D3DPOOL_DEFAULT.