Recently I showed off Halo Infinite running quite nicely online on the Steam Deck and now GE-Proton 7-27 that just went up makes the process even smoother and the campaign and videos now work too. This is another great step forwards.
Note: GE-Proton (formerly Proton-GE), is a community-built version of Proton not controlled by Valve. Not to be confused with Proton Experimental, which is from Valve.
Here's the new steps to get Halo Infinite working on Steam Deck:
- Opt into the Steam Deck Preview branch, if you don't see it then opt into the Beta on both options for the Client and OS
- In desktop mode: download GE-Proton 7-27 info in my previous guide (using ProtonUp-Qt)
- Set Halo Infinite to use GE-Proton7-27. Open Halo Infinite in your Steam Library and click the little Cog Icon -> Properties -> Compatibility, tick the box and select it from the dropdown.
The GE-Proton developer does mention that there will still be some issues, as the code to get it all working is very fresh. Right now honestly I wouldn't really recommend it, as the audio stutter is very distracting and there's still some noticeable graphical glitches but it's truly getting close now to being properly playable in all parts. I'll keep testing at each release to let you know when it's really good to go.
A bunch of other updates in GE-Proton 7-27 include:
- protonfix added for Halo CE mod tools (confirmed working) -- thanks Oro!
- protonfix added for Halo 2 mod tools (still has issues) -- thanks Oro!
- protonfix added for Halo 3 mod tools (confirmed working) -- thanks Oro!
- protonfix added for Halo 3: ODST mod tools (confirmed working) -- thanks Oro!
- Fall Guys protonfix updated to fix hang after EOS install on clean prefix setup.
- Witcher 2 protonfix added to fix failure to launch on systems with large core counts
- Farcry 3 protonfix added to fix failure to launch on systems with large core counts
- Battlefield Bad Company 2 protonfix removed, no longer needed and was causing DXVK not to load for the game
- Endless Space 2 protonfix removed, was causing game to crash. Game now works but videos are upside down (known proton issue)
- Gwent: Rogue Mage protonfix added
- SQUAD protonfix EAC blob updated to last-known working version
The Halo patches are suspected to have broken other games. If 7-27 breaks a game for you, please use a different version for now.
From the official discord:
Quoting: TheRiddickThey should add a option to SteamOS for Steam-Deck or handhelds where you can in compatibility section also choose OPTIMAL settings for specific fps, say options for 30/40/50 and 60fps which automatically apply specific optimized config files to the games with optimal presets. That be quite nice.
Why only SteamOS or Steam Deck? This seems useful on desktop too.
Quoting: itscalledrealityQuoting: TheRiddickThey should add a option to SteamOS for Steam-Deck or handhelds where you can in compatibility section also choose OPTIMAL settings for specific fps, say options for 30/40/50 and 60fps which automatically apply specific optimized config files to the games with optimal presets. That be quite nice.
Why only SteamOS or Steam Deck? This seems useful on desktop too.
Mainly because desktop hardware can vary wildly so a preset that is designed for 120 or 144fps may only be viable on specific hardware configurations.
But these handhelds are all using 6800U chips or what not so its pretty predictable what hardware bracket their in.
Even steam-deck-2 will be 7600U-7800U like APU chip and will still target 60fps (hopefully 1080p)
Quoting: GroganI built that the other night after seeing the new commits, and it was poo... periodic hitches (display, input, audio, everything). I tested his 7-27 build too and it was the same. My previous build I did on July 10 is good.
Following up, on what I said here, simply because I don't like to shit and run. I found out the real reason that was happening to me (it wasn't just GE Proton 7-27 but current Valve's too)
I'm not sure which (too many to cherry pick) but some of Valve's Wine patches seem to have made it so it doesn't like actually being able to get the priority it requests.
I took away my user's ability to lower nice (back to scheduling priority (-e) 0... ulimit I mean) and that cleared up the contention with current Protons.
(and the problem is the same for me with PREEMPT_RT kernels and normal ones, I had tested it with a normal kernel too... it's the niceness)
Last edited by Grogan on 31 July 2022 at 8:02 pm UTC
See more from me