I am attaching an apitrace but I don't see how this is going to help - how can I enable both dxvk and apitrace at the same time?
Thank you for the report.
I bisected this to be a regression in commit https://github.com/doitsujin/dxvk/commit/1b0d2e80c6e4273917c8e49464d51ea57e679b2d
I also made a apitrace after testing ingame: https://drive.proton.me/urls/C3TXTT8Q54#7pURRMF2B1wp
Turns out the old resolve path was hiding a bug here, we're hitting the blit path when we really shouldn't be.
I had this exact same issue myself. I tried everything in the books and it boiled down to 2.7 completely ignoring msaa built via in-game settings. 2.6.2 works currently.
Please try the above PR, it should solve the issue.
DXVK doesn't "completely ignore" anything, it just fucks up the resolve because of an oversight in our multisample resolve code.
I confirm that that PR makes it work again. Thank you.
Confirmed, PR works! Thanks!
Nothing extracted yet.
As of dxvk 2.7, the antialiasing feature of World of Warcraft 3.3.5 no longer works. No matter what option you choose antialiasing remains disabled. It worked fine with dxvk 2.6.2.
Software information
World of Warcraft 3.3.5 (d3d9) on Windows
System information