[PATCH 01/12] wined3d: store wined3d_texture and sub_resource_idx in d3dX volumes

Henri Verbeet hverbeet at gmail.com
Thu Oct 1 12:48:48 CDT 2015

On 1 October 2015 at 17:50, Stefan Dösinger <stefandoesinger at gmail.com> wrote:
> Am 2015-10-01 um 17:42 schrieb Henri Verbeet:
>> Not all d3d9 surfaces will necessarily have a corresponding d3d9
>> texture, and I'm not sure it's worth changing that. So in that
>> regard this is fine. (But please fix the '*' placement.) Once you
>> pass a wined3d_texture the container_parent parameter becomes
>> redundant.
> Just to make sure I understand this right, especially in combination
> with
> https://www.winehq.org/pipermail/wine-devel/2015-September/109145.html
> : There may not always be a d3d9_texture for a d3d9_surface but
> there's always a wined3d_texture, which we store in the d3d9_surface
> instead of the d3d9_texture. If we need the d3d9_texture for some
> reason we get the parent. I.e. pretty much what Riccardo has done in
> this regard in this patch?
Yeah, although it's not necessarily wrong to just store the d3d9
texture pointer in the d3d9 surface as well.

More information about the wine-devel mailing list