[Bug 51062] New: Warframe through Lutris no longer has dx12 option in Launcher with wine staging 6.7
https://bugs.winehq.org/show_bug.cgi?id=51062 Bug ID: 51062 Summary: Warframe through Lutris no longer has dx12 option in Launcher with wine staging 6.7 Product: Wine-staging Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhu543369(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Running Warframe through Lutris with a custom runner pointing to wine-6.6-staging/bin/wine64 and in the launcher options, dx12 experimental is available. Switch runner to wine-6.7-staging/bin/wine64 and the launcher no longer has a dx12 experimental option, just dx11. World of Warcraft through Lutris with the 6.7 runner works fine with dx12. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Sveinar Søpler <cybermax(a)dexter.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #1 from Sveinar Søpler <cybermax(a)dexter.no> --- I think this would be a "lutris bug", since there is no "dx12 experimental" in wine-staging that you can "choose" in any meaningful way? NOTOURBUG? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- Lutris and other wrappers are not supported in this bug tracker; please test with wine-staging or (ideally) upstream wine, or else report this bug to the Lutris project. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Kron4ek <kron4ek(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kron4ek(a)gmail.com --- Comment #3 from Kron4ek <kron4ek(a)gmail.com> --- This issue happens without Lutris as well, i tested with Wine-Staging 6.7 and with vanilla Wine 6.7 - both are affected. How to reproduce: 1. Download Warframe launcher (Warframe.msi). The game itself is not needed, only the launcher. 2. Install vkd3d-proton to your Wine prefix 3. Set Windows version to 10 in winecfg 4. Disable libglesv2 in winecfg, otherwise the launcher window will be black (https://bugs.winehq.org/show_bug.cgi?id=44985) 5. Run Warframe.msi and go to the launcher settings With Wine 6.6 DirectX 11 and DirectX 12 renderers are available in the launcher settings menu, but with 6.7 release there is only DirectX 11. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- vkd3d-proton is also not supported in this bug tracker; please report bugs to the vkd3d-proton developers. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #5 from Kron4ek <kron4ek(a)gmail.com> ---
vkd3d-proton is also not supported in this bug tracker; please report bugs to the vkd3d-proton developers.
I don't think this is a vkd3d-proton bug. I used the same vkd3d-proton version with both Wine 6.6 and 6.7. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Kron4ek from comment #5)
vkd3d-proton is also not supported in this bug tracker; please report bugs to the vkd3d-proton developers.
I don't think this is a vkd3d-proton bug. I used the same vkd3d-proton version with both Wine 6.6 and 6.7.
That may be true, but this may also be a change in Wine exposing a bug in vkd3d-proton. Without knowledge of what the breaking change is, or what vkd3d-proton is doing, it's hard to say. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lvb.crd(a)protonmail.com --- Comment #7 from Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> --- (In reply to Kron4ek from comment #3)
4. Disable libglesv2 in winecfg, otherwise the launcher window will be black (https://bugs.winehq.org/show_bug.cgi?id=44985)
Disabling libglesv2 does not completely solve the problem, instead, the best option would be to disable "Launcher GPU Acceleration" in the launcher settings. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #8 from Kron4ek <kron4ek(a)gmail.com> --- I figure out that the first bad commit is a27d5bae114eef5352b699ee38975bc8793b4dcb (winevulkan: Use standard CRT memory allocators.). And i see "free(): invalid size" in the Wine output when i run the launcher. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #9 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Kron4ek from comment #8)
I figure out that the first bad commit is a27d5bae114eef5352b699ee38975bc8793b4dcb (winevulkan: Use standard CRT memory allocators.). And i see "free(): invalid size" in the Wine output when i run the launcher.
Can't be that one, cos i tried with my custom proton'ish hack wine-6.5, and i do not have that commit at all. I do however have the same problem with only being able to choose DirectX11. Booting my older staging-6.4 wine, i could choose d3d12 tho. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #10 from Kron4ek <kron4ek(a)gmail.com> --- (In reply to Sveinar Søpler from comment #9)
(In reply to Kron4ek from comment #8)
I figure out that the first bad commit is a27d5bae114eef5352b699ee38975bc8793b4dcb (winevulkan: Use standard CRT memory allocators.). And i see "free(): invalid size" in the Wine output when i run the launcher.
Can't be that one, cos i tried with my custom proton'ish hack wine-6.5, and i do not have that commit at all.
I do however have the same problem with only being able to choose DirectX11.
Booting my older staging-6.4 wine, i could choose d3d12 tho.
Well, at least for me the issue definitely starts to happen with the commit i mentioned, because compiling from the earlier commit (3b63afeeba29a76e19eee41a90c9a32838645cf9) fixes the issue. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #11 from Sveinar Søpler <cybermax(a)dexter.no> --- Wow.. interesting phenomenon. wine @3b63afeeba29a76e19eee41a90c9a32838645cf9 staging @d805441f461d2f156a3c786e79fd1a4899f83f2b vkd3d-proton @3ed3526332f53d7d35cf1b685fa8096b01f26ff0 Working! I add a27d5bae114eef5352b699ee38975bc8793b4dcb on top of my tree and recompile without doing anything else.. smack - no d3d12 option. As i said above - on my own custom wine-staging-6.5 tree, i do not have that commit at all, but i have plenty of other vulkan hacks/tweaks (proton-fshack+++) and it does not work with d3d12 either... Something else at play here i think. Maybe some memory offset thingy that makes winevulkan not load certain extensions that vkd3d-proton checks for maybe? Ill post some logs with WINEDEBUG=-all,+dxgi,+vulkan later. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #12 from jhu543369(a)gmail.com --- Interesting concept, except (at least with my setup) World of Warcraft loads d3d12.dll and runs smoothly on wine-staging 6.7. I don't anything else outside steam that uses dx12 to test.. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #13 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to jhu543369 from comment #12)
Interesting concept, except (at least with my setup) World of Warcraft loads d3d12.dll and runs smoothly on wine-staging 6.7. I don't anything else outside steam that uses dx12 to test..
Yeah, WoW loads just fine with vkd3d-proton, so it is some weird setup in Warframe that faulters. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #14 from Zebediah Figura <z.figura12(a)gmail.com> --- Unless this can be reproduced with upstream vkd3d and without third-party DLLs and workarounds, please take this discussion to another channel. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #15 from jhu543369(a)gmail.com --- Ok not sure what you mean by "upstream vkd3d", but I have tried every release of vkd3d from the git (including 2.3.1) as well as copying over the d3d12.dll from proton (current proton experimental, 6.3-2, 5.13-6 and 5.0-10) with both unpatched wine-staging 6.6 and 6.7. The issue only occurs with 6.7. I followed Kron4ek's installation so there are no third-party wrappers or dll's being loaded and deleted the prefix between versions (thank god for unlimited fibre high speed internet). I have reported the issue in the vkd3d-proton bug tracker as well. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #16 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to jhu543369 from comment #15)
Ok not sure what you mean by "upstream vkd3d", but I have tried every release of vkd3d from the git (including 2.3.1) as well as copying over the d3d12.dll from proton (current proton experimental, 6.3-2, 5.13-6 and 5.0-10) with both unpatched wine-staging 6.6 and 6.7.
The issue only occurs with 6.7. I followed Kron4ek's installation so there are no third-party wrappers or dll's being loaded and deleted the prefix between versions (thank god for unlimited fibre high speed internet). I have reported the issue in the vkd3d-proton bug tracker as well.
You are not using vkd3d, but rather vkd3d-proton, which is a fork. Upstream vkd3d is distributed from winehq.org; the latest release is 1.2. I would like to once again remind that the only projects supported by this bug tracker are wine, wine-staging, wine-mono, wine-gecko, and vkd3d. Wrappers such as lutris and proton, and third-party DLLs such as dxvk and vkd3d-proton, are not supported. We can't be held accountable for anything these projects are doing. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #17 from Kron4ek <kron4ek(a)gmail.com> --- (In reply to Zebediah Figura from comment #14)
Unless this can be reproduced with upstream vkd3d and without third-party DLLs and workarounds, please take this discussion to another channel.
There is no DX12 renderer in the Warframe launcher options with upstream vkd3d as well (tried 1.2 and latest git version), but it's missing even with older Wine versions, even though other DX12 applications seem to work fine (tested UE4 Elemental Demo in DX12 mode and it works). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 --- Comment #18 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Kron4ek from comment #17)
(In reply to Zebediah Figura from comment #14)
Unless this can be reproduced with upstream vkd3d and without third-party DLLs and workarounds, please take this discussion to another channel.
There is no DX12 renderer in the Warframe launcher options with upstream vkd3d as well (tried 1.2 and latest git version), but it's missing even with older Wine versions, even though other DX12 applications seem to work fine (tested UE4 Elemental Demo in DX12 mode and it works).
I also tested wine @3b63afeeba29a76e19eee41a90c9a32838645cf9 aswell as wine-staging-6.5 and wine-staging-6.7 with upstream vkd3d @8b99fc66d3b4dba3d213c7115aa79a22ece38719 No D3D12 option available in any of them. So in a sense, vkd3d does not work AT ALL vs. vkd3d-proton works with <= 3b63afeeba29a76e19eee41a90c9a32838645cf9. So it could be said that fixing D3D12 support for Warframe with upstream vkd3d would be nice :) (But then better suited for a new bug-report) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=51062 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #19 from Zebediah Figura <z.figura12(a)gmail.com> --- Closing invalid; please feel free to report a new bug against upstream vkd3d. -- 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.
participants (1)
-
WineHQ Bugzilla