https://bugs.winehq.org/show_bug.cgi?id=47269
Bug ID: 47269 Summary: World of Warcraft / D3D12 / Unplayable with RADV Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs@winehq.org Reporter: berillions@gmail.com Distribution: ---
Created attachment 64563 --> https://bugs.winehq.org/attachment.cgi?id=64563 WoW d3d12 log
Hello,
i use wine-staging 4.8 + Mesa Git + LLVM 9 + vkd3d git and the game is unplayable with RADV. As you can see on the screenshot, i have a lot of graphical glitches.
I have this line in the log : fixme:vkd3d_bind_heap_memory: Invalid heap offset 0x3b0000.
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #1 from Berillions berillions@gmail.com --- Created attachment 64564 --> https://bugs.winehq.org/attachment.cgi?id=64564 WoW d3d12 Screenshot
https://bugs.winehq.org/show_bug.cgi?id=47269
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #2 from Józef Kucia joseph.kucia@gmail.com --- Created attachment 64582 --> https://bugs.winehq.org/attachment.cgi?id=64582 Patch
Please attach a terminal output (with the patch applied).
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #3 from Berillions berillions@gmail.com --- Created attachment 64585 --> https://bugs.winehq.org/attachment.cgi?id=64585 Output log with patch applied
Thanks Josef, the patch fix the rendering issue ;-)
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #4 from Berillions berillions@gmail.com --- Josef,
Currently, WoW works with vkd3d only when i'm in the old region of WoW Vanilla. But when i want to use a character who is in the new region of WoW BfA, the game game crash with an Error 132 :
"ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception! The instruction at "0x00007f38292be4e0" referenced memory at "0x0000000000000101". The memory could not be "read"."
I still have this line in the output console : "Failed to acquire Vulkan semaphore for fence 0x7d30e810, value 0x20a2, completed value 0x20a1."
WoW + DXVK + D3D11 still work in the new region of BfA
https://bugs.winehq.org/show_bug.cgi?id=47269
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|World of Warcraft / D3D12 / |World of Warcraft / D3D12 / |Unplayable with RADV |Invalid heap offset
https://bugs.winehq.org/show_bug.cgi?id=47269
minion minion.procyk@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |minion.procyk@gmail.com
--- Comment #5 from minion minion.procyk@gmail.com --- I'm going to bet someone here is going to ask you to create a separate bug for your new, separate issue. And that the original bug is now resolved and this patch will be applied for this specific bug.
Just trying to give a heads up.
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #6 from Józef Kucia joseph.kucia@gmail.com --- Created attachment 64655 --> https://bugs.winehq.org/attachment.cgi?id=64655 Debug patch
(In reply to Berillions from comment #3)
Thanks Josef, the patch fix the rendering issue ;-)
I would like to submit the fix upstream, but I need to fully understand the issue. Could you please get a "VKD3D_DEBUG=trace" log with the attached patch?
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #7 from Berillions berillions@gmail.com --- Hello Josef,
You can download the "VKD3D_DEBUG=trace" log with the attached patch here : https://drive.google.com/open?id=15Xi22NP0aHQtV-plXlQPkTo5HtJJ52xh
https://bugs.winehq.org/show_bug.cgi?id=47269
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #8 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Berillions from comment #7)
You can download the "VKD3D_DEBUG=trace" log with the attached patch here : https://drive.google.com/open?id=15Xi22NP0aHQtV-plXlQPkTo5HtJJ52xh
Thanks. It seems that WoW ignores the alignment returned from GetResourceAllocationInfo() and uses D3D12_DEFAULT_RESOURCE_PLACEMENT_ALIGNMENT (0x10000).
https://bugs.winehq.org/show_bug.cgi?id=47269
--- Comment #9 from Berillions berillions@gmail.com --- (In reply to Józef Kucia from comment #8)
(In reply to Berillions from comment #7)
You can download the "VKD3D_DEBUG=trace" log with the attached patch here : https://drive.google.com/open?id=15Xi22NP0aHQtV-plXlQPkTo5HtJJ52xh
Thanks. It seems that WoW ignores the alignment returned from GetResourceAllocationInfo() and uses D3D12_DEFAULT_RESOURCE_PLACEMENT_ALIGNMENT (0x10000).
Hum... Ok :D I'm not familiar with Directx and/or Vulkan si i trust you. This issue is difficult to fix ?
https://bugs.winehq.org/show_bug.cgi?id=47269
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |be23a8fc90bade6c1af4f2e317b | |0b0d8a34593b7 Summary|World of Warcraft / D3D12 / |World of Warcraft / D3D12 / |Invalid heap offset |Invalid heap offset / radv | |Polaris Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #10 from Józef Kucia joseph.kucia@gmail.com --- The workaround for the heap offset issue was committed.
https://source.winehq.org/git/vkd3d.git/?a=commit;h=be23a8fc90bade6c1af4f2e3...
Please open new bugs for other remaining issues.
https://bugs.winehq.org/show_bug.cgi?id=47269
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Nikolay Sivov bunglehead@gmail.com --- Closing bugs fixed in 1.10.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla