Breaking down barriers towards closer Windows compatibility, the Wine compatibility layer team have released the Wine 5.20 development release along with new features and fixes.
Need to know what Wine is? Here's our quick primer: it's a constantly improving compatibility layer that allows the running of Windows-only applications and games on Linux and other operating systems. It's one of the driving forces behind Steam Play Proton. Helping you to get whatever you need done on Linux, or perhaps so you don't have to give up that favourite game.
Here's the highlights:
- More work on the DSS cryptographic provider.
- A number of fixes for windowless RichEdit.
- Support for FLS callbacks.
- Window resizing in the new console host.
On top of that the usual assortment of bug fixes are here, with 36 getting the tick this time around. Some old solved in previous releases, some newer. These include: Metro Exodus, PS Remote Play, The Sims Complete Collection, Dungeons & Dragons Online, Saints Row 2 and lots more games seeing fixes across a few releases now being found to work better.
See the full release notes for Wine 5.20 here.
If you need help running multiple Wine versions, Lutris is good for that. You can also get help in our Forum any time.
I've compiled 5.20 Staging this morning, esync is definitely back to working. I tried to apply Fsync from Tk-Glitch's github but it wouldn't compile. For now, I'm happy to have esync + mfplat support on without needing too much work, I'll work on the Fsync issue.
As per my usual biweekly mfplat tests, I've yet to run those but I won't leave this post empty handed:
Aquanox: Deep Descent - FMV's are working out of the box, no workarounds required. I ran into a weird memory leak with 5.19 but 5.20 is smooth sailing and dxvk is also working fine.
Shadows: Awakening - I've previously reported FMV's working out of the box already with previous Wine releases, adding Esync provided me a solid 25+ fps increase in some areas. Have yet to test it for any instabilities.
Darksiders 1: Warmastered Edition - Crashes on startup. Works fine with Wine 5.8 + Microsoft mfplat dll's.
More to come....
Last edited by Avehicle7887 on 24 October 2020 at 2:39 pm UTC
Quoting: BielFPsDoes this also help Fsync? or not yet?
I just tried to enable Fsync and Esync through Lutris on prey with Wine 5.20 and both still gave me the error about uncompatible Wine version so I don't think that is fixed yet.
Last edited by PublicNuisance on 25 October 2020 at 4:50 am UTC
Quoting: BielFPsDoes this also help Fsync? or not yet?no idea if that helps, but fsync has always worked for me with the tkg builds. he probably backported though?
i have been using fsync with all the versions since 5.9 till now with no problems.
Last edited by andy155 on 25 October 2020 at 9:03 am UTC
Both of
autoreconf -f
tools/make_requests
are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.
HTH
Quoting: mickski56@Avehicle7887
Both of
autoreconf -f
tools/make_requests
are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.
HTH
Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?
Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?
I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton
Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?
Last edited by Avehicle7887 on 25 October 2020 at 9:58 am UTC
Quoting: Avehicle7887Quoting: mickski56@Avehicle7887
Both of
autoreconf -f
tools/make_requests
are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.
HTH
Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?
Yes that is correct apply all patches you require i.e staging + fsync then run
autoreconf -f
tools/make_requests
in your build dir then continue to build as you normally do.
Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?
I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton
Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?
Yes all other fsync patches are for older versions and will not apply to 5.20
I'm hoping some of the other patches will be updated as upstream wine settles down, but it hasn't happened yet.
Quoting: mickski56Quoting: Avehicle7887Quoting: mickski56@Avehicle7887
Both of
autoreconf -f
tools/make_requests
are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.
HTH
Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?
Yes that is correct apply all patches you require i.e staging + fsync then run
autoreconf -f
tools/make_requests
in your build dir then continue to build as you normally do.
Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?
I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton
Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?
Yes all other fsync patches are for older versions and will not apply to 5.20
I'm hoping some of the other patches will be updated as upstream wine settles down, but it hasn't happened yet.
It worked, thanks :)
In case anyone is also self compiling, steps I took:
Unpacked Wine source
Applied Staging patches
Applied 'fsync-unix-staging.patch'
Ran 'autoreconf -f'
Ran './tools/make_requests'
And the usual './configure' and 'make' commands. Can confirm FSync is working (Outward benefits a lot from this).
Happy Sunday everyone :)
See more from me