search

kakra / wine-proton

Proton'ized Wine, served hot, extra spicy: Please read README.md as a starting point
https://github.com/kakra/wine-proton/blob/rebase/proton_3.16/README.md
Other
35 stars 1 forks source link

Just Cause 3 issue #9

Open WernerAUT opened 5 years ago

WernerAUT commented 5 years ago

Hello first thanks for your work :)

I tried your wine-proton build, it runs on my LinuxMint 19.1 after installing some of the deb files you listed. I play JustCause 3 over Lutris Wine-Steam using Wine 4.0 Staging + Esync + DXVK 0.96 without issues, so i was hoping that with your wine-proton i would be able to kick wine steam and use Steam with proton-wine, but the Game doesn't even launch, so i think it is missing a patch from the staging, but i have no idea which one. As i searched around i saw that Just Cause 3 is using Denuvo and this can only work with wine staging because it has some patches which makes them working. I attached also the log i get using your build.

steam-225540.log

pchome commented 5 years ago

... it seems to happen after loading an audio API What if this is related to NVAPI? The game crashes shortly after loading cudart64_55.dll.

Threads, likely. The game trying to do it's usual work, but then interrupted by something.

Running your pre-built test shows failures

WINE dev's vs user's approach.

For WINE dev those failures are TODOs, but for regular app it should be failures. I don't know why it fails for command you posted, but I'm explicitly set export WINETEST_PLATFORM=windows in the runner script, and expecting failures.

kakra commented 5 years ago

@WernerAUT Okay, a fix for the controller regression is queued at https://source.winehq.org/patches/. I reported it, and Zeb found a strange bug and fixed it. Will be in my next update.

WernerAUT commented 5 years ago

@kakra thanks hadn't time to report it but was planing todo it this week, so thanks that you did :+1:

kakra commented 5 years ago

@WernerAUT FTR, I was seeing it too, now. It was a long-standing bug hidden behind some quirky behavior in xinput, and was only uncovered by the latest changes fixing yet another bug. Bug-ception? :-D