Comment by sitkack
5 months ago
Given that Windows games run faster via Proton on SteamOS, developers should prioritize targeting SteamOS APIs—not Windows. This ensures compatibility with Windows while maximizing performance. Game engines like Unity and Unreal must adopt SteamOS as the primary target, with CI systems rigorously testing both platforms. SteamOS, not Windows, should be the baseline for optimization.
Does Valve run a SteamOS CI/CD farm? I could see a Rust based template and library for calling into this set of APIs that you could upload your well structured project and it would build and test for all platforms. Rust would just be the skeleton, your game logic could be in anything Rust could link to.
I'm not sure that makes sense since the Windows API is the source of truth for how something works. If you make a game that works on Windows but not in Proton, Valve will push a fix that makes Proton work the same as Windows. But if you make your game work with Proton, but not Windows, you are relying on some quirk of Proton which isn't guaranteed to work in to the future and as soon as something else needs it to work the same as Windows, your game will break.
Test your game to make sure it works on the Steam Deck and avoid features that don't work on Proton, but you still have to primarily target Windows.
You would need to test on both of course. I am arguing that one should target the fast happy-path on Proton as Proton is a subset of the Windows APIs that runs faster than Windows.
Proton isn't a subset of the Windows APIs though. It's very likely that you could end up depending on behaviors which only exist in Proton.
3 replies →
The only stable ABI on SteamOS is Win32. Targeting anything else is asking for it to break over time.
Valve actually ships "stable ABI" Linux runtimes that Linux games and Proton are built against, so that they don't have to rely on distribution packages, similarly to Flatpak. They renew them every few years but they stay stable so that games built against a specific runtime keep working.
https://github.com/ValveSoftware/steam-runtime
That's not an ABI.
The ABI lives below Steam.
https://en.wikipedia.org/wiki/Application_binary_interface
I only referred to the API as exposed by Proton, no argument was made for targeting a different ABI.
Not sure Epic, who owns Unreal engine would be happy with optimizing for SteamOS and its API's after the whole debacle with Epic Store vs Steam.
Ignoring that, you know, 99% of users are running Windows and not SteamOS. Test on what your users run. Proton is just an implementation of Win32, you're still just targeting Windows.
Only 95.45% now (https://store.steampowered.com/hwsurvey) but yeah.
Over what time period? 99 -> 95.45 is a huge absolute number. Is most of that attributable to SteamDeck? Would that mean that 4.5% of active Steam users own a SteamDeck?
1 reply →