On Tue, 20 Nov 2018 at 17:39, Paul Gofman gofmanp@gmail.com wrote:
It gets WINED3D_LOCATION_SYSMEM right at initialiaztion and this location is never used again anywhere but in the fast texture load code path under consideration (which ultimately prefers the sysmem location). Application never tries to map it.
Ah yes, that would do it. I think ideally we'd fix that as well. There's a somewhat theoretical concern that for e.g. a mappable rendertarget or default pool offscreen plain surface it may be advantageous to use the download path as well. I'm not sure how much we care about those cases.