http://bugs.winehq.org/show_bug.cgi?id=55775 --- Comment #47 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Chunhao Hung from comment #44)
I just want to share my opinion.
Thanks for feedback.
I understand that the MR-11398 workaround might break some applications, so I think it makes sense to make it opt-in through a config option, either an environment variable or a registry setting. Personally, I would prefer an environment variable.
`WINE_D3D_CONFIG=no_create_flags=0x800` is implemented like the others so environment variable overrides registry when defined: [Software\\Wine\\Direct3D] "csmt"=dword:00000001 "no_create_flags"=dword:00000800
This workaround seems to help video playback in a number of Unity games, so I think it is nice to have
Unity games seem far more common and impacted by `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` not failing vs vice versa for apps which may require `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` not failing. I'm still seeking any apps that require `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` so please let me know of any so that MR-11398 may be more thoroughly tested.
Because of that, I think it should only be treated as a temporary workaround, and it should be removable at any time once the proper implementation is done. Maybe it could also be documented on the Wine wiki with a clear note that it is temporary.
I implemented in such a way to hopefully keep for long term debugging convenience purposes in case issues like Haven video bugs are ever encountered again which may allow users to find solutions without requiring dev efforts to discover cause of problems. Keeping long term potentially risks users reporting bugs due to misusing the feature but users savvy enough to use WINE_D3D_CONFIG seem to be aware of the impact such as changing `WINE_D3D_CONFIG=csmt=0x2` -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.