https://bugs.winehq.org/show_bug.cgi?id=46020
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple issues with |Multiple issues with |Microsoft DirectX SDK DX11 |Microsoft DirectX SDK June |Demos |2010 DX11 Demos CC| |focht@gmx.net URL| |https://download.microsoft. | |com/download/A/E/7/AE743F1F | |-632B-4809-87A9-AA1BB3458E3 | |1/DXSDK_Jun10.exe Keywords| |download
--- Comment #2 from Anastasius Focht focht@gmx.net --- Hello Svyatpro,
most of the issues are likely already covered by existing tickets.
In case of 'failed to create Direct3D device' ('None of the requested D3D feature levels is supported on this GPU with the current shader backend.') messages use the 'forcefeaturelevel' command line option to set explicit override. Otherwise failed code paths on adapter enumeration lead to stuff like '(D3D_FEATURE_LEVEL)0' etc. passed in.
* D3D_FEATURE_LEVEL_11_0 * D3D_FEATURE_LEVEL_10_1 * D3D_FEATURE_LEVEL_10_0 * D3D_FEATURE_LEVEL_9_3 * D3D_FEATURE_LEVEL_9_2 * D3D_FEATURE_LEVEL_9_1
For example:
--- snip --- $ wine ./AdaptiveTessellationCS40.exe -forcefeaturelevel:D3D_FEATURE_LEVEL_11_0 ...
$ wine ./FluidCS11.exe -forcefeaturelevel:D3D_FEATURE_LEVEL_11_0 ...
$ wine ./NBodyGravityCS11.exe -forcefeaturelevel:D3D_FEATURE_LEVEL_11_0 ... --- snip ---
There are additional command line overrides to explicitly set things (API, adapter, etc). Read the source.
Regards