https://bugs.winehq.org/show_bug.cgi?id=52676
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #8)
Given that as clear 'not implemented' messages as the one that comes here without native d3dcompiler_47 are often the very reason for crashes (especially within the d3dx9/d3dcompiler set), 'strongly implied' would be putting it lightly, especially if you already suggested that in the original bug.
No. Forcing developers to discover by themselves that workarounds are required, or have been used, only wastes their time. If a clean prefix is explicitly requested, a clean prefix should be used. You should not assume that we will download the program, run it, realize that it needs a certain workaround, and assume that you used that workaround despite being asked not to.