http://bugs.winehq.org/show_bug.cgi?id=46687 --- Comment #5 from Stian Low <wineryyyyy@gmail.com> --- Created attachment 81787 --> http://bugs.winehq.org/attachment.cgi?id=81787 Screenshot wine-4.0~rc2 for Gothic II with resolution 1368x768 available (In reply to Ken Sharp from comment #4) wine-4.0~rc2 tested (via Debian 13) via: https://dl.winehq.org/wine-builds/debian/pool/main/ Despite screenshot proving some wine-4.0 commit supported 1368x768, it's possible a regression was introduced during 4.0 that was fixed.
How on Earth is this fixed? How on Earth is such an ambiguous bug met with "How on Earth"?
It may have been fixed just as likely as invalid given the time diff between report and response. It may have been system/user specific vs wine but without a specific commit/regression test it seems unclear either way. But since it seems beyond Earthrealm comprehension why fixed may be suggested: - WINED3D was also reported bugged for wine 4.0 so not just DXVK - EnumAdapterModes provides d3d with resolutions based on shared libs external to d3d so if both were bugged then it seemed plenty possible wine may have introduced a regression. Unclear if DXVK shared same wined3d dependencies at the time.
OP never responded. DXVK is not supported. OP was never responded to until after nearly 3 years which is a bit too late.
OP seemed aware DXVK was not supported and provided WINED3D test cases also bugged. I gave OP benefit of the doubt that they knew what they were reporting. I have no pref regarding fixed or invalid status because neither seem of Outworld logic. Thanks for closing/resolving bug which is most relevant. -- 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.