http://bugs.winehq.org/show_bug.cgi?id=59847 --- Comment #6 from Artem S. Tashkinov <aros@gmx.com> --- (In reply to Zeb Figura from comment #5) Thanks for the clarification. My impression came mostly from practical testing and from old unresolved bugs rather than from a precise inventory of missing D3D10 features. I agree that "extremely incomplete" was probably too broad a statement if the remaining WineD3D problem here is specifically stream output overflow queries. That said, from a user perspective, long-standing gaps tend to push people toward workarounds such as DXVK, especially when those alternatives appear to work better for many real-world applications. I understand that third-party libraries are not Wine's responsibility and that this tracker is for Wine itself. To be clear, I cannot confirm that the crash at the end of the first graphics test occurs with Wine's own D3D10 implementation, because without overrides the application does not get that far. With WineD3D, it appears to fail earlier due to the missing stream output overflow query support tracked in bug 46594. So the later crash may well be DXVK-specific and outside the scope of Wine's bug tracker. But the no-overrides WineD3D failure still seems to be a real missing-feature issue, not an invalid report. Is the intended conclusion that this should simply be tracked under bug 46594 instead? There is also the separate complication that 3DMark Vantage appears to require native d3dx10_43.dll and d3dcompiler_43 to get this far. That makes relying on Wine's built-in components alone difficult even for an application from the D3D10 era. -- 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.