http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #11 from TheGeekn°72 <thegeekno72@gmail.com> --- (In reply to Stian Low from comment #3)
(In reply to TheGeekn°72 from comment #0) Welcome to Wine and Linux and liberation. Haha thanks! Truthfully, I've been on CachyOS for just over 5 months now, I only touch windows at work for reasons beyond my control
Wine has a staging repo that seems to have already worked around this bug many years ago: Staging patches are usually considered hacks as workarounds until more difficult fixes are solved: - https://gitlab.winehq.org/wine/wine-staging You may also build wine yourself to test latest changes not part of prebuilds yet: - https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine I don't even know how to build a package yet, most of the operations I've been doing while testing how to get the game to work has been replacing precise files or trying a different proton fork, I'll mention that to my dev friends, see how we can leverage this, though my final objective was to see how we could get that fixed officially "upstream" (am I using this right within present context?) so that any "John Gamer" could play the games blocked by this issue, hopefully (as with every software project of course) there is a definite breakthrough leading to a valid fix to this issue
Wine-staging applies patches atop latest wine via patchinstall.py: - https://gitlab.winehq.org/wine/wine-staging Since my issue stems from a Proton build, I would guess this is not compatible to my situation? eh, I'll figure something out.
(In reply to Stian Low from comment #4)
(In reply to TheGeekn°72 from comment #0) Wine has tests for expected behavior that must pass for solutions to be considered fixes vs hacks so most of the patches in staging likely fail some of those tests despite otherwise fixing many apps thus they are kept in separate staging repo until fixes that pass tests are provided. Often staging provides a basis of understanding for what is bugged and guides for fixes. So, hacks that solve specific bug instances, not everything, but provides info on what exactly is to be fixed, like laboratory experiments, got it
(In reply to Stian Low from comment #10)
(In reply to Stian Low from comment #9) experimental patches log typically indicates that staging is already used which contains the patch upstream so a bit confusing why it requires separate patching via github link. Maybe cachyos builds differently. I set Steam to use proton-cachy-slr which I keep updated to latest whenever a new build releases, though we got the game to work using a different proton fork (Proton-EM 11, as per the link to the commit I shared) in which my dev friend tweaked the wintrust dll in order to skip something? jump past the part that caused the game to fail launching? I'll test by using that modded wintrust in prootn-cachy-slr to make sure it's only that halting the game launch and not moving to a different proton fork altogether (since it occurred to me I did not test to make definitively sure that was it)
(In reply to Zeb Figura from comment #6)
Let's please try to stay on topic.
Proton is not supported in this bug tracker; please use upstream Wine or file bugs with Proton. I'd just like to say that I'm here because my dev friend (who maintains Proton-EM) told me wintrust was originally a WINE component and to get that fixed, it would have to be done upstream and thus to open an issue in here since this is the source of the file and not Proton projects, sorry if there was a better place to submit this issue, I was not made aware of it.
-- 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.