Another two weeks have gone by and the team hacking away on the compatibility layer Wine have a brand new development release available.
Need to know what Wine is? Here's a 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.
September 11 saw the release of Wine 5.17. The release highlights include:
- ADVAPI32 library converted to PE.
- Beginnings of an NDIS network driver.
- Still more restructuration of the console support.
They also noted 17 bug fixes. Solving issues either with this release or previously for: Deadlight: Director's Cut, Chrome / Chromium, World of Tanks, Risk II, Visual Studio 2019, Motocross Madness 2, The Sims Complete Collection and more. Full release notes here.
If you need help running multiple versions, Lutris is good for that. You can also get help in our Forum any time.
What custom build of proton do you recommend? ProtonGE slowed the releases, and I want to try newer versions of wine.
Quoting: fagnerlnWoah... Motocross Madness! That's (g)old, I played a lot when I was a teenager, it's funny.
What custom build of proton do you recommend? ProtonGE slowed the releases, and I want to try newer versions of wine.
I recommend using lutris and running any version of wine you like on whatever game you want and chances are there is a more recent script to overcome issues.
EDIT:
Wine Staging 5.17.2 has been released with 2 patches which allow compiling and compatibility on older distros. I'll see if I can get some tests up and running
Last edited by Avehicle7887 on 13 September 2020 at 1:34 pm UTC
However I think the priorities needs to be redirected.
Instead of supporting all the newest games, Wine should focus on solving every single annoyance that _still_ keeps happening with the old versions of Microsoft Office 2010 or 2013. This should be Wine if not Codeweavers priority in my humble opinion.
If you want to convert enterprises to Linux, MSOffice is unfortunately a must-have, and therefore efforts should be made to make it run 100% flawlessly; ten years and MSO 2010 still has some rough edges that makes it sometimes unusable or very buggy, hence not usable in a professional environment (and MSO 2013 crashes pretty often or just does not work great).
I'm always stumped to see the latest AAA games runs at 120fps while the wildly more used office 2013 still can't do basic stuff without crashing/being unresponsive :(
tl;dr: Instead of improving some new games that will be use by a few number of users, Wine and Codeweavers should focus their effort on supporting apps that are wildly used in the professional world like MS Office, so that more user could switch over to Linux while still being able to continue working with the tools their company chose.
Last edited by AciD on 13 September 2020 at 11:54 am UTC
Shadow Warrior 2 (CUSTOM ENGINE) - Videos still broken.
Darksiders Warmastered Edition (CUSTOM ENGINE) - Videos still broken.
Unfortunately no change yet since the previous release.
As a reminder - The purpose of my tests I are for testing in game videos using the Windows Media Foundation framework without any additional workarounds or files borrowed from Windows.
For the next Wine release I'll have a few new games I never tried before.
Last edited by Avehicle7887 on 13 September 2020 at 3:40 pm UTC
Quoting: AciDGetting more games to work is great, and I thank all the contributors to the Wine projet.
However I think the priorities needs to be redirected.
Instead of supporting all the newest games, Wine should focus on solving every single annoyance that _still_ keeps happening with the old versions of Microsoft Office 2010 or 2013. This should be Wine if not Codeweavers priority in my humble opinion.
If you want to convert enterprises to Linux, MSOffice is unfortunately a must-have, and therefore efforts should be made to make it run 100% flawlessly; ten years and MSO 2010 still has some rough edges that makes it sometimes unusable or very buggy, hence not usable in a professional environment (and MSO 2013 crashes pretty often or just does not work great).
I'm always stumped to see the latest AAA games runs at 120fps while the wildly more used office 2013 still can't do basic stuff without crashing/being unresponsive :(
tl;dr: Instead of improving some new games that will be use by a few number of users, Wine and Codeweavers should focus their effort on supporting apps that are wildly used in the professional world like MS Office, so that more user could switch over to Linux while still being able to continue working with the tools their company chose.
Businesses aren't likely to rely on software that isn't officially supported by it's vendor. For instance, running Office in Wine isn't supported by Microsoft. Its better to run this sort of software in a Windows virtual machine.
Plus there are a ton of Office alternatives for Linux that claim excellent Office file format support, including commercially supported ones like Only Office and SoftMaker.
Quoting: t3gI wonder what version of WINE the Proton team will use next, considering the latest version is based on 5.9
Hmm, that's interesting to know (I don't use Proton), a lot of stuff has changed after that version (such as not being able to apply esync using just the wine mainline code + staging). Also some 32bit games tend to crash for me at launch using the latest 5.1x builds (Risen 2, Darksiders 1).
I've been sticking with Wine 5.9 myself for now, I only use more recent builds to run tests but not actually using them for everyday gaming.
Quoting: Xaero_VincentBusinesses aren't likely to rely on software that isn't officially supported by it's vendor. For instance, running Office in Wine isn't supported by Microsoft.
This is true, plus Office 2010/2013 are quite old and a bit of a security issue now. I work for a non profit, and they recently made the switch from 2013 to Office 365. We've been through the whole process of justifying why it should be done.
See more from me