dxvk: d3d10 error (World of Warcraft)

@TomBZombie Hard to say. Loads of the problems WoW have - atleast imo - is that it seems to be using a multitude of old-engine-code with bits and pieces of dx9/10/11 functions, and it will be fun to experiment with that once wine-devel can run blizzard games i guess 😃

You can test with wine-staging, but the problem is as was posted at start of thread, that wow is not a “pure” dx11 code it seems, and will have problems.

To the question: Since DX11 in windows have quite more fps than wine w/dx11 now, dx11 -> Vulkan would improve the rendering a lot and hopefully match that of windows. Still would not be “night & day” comparably when it comes to fps, as much of the fps limitation is not local hardware, but more the “talking back and forth to servers” that all MMO’s do 😃

@TomBZombie The whole idea of DXVK is to make use of a lower level API as to reduce/eliminate the overhead in running DX11 on top of OpenGL. So it should especially prove useful in games like WoW where the framerate is already severly CPU limited 😃

This issue appears to have been resolved by recent commits, if you have DXVK_FAKE_DX10_SUPPORT=1 set. However, there’s still an issue here. On both live and beta, on launch of the game I’ll either get a black screen and nothing else, or graphics will start to load (may get the title screen, may not, but the HUD renders for a couple frames) and then freeze entirely. Nothing obvious at all in the logs with debug enabled. I have found that on beta (not on live, sadly), if I set DXVK_FAKE_DX10_SUPPORT=0 and attempt to launch the game, it indicates that my graphics hardware has changed and prompts me to reset to defaults, then fails to launch as expected. If I then set it back to 1, it prompts me again, and on clicking yes the game launches and runs perfectly. If I exit and start it again, it’s back to the previous behavior with the black screen/freeze. If logs might be helpful, I could upload them, but I’m only using the standard logging with the debug level and saw no errors of any kind. Also, if you’d prefer this be opened as a separate issue, I’m more than willing to do that. Don’t want to hijack something that might be ready to close. WINE: 3.7-pba dxvk: 0.50-1 from AUR NVIDIA drivers: 396.24

Attaching and apitrace of starting WoW. The game should be using d3d11, but they seemingly do something weird in startup. wow64.zip EDIT: It should be noted that the trace ends after the first frame, but the game continue to launch and display, not sure if there’s a trick to capturing more. EDIT 2: Combining with the logging info above, I’d assume the game creates and destroys several D3D instances, not quite sure why. Maybe to make injection of external graphics more difficult?