https://bugs.winehq.org/show_bug.cgi?id=57834
Bug ID: 57834 Summary: Regression: Cyberpunk 2077 doesn't load with CyberEngine Tweaks Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shtetldik@gmail.com Distribution: ---
Between Wine 10.0 and 10.1 some regression occurred that causes Cyberpunk 2077 with cyber engine tweaks plugin not to load (without CET it works fine in 10.1 too).
CET is loaded in general by overriding version.dll as native, builtin.
The only suspicious error in the log that I see is this:
0184:fixme:graphics:ShutdownBlockReasonCreate (0000000000030056, L"Generating error report"): stub
I'm running the game with usual things like
* esync from staging * dxvk / vkd3d-proton
https://bugs.winehq.org/show_bug.cgi?id=57834
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #1 from joaopa jeremielapuree@yahoo.fr --- dvxk - proton are not supported in this tracker. Please report to them
Or try with vanilla wine in a fresh new prefix and report here again.
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #2 from Shmerl shtetldik@gmail.com --- This is not an issue with dxvk and dxvk-proton but with some upstream Wine component.
It's impossible to run the game suing vanilla wine for all practical purposes, so your proposal is not really helping troubleshoot the issue.
I'll try to bisect the bug.
https://bugs.winehq.org/show_bug.cgi?id=57834
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #3 from Shmerl shtetldik@gmail.com --- I found the first offending commit where things become broken:
https://gitlab.winehq.org/wine/wine/-/commit/33756286efb9e6b58831b01b9f2ef4d...
But I have no idea how that's related really.
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- Can you retry with current git?
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #5 from Shmerl shtetldik@gmail.com --- (In reply to Hans Leidekker from comment #4)
Can you retry with current git?
It works, thank you! Which commit is fixing it?
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #6 from Rafał Mużyło galtgendo@o2.pl --- (In reply to Shmerl from comment #5)
(In reply to Hans Leidekker from comment #4)
Can you retry with current git?
It works, thank you! Which commit is fixing it?
fe4ed10e, obviously.
https://bugs.winehq.org/show_bug.cgi?id=57834
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Regression SHA1| |33756286efb9e6b58831b01b9f2 | |ef4d7992a967a Fixed by SHA1| |fe4ed10ea18b064ed1431fbec5f | |36aa16d4a45f0 Summary|Regression: Cyberpunk 2077 |Cyberpunk 2077 doesn't load |doesn't load with |with CyberEngine Tweaks |CyberEngine Tweaks | Resolution|--- |FIXED
--- Comment #7 from Gijs Vermeulen gijsvrm@gmail.com --- Resolving FIXED, thanks for the report and bisection!
https://bugs.winehq.org/show_bug.cgi?id=57834
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 10.2.
https://bugs.winehq.org/show_bug.cgi?id=57834
FoX virtuousfox@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |virtuousfox@gmail.com
--- Comment #9 from FoX virtuousfox@gmail.com --- (In reply to Shmerl from comment #2)
This is not an issue with dxvk and dxvk-proton but with some upstream Wine component.
It's impossible to run the game suing vanilla wine for all practical purposes, so your proposal is not really helping troubleshoot the issue.
I'll try to bisect the bug.
Thanks for mentioning vkd3d-proton as just downloading prebuilt dlls from https://github.com/HansKristian-Work/vkd3d-proton/releases and putting them into game's folder made it finally work under wine. I wish someone would mention this in appdb.
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #10 from Shmerl shtetldik@gmail.com --- (In reply to FoX from comment #9)
Thanks for mentioning vkd3d-proton as just downloading prebuilt dlls from https://github.com/HansKristian-Work/vkd3d-proton/releases and putting them into game's folder made it finally work under wine. I wish someone would mention this in appdb.
That's really self explanatory if you are playing any games on Linux including using upstream Wine. Simply always enable dxvk + vkd3d-proton (I symlink them in the prefix so I can update them independently). They are giving best performance and compatibility so it's sort of redundant to mention it in app db, it's an implicit expectation at this point.
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #11 from FoX virtuousfox@gmail.com --- (In reply to Shmerl from comment #10)
(In reply to FoX from comment #9)
Thanks for mentioning vkd3d-proton as just downloading prebuilt dlls from https://github.com/HansKristian-Work/vkd3d-proton/releases and putting them into game's folder made it finally work under wine. I wish someone would mention this in appdb.
That's really self explanatory if you are playing any games on Linux including using upstream Wine. Simply always enable dxvk + vkd3d-proton (I symlink them in the prefix so I can update them independently).
There is nothing "self-explanatory" in using a fork of wine's core subsystem about existence of which I haven't even heard until now. And there is no ready-to-use distro package for it either, while I'm too lazy to make it (rpm spec-scripts for dll compilation are some obtuse bullshit, I'll tell you what) and keep it updated along with my custom dxvk package. So it's a boon that I did not have to build it too myself.
They are giving best performance and compatibility so it's sort of redundant to mention it in app db, it's an implicit expectation at this point.
No, this is an obscure hack and exactly what appdb is for. I haven't seen it even mentioned anywhere during web-wide search for hacks to make CP2077 playable, it was all about giving up on wine and using proton. Nobody even said which part of proton makes it work.
https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #12 from Shmerl shtetldik@gmail.com --- (In reply to FoX from comment #11)
No, this is an obscure hack and exactly what appdb is for. I haven't seen it even mentioned anywhere during web-wide search for hacks to make CP2077 playable, it was all about giving up on wine and using proton. Nobody even said which part of proton makes it work.
It's not an obscure hack and has been around for years at this point? dxvk and vkd3d-proton rely on modern features of Vulkan without limitations, which allows them to provide implementations of D3D9 - D3D12 that have very good performance.
Upstream Wine has to accommodate limitations of translating Vulkan to Metal on macOS which limits features of Vulkan it relies on, that's why on Linux upstream Wine's implementation leaves some performance on the table so to say.
If you weren't aware of that - well now you are. But this has been so for a quite a while already and it's the primary reason to always use dxvk + vkd3d-proton for gaming on Linux even if you use upstream Wine.
https://bugs.winehq.org/show_bug.cgi?id=57834
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #13 from Zeb Figura z.figura12@gmail.com --- (In reply to Shmerl from comment #12)
It's not an obscure hack and has been around for years at this point? dxvk and vkd3d-proton rely on modern features of Vulkan without limitations, which allows them to provide implementations of D3D9 - D3D12 that have very good performance.
Upstream Wine has to accommodate limitations of translating Vulkan to Metal on macOS which limits features of Vulkan it relies on, that's why on Linux upstream Wine's implementation leaves some performance on the table so to say.
Yeah, no, that's not why Wine "leaves some performance on the table".