It's never too early for a little Wine, so grab a glass and come see what's new and improved with the latest development release.
Here's the highlights of what's new:
- Async interfaces and ACF files in the IDL compiler.
- Support for substorage transforms in MSI.
- RPC/COM marshalling fixes.
- Support for Unicode requests in WinHTTP.
- Shell Autocomplete optimizations.
When it comes to bug fixes, the Wine dev team noted 36 fixed. As always though, some may be from earlier releases only now being noticed. In particular for this release, they fixed some issues with BattlEye, Elite Dangerous Horizons, an issue with multiple different installers was solved, EVE Online had a fix and more.
Full details here.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
Comandante Ñoñardo 10 Nov 2018
At this rhythm, Proton will never leave Beta stage and the new Steam play will never be officially implemented.
0 Likes
At this rhythm, Proton will never leave Beta stage and the new Steam play will never be officially implemented.
No , this is not related. SteamPlay is in beta still because that showed
1-) How SteamRuntime is dated and needs to be updated
2-) SteamWorks support is not flawless, for example Soulcalibur VI issue
When these issues get ironed out ; probably that will be out of beta.
Also SteamPlay has a nice feature you probably didn't notice it ; it picks the known working Proton version for games. Which means , let's say DOOM 2016 whitelisted against Proton 3.7 ; it will use it unless you say otherwise to Steam Client.
Which eliminates regression possibility related to Wine.
6 Likes, Who?
SteamPlay has a nice feature you probably didn't notice it ; it picks the known working Proton version for games. Which means , let's say DOOM 2016 whitelisted against Proton 3.7 ; it will use it unless you say otherwise to Steam Client.What would really be needed would be a per-game setting.
Which eliminates regression possibility related to Wine.
You can change the used Proton version globally, but not per game, which can be rather annoying.
0 Likes
SteamPlay has a nice feature you probably didn't notice it ; it picks the known working Proton version for games. Which means , let's say DOOM 2016 whitelisted against Proton 3.7 ; it will use it unless you say otherwise to Steam Client.What would really be needed would be a per-game setting.
Which eliminates regression possibility related to Wine.
You can change the used Proton version globally, but not per game, which can be rather annoying.
I think you can. Each game gets their own proton prefix (aka wine prefix) on which you can do all the configurations you need. You can find it on: Steam/steamapps/compatdata/XXXX ("XXXX" is the game id).
0 Likes
That isn't really the convenience I'm looking for when using Steam Play. Anything other than plug'n'play and settings in the Steam interface itself won't do.SteamPlay has a nice feature you probably didn't notice it ; it picks the known working Proton version for games. Which means , let's say DOOM 2016 whitelisted against Proton 3.7 ; it will use it unless you say otherwise to Steam Client.What would really be needed would be a per-game setting.
Which eliminates regression possibility related to Wine.
You can change the used Proton version globally, but not per game, which can be rather annoying.
I think you can. Each game gets their own proton prefix (aka wine prefix) on which you can do all the configurations you need. You can find it on: Steam/steamapps/compatdata/XXXX ("XXXX" is the game id).
If I wanted that, I could just use Wine as usual. Which I still do for non-Steam software.
0 Likes
In this wine version steam login problem still remains
Last test with Pentium G3258 @ 4.1ghz + Artic Cooling Alpine 11 Plus
https://www.youtube.com/watch?v=zvz6TRJ-cF0
With Core i3 8350K Tri-Core @ 5.0ghz + CoolerMaster Hyper T4
https://www.youtube.com/watch?v=cUYxL4W-tXc
^_^
Last test with Pentium G3258 @ 4.1ghz + Artic Cooling Alpine 11 Plus
https://www.youtube.com/watch?v=zvz6TRJ-cF0
With Core i3 8350K Tri-Core @ 5.0ghz + CoolerMaster Hyper T4
https://www.youtube.com/watch?v=cUYxL4W-tXc
^_^
2 Likes, Who?
That isn't really the convenience I'm looking for when using Steam Play. Anything other than plug'n'play and settings in the Steam interface itself won't do.SteamPlay has a nice feature you probably didn't notice it ; it picks the known working Proton version for games. Which means , let's say DOOM 2016 whitelisted against Proton 3.7 ; it will use it unless you say otherwise to Steam Client.What would really be needed would be a per-game setting.
Which eliminates regression possibility related to Wine.
You can change the used Proton version globally, but not per game, which can be rather annoying.
I think you can. Each game gets their own proton prefix (aka wine prefix) on which you can do all the configurations you need. You can find it on: Steam/steamapps/compatdata/XXXX ("XXXX" is the game id).
If I wanted that, I could just use Wine as usual. Which I still do for non-Steam software.
Ok, but I just mentioned it because you say that you can't make configs per game when you can do it.
I agree that a Steam client tool would be better, but we also have third party tools that helps (https://asciinema.org/a/B1c5EdNOA3njQTRLtDVtYH9XK). From my point of view, proton is still much more easier than having to deal with plain wine and a big improvement to gaming on Linux.
1 Likes, Who?
Patreon
PayPal
How to install GE-Proton on Steam Deck, SteamOS, Linux
An idiots guide to setting up Minecraft on Steam Deck / SteamOS with controller support
See more from me