http://bugs.winehq.org/show_bug.cgi?id=59344 --- Comment #2 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Andrey Gusev from comment #0)
0ba4:fixme:d3d:wined3d_texture_gl_prepare_texture No GL internal format for format WINED3DFMT_NV12_PLANAR. 0ba4:err:d3d:wined3d_debug_callback 00007FA3EB30F610: "GL_INVALID_ENUM error generated. <internalFormat> not valid.". 0ba4:err:d3d:wined3d_debug_callback 00007FA3EB30F610: "GL_INVALID_VALUE error generated. Invalid texture format.".
It's hard to say what exactly is going on from just these few lines, but WINED3DFMT_NV12_PLANAR is currently only supported with the wined3d Vulkan backend, and you may have better luck with that. In principle the format isn't that different from WINED3DFMT_NV12, although there are some differences between the way d3d9 uses planar formats and the way d3d11 uses them. Commit 984e24d327ecc5ec92e3cf8f8afa9d7631d39d64 split WINED3DFMT_NV12, although I suspect the issue could have been handled with e.g. a WINED3D_VIEW_ALL_PLANES flags as well, much like how we handle other differences between d3d9 and d3d11. The immediate question then probably is whether this part of the issue is a regressions from commit 984e24d327ecc5ec92e3cf8f8afa9d7631d39d64, or if this never worked at all. (In reply to Andrey Gusev from comment #1)
vkd3d:0bb4:fixme:d3d12_command_list_CopyTextureRegion Depth-stencil format 0x13 not fully supported yet. vkd3d:0bb4:err:d3d12_command_list_copy_incompatible_texture_region Failed assertion: dst_format->byte_count == src_format->byte_count
This part is a vkd3d issue, and that seems to imply the application is using both d3d11 and d3d12. Format 0x13 is DXGI_FORMAT_R32G8X24_TYPELESS. I happen to have done some work on depth/stencil format support recently, but it probably doesn't address this particular issue. Could you attach a VKD3D_DEBUG="trace" log? (Specifically, I'd like to know both the source and destination formats involved; d3d12_command_list_copy_incompatible_texture_region() contains a WARN for those.) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.