https://bugs.winehq.org/show_bug.cgi?id=29586
Sergey Isakov isakov-sl@bk.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |isakov-sl@bk.ru
--- Comment #6 from Sergey Isakov isakov-sl@bk.ru --- It's a pity wine-stage with dxtn support doesn't help with this game with either native or builtin d3dx9_36.dll. With or without CSMT enabled. Enable or disable volume DXTn textures. Somehow wined3d have a bug with DXTn surfaces. This texture was successfully created --- trace:d3d_texture:wined3d_texture_create device 0x1da698, desc 0x6a8e090, level_count 7, surface_flags 0x4, data 0x0, parent 0x200338, parent_ops 0x47d229bc, texture 0x6a8e08c. trace:d3d_texture:wined3d_texture_init texture 0x2003c8, texture_ops 0x47e7a3a8, layer_count 1, level_count 7, resource_type WINED3D_RTYPE_TEXTURE, format WINED3DFMT_DXT5, multisample_type 0, multisample_quality 0, usage WINED3DUSAGE_TEXTURE, pool WINED3D_POOL_MANAGED, width 64, height 64, depth 1, surface_flags 0x4, device 0x1da698, parent 0x200338, parent_ops 0x47d229bc, resource_ops 0x47e7a3c4. ... trace:d3d_texture:wined3d_texture_create Created texture 0x2003c8. ---
Other one no. --- trace:d3d_texture:wined3d_texture_create device 0x1da698, desc 0x6a8de80, level_count 1, surface_flags 0x3, data 0x0, parent 0x0, parent_ops 0x47e738fc, texture 0x6a8deac. trace:d3d_texture:wined3d_texture_init texture 0x123180, texture_ops 0x47e7a3a8, layer_count 1, level_count 1, resource_type WINED3D_RTYPE_TEXTURE, format WINED3DFMT_DXT5, multisample_type 0, multisample_quality 0, usage 0, pool WINED3D_POOL_SCRATCH, width 64, height 64, depth 1, surface_flags 0x3, device 0x1da698, parent 0x0, parent_ops 0x47e738fc, resource_ops 0x47e7a3c4. trace:d3d_texture:texture_init xf(1.000000) yf(1.000000) ... trace:d3d_texture:wined3d_texture_decref texture 0x123180, swapchain 0x0. ---
I see the difference is in surface_flags #define WINED3D_SURFACE_MAPPABLE 0x00000001 #define WINED3D_SURFACE_DISCARD 0x00000002 #define WINED3D_SURFACE_PIN_SYSMEM 0x00000004
any ideas?