Update: If you're having mouse problems since this update, there's a new Beta to opt into. See here for the details.
A brand new update to Steam Play Proton has arrived ahead of the weekend with Proton 4.11-10, giving out of the box play for Halo: The Master Chief Collection.
For Halo, you will need the Steam Beta Client if you're on an older distribution, plus online matchmaking still won't work due to Easy Anti-Cheat not supporting Steam Play Proton. However, single-player does work fine and you should be able to play with friends outside of matchmaking. I've tested Halo myself, and it does work first time without issues signing into Live:
Also added in this release of Proton is a claim of major mouse handling improvements. They said this improved the experience in Fallout 4, Furi, and Metal Gear Solid V. On the subject of input there's also force feedback improvements, an Xbox controller performance regression was solved, and fixes for multiple games having problems with controller mapping like Telltale games with Xbox controllers and Cuphead and ICEY when using PlayStation 4 controllers over Bluetooth.
There's a new integer scaling mode available, which they said will "give sharp pixels when upscaling". You can enable it with the "WINE_FULLSCREEN_INTEGER_SCALING=1" environment variable.
Apart from that there's a fix for Metal Gear Solid V hanging on launch, Trine 4 should no longer be locked to 30 FPS and a frequent IL-2 Sturmovik crash should be solved. They also updated D9VK, FAudio and pulled in some misc DXVK bugfixes.
See the changelog here. To get the update, your Steam client should download it automatically. If not, ensure you have Proton 4.11 installed in the Tools menu.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: NanobangUnfortunately, 4.11-10 messed up something with Borderlands 2 for me. Whilst Nvidia reported FPS around 120, it kinda looked as if every other frame was being displayed---jumpy, not smooth. Most disconcerting was the way a frame would flash on the screen from an entirely different sequence altogether, like a menu frame while running through Sanctuary or something.Does it run better under Proton or something? Borderlands 2 is a native game.
Rolling back to 4.2-9 fixed it right up. Would this sort of regression be best reported to the Proton github page, or should I just assume it'll get fixed up on a later iteration? Or maybe I'll just lock Borderlands 2 to 4.2-9 and call it good.
1 Likes, Who?
Quoting: 14Quoting: NanobangUnfortunately, 4.11-10 messed up something with Borderlands 2 for me. Whilst Nvidia reported FPS around 120, it kinda looked as if every other frame was being displayed---jumpy, not smooth. Most disconcerting was the way a frame would flash on the screen from an entirely different sequence altogether, like a menu frame while running through Sanctuary or something.Does it run better under Proton or something? Borderlands 2 is a native game.
Rolling back to 4.2-9 fixed it right up. Would this sort of regression be best reported to the Proton github page, or should I just assume it'll get fixed up on a later iteration? Or maybe I'll just lock Borderlands 2 to 4.2-9 and call it good.
If I have to guess (s)he runs it under Proton due to the HD-update of BL2 that we never got on Linux and which made the Linux-version no longer being able to connect to multiplayer servers.
1 Likes, Who?
Quoting: 14Quoting: NanobangUnfortunately, 4.11-10 messed up something with Borderlands 2 for me. Whilst Nvidia reported FPS around 120, it kinda looked as if every other frame was being displayed---jumpy, not smooth. Most disconcerting was the way a frame would flash on the screen from an entirely different sequence altogether, like a menu frame while running through Sanctuary or something.Does it run better under Proton or something? Borderlands 2 is a native game.
Rolling back to 4.2-9 fixed it right up. Would this sort of regression be best reported to the Proton github page, or should I just assume it'll get fixed up on a later iteration? Or maybe I'll just lock Borderlands 2 to 4.2-9 and call it good.
Borderlands 2 runs fine natively, but the latest DLC (Commander Lilith & the Fight for Sanctuary) does not have a Linux port.
1 Likes, Who?
Quoting: 14Quoting: NanobangUnfortunately, 4.11-10 messed up something with Borderlands 2 for me. Whilst Nvidia reported FPS around 120, it kinda looked as if every other frame was being displayed---jumpy, not smooth. Most disconcerting was the way a frame would flash on the screen from an entirely different sequence altogether, like a menu frame while running through Sanctuary or something.Does it run better under Proton or something? Borderlands 2 is a native game.
Rolling back to 4.2-9 fixed it right up. Would this sort of regression be best reported to the Proton github page, or should I just assume it'll get fixed up on a later iteration? Or maybe I'll just lock Borderlands 2 to 4.2-9 and call it good.
Good question! The short answer is: I think it plays about the same under Linux, which is great, and which is how I'd rather be playing.
The long answer is: Aspyr Media---the company that ported B2 to Linux---hasn't made the time to update the port since the graphics improvements were made, over 8 months ago. I regularly play B'lands 2 with my brother-in-law, who is on Windows, and the non-updated Linux B'lands 2 can't play with the updated Windows B'lands 2. When the Fight for Sanctuary DLC was released I switched over to the Windows B'lands 2 port under Linux. :)
0 Likes
Quoting: Liam DaweQuoting: NanobangUnfortunately, 4.11-10 messed up something with Borderlands 2 for me. Whilst Nvidia reported FPS around 120, it kinda looked as if every other frame was being displayed---jumpy, not smooth. Most disconcerting was the way a frame would flash on the screen from an entirely different sequence altogether, like a menu frame while running through Sanctuary or something.Never, ever assume a bug will just get fixed. Always report. This could be a d9vk regression.
Rolling back to 4.2-9 fixed it right up. Would this sort of regression be best reported to the Proton github page, or should I just assume it'll get fixed up on a later iteration? Or maybe I'll just lock Borderlands 2 to 4.2-9 and call it good.
Will do! thanks Liam!
0 Likes
This is, quite literally, a gamechanger. In this case, Fallout 4 finally works without jerking around the mouse it's impossible to hit anything or to walk in a straight line.
Now I'm playing Fallout 4 until January, with some breaks, like for working..
Now I'm playing Fallout 4 until January, with some breaks, like for working..
1 Likes, Who?
DanglingPointer Apr 22, 2020
20 years ago as a student in uni, Halo was unleashed on my original xbox! What an evolutionary game that was back then!
I would say it was perhaps the only reason I upgraded to the Xbox360 a decade and half ago. Haven't really used the 360 since! The game brings back many memories of playing with me best mates and cousins!
I bought the game (Halo MCC) last weekend and unfortunately it failed to work with proton 5.0-5 and 5.0-6 with mesa 19.2.8 with R9-290X.
I dropped it down to proton 4.11-13 and it worked perfectly with enhanced/remastered graphics on! It never went down below 59-60fps on Halo Reach! Finished Reach and will Start the original Halo next weekend! It's very well remastered! Well Reach at least!
Kisak-valve (dev triaging and fixing proton bugs from Valve) had a look at my problem and advised to upgrade mesa to his ppa or Oibaf's. It should hopefully fix the proton 5.0-x problem. Unfortunately I've been burned in the past by Oibaf and use my rig for work so can't risk unstable mesa ppa's.
I'm on Ubuntu-x stable mesa ppa. We probably will not get mesa 20.x until after the release of the next ubuntu LTS. Timo Altonen looks after that packaging and he hasn't gotten back to me. about it.
I did hear from Paulo Dias from Padoka stable ppa, and he said he's still supporting his ppa but has been waiting months for a fix for llvm 10.x which doesn't work properly with meson.
Anyways, the game works with R9-290X GCN 1.1 on proton 4.11-13 with mesa 19.2.8
Enjoy!
Last edited by DanglingPointer on 22 April 2020 at 6:25 am UTC
I would say it was perhaps the only reason I upgraded to the Xbox360 a decade and half ago. Haven't really used the 360 since! The game brings back many memories of playing with me best mates and cousins!
I bought the game (Halo MCC) last weekend and unfortunately it failed to work with proton 5.0-5 and 5.0-6 with mesa 19.2.8 with R9-290X.
I dropped it down to proton 4.11-13 and it worked perfectly with enhanced/remastered graphics on! It never went down below 59-60fps on Halo Reach! Finished Reach and will Start the original Halo next weekend! It's very well remastered! Well Reach at least!
Kisak-valve (dev triaging and fixing proton bugs from Valve) had a look at my problem and advised to upgrade mesa to his ppa or Oibaf's. It should hopefully fix the proton 5.0-x problem. Unfortunately I've been burned in the past by Oibaf and use my rig for work so can't risk unstable mesa ppa's.
I'm on Ubuntu-x stable mesa ppa. We probably will not get mesa 20.x until after the release of the next ubuntu LTS. Timo Altonen looks after that packaging and he hasn't gotten back to me. about it.
I did hear from Paulo Dias from Padoka stable ppa, and he said he's still supporting his ppa but has been waiting months for a fix for llvm 10.x which doesn't work properly with meson.
Anyways, the game works with R9-290X GCN 1.1 on proton 4.11-13 with mesa 19.2.8
Enjoy!
Last edited by DanglingPointer on 22 April 2020 at 6:25 am UTC
1 Likes, Who?
Quoting: DanglingPointer(snip)Ha, I saw your comments on the issue tracker :)
I'm on the fence for this one. I'm more or less in the same case as you (having bought an x360 for halo). That said, I don't have much time for playing, so I'll wait an probably buy the full collection at a discount (plus there's no splitscreen support for now, what a shame).
1 Likes, Who?
Patreon
PayPal
See more from me