[Bug 42379] New: Sleeping Dogs needs d3d11: wined3d_usage_from_d3d11 bind flags 0x80.
https://bugs.winehq.org/show_bug.cgi?id=42379 Bug ID: 42379 Summary: Sleeping Dogs needs d3d11:wined3d_usage_from_d3d11 bind flags 0x80. Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: winetest(a)luukku.com Distribution: --- I just tried to run Sleeping dogs with wine-staging 2.0 and I got bored of waiting it to load with white screen. I don't know if it would eventually. But the console is spamming some messages alot, this is one of them. I have no idea what it means. This code needs some enchanment. 400 DWORD wined3d_usage_from_d3d11(UINT bind_flags, enum D3D11_USAGE usage) 401 { 402 static const DWORD handled = D3D11_BIND_SHADER_RESOURCE 403 | D3D11_BIND_RENDER_TARGET 404 | D3D11_BIND_DEPTH_STENCIL; 405 DWORD wined3d_usage = 0; 406 407 if (bind_flags & D3D11_BIND_SHADER_RESOURCE) 408 wined3d_usage |= WINED3DUSAGE_TEXTURE; 409 if (bind_flags & D3D11_BIND_RENDER_TARGET) 410 wined3d_usage |= WINED3DUSAGE_RENDERTARGET; 411 if (bind_flags & D3D11_BIND_DEPTH_STENCIL) 412 wined3d_usage |= WINED3DUSAGE_DEPTHSTENCIL; 413 if (bind_flags & ~handled) 414 FIXME("Unhandled bind flags %#x.\n", bind_flags & ~handled); 415 This doesnt look really fatal message so I am just setting severity to enchament. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42379 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3dx11 |directx-d3d Severity|enhancement |trivial Summary|Sleeping Dogs needs |Sleeping Dogs triggers |d3d11:wined3d_usage_from_d3 |wined3d_usage_from_d3d11 |d11 bind flags 0x80. |"Unhandled bind flags | |0x80." FIXME | |(D3D11_BIND_UNORDERED_ACCES | |S) --- Comment #1 from Matteo Bruni <matteo.mystral(a)gmail.com> --- I don't know if we'll need to do anything specific for that bind flag, eventually. Either way I guess that this bug doesn't help much. I'm keeping it open for the time being but if anyone with a better clue thinks otherwise, go ahead. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42379 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nikolay Sivov <bunglehead(a)gmail.com> --- This part was reworked since then, mentioned trace was removed in the process. Marking wontfix. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42379 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #3 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing wontfix. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla