You need wine 3.14.
Ah, thanks. Maybe this should be stated in readme? It currently says
wine 3.10 or newer
The mingw builds work perfectly fine with 3.10, and the winelib builds are currently somewhat inofficial. There were also reports about the 32-bit winelib builds being highly unstable compared to the mingw builds.
Where can I find more details about those reports?
@jacekcw
I noticed unstable behaviour with d3d10 "dlls" once, currently beeng built with d3d11_dep https://github.com/doitsujin/dxvk/blob/master/src/d3d10/meson.build#L9
Now I'm using lib_d3d11 instead and can't say there is other problems (compared to the mingw builds) since 32 bit patches introduced.
But I have tested a few 32 bit games/apps only, and can't say there is no problems at all.
https://github.com/doitsujin/dxvk/issues/567#issuecomment-413326698 - this happen for both winelib and mingw builds.
It seems to me that using lib_d3d11 would be the right thing to do. Are you planning to upstream that?
I have already mentioned this several times, this change was present in my hint https://github.com/doitsujin/dxvk/issues/424#issuecomment-412335146 , and then in d3d10 branch.
But was changed then, I'm not sure for what reason, so leaving this for you and @doitsujin .
Building with lib_d3d11 breaks 32-bit mingw builds because it fails to find D3D11CoreCreateDevice for some reason.
Then possible solution can be something like
d3d10_deps = [ lib_d3dcompiler_43, lib_dxgi ]
d3d10_deps += meson.get_cross_property('winelib', false) ? lib_d3d11 : d3d11_dep
and using d3d10_deps in dependencies.
Edit: tested this and created PR https://github.com/doitsujin/dxvk/pull/608
dxgi.dllx1 2018-08
Before #520 winelib builds used to work fine.
Fedora 28, wine-staging 3.13