• 9 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • Always porting not-yet-upstreamed patches to new release kernels is additional work to the upstreaming work towards the latest development tree. The Valve engineers interviewed around the very first Steam Deck announcement said their goal with moving from Debian to Arch was to minimize the patchset maintenance burden. Their approach surely has that goal in mind. There are only two variants of Steam Deck with minor differences between them. If backporting patches from newer kernels is less work than forward porting their patches, they just stay with that version for a while. Updates to drivers for hardware they don’t use and filesystems they don’t use aren’t relevant to them anyway.






  • Proton is the gateway drug to us getting more Linux native games.

    It’s not when Win32 apologists keep making insane claims how stable Proton is… “Proton is great, it just runs all the Windows games” is the mess that got us to the place where games we buy just start crashing suddenly because nobody of those developers realizes that each major release of Proton must be treated like its own OS with proper QA targeting that. Proton works great for old games because these old games no longer change. For modern games that still get updates Proton is a gamble because a reverse engineered version of the Windows API just isn’t stable.















  • The ONLY problem I have had with this, is the controller on the system itself defaults as controller 1, so SOME games it takes a little fiddling to use different controllers. But I have done this and it works great.

    I don’t know if you’re talking about in-game fiddling or Steam Input but to clarify for others here: Steam allows to reorder the controllers, so the thing I usually do at the beginning of game party is to move the Deck’s integrated inputs to the last place.