

At my studio we maintain a native Linux version with a custom game engine, and it indeed takes a lot of time. I don’t consider Proton a viable option as we lost the ability to integrate with Linux-specific stuff such as Wayland APIs or better input, but I can definitely see the appeal of switching to Proton… if your team uses Windows. If you have some developers on Linux, you naturally get a Linux build (if using cross platform APIs ofc) and it’s actually faster to cross-compile a Windows build every once in a while (skip the slow ntfs I/O) and ship that. But it requires getting more of the team on Linux :)
Ah, yes… if only. I’ve upgraded internally SLR 1.0 -> SLR 3.0 but we can’t deploy it until a bug is fixed in the Steam client that causes, when we enable SLR 3, all Steam Decks to run the Linux build. Yes, Steam Decks run the Proton version, solely because the save file has different letter casing (yes I know it’s so annoying haha). We’ve spent quite some time on this and there’s no way to fix this without some folks losing their saves, and that is absolutely not an option. Soooo for now desktop Linux is stuck on runtime 1.0, and Steam Deck users are stuck on Proton. “fun” :/