https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #13 from Alexander angavrilov@gmail.com --- Created attachment 49596 --> https://bugs.winehq.org/attachment.cgi?id=49596 log with WINEDEBUG=+d3d_surface (bzip2)
Since the patch shows the issue is somewhere in the D3D surface code, I produced a log of that as the game loads and then a couple of switches between tanks are done in hangar (this is when the bug most commonly appears). The log contains inserted comments starting with '==============' that describe what is being done.
To reduce the size of the log I filtered out very frequent repeating spam of this kind:
trace:d3d_surface:surface_invalidate_location surface 0x4e6bc28, location WINED3D_LOCATION_DISCARDED | WINED3D_LOCATION_SYSMEM | WINED3D_LOCATION_USER_MEMORY | WINED3D_LOCATION_DIB | WINED3D_LOCATION_BUFFER | WINED3D_LOCATION_TEXTURE_RGB | WINED3D_LOCATION_TEXTURE_SRGB | W. trace:d3d_surface:surface_load_location surface 0x4e6bc28, location WINED3D_LOCATION_RB_MULTISAMPLE. trace:d3d_surface:surface_load_location Location already up to date. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00.
and
trace:d3d_surface:surface_modify_ds_location surface 0x4e6c150, new location 0x100, w 1280, h 1024.