SSVOpenHexagon VS steam-runtime

Open Hexagon, re-implementation of Super Hexagon

Yeah, that is interesting. The github page is under an AFL license which contradicts his Steam EULA in multiple ways.

Open Hexagon

https://github.com/vittorioromeo/SSVOpenHexagon

Space Station 13 (and the remake, SS14) is an incredibly unique and feature rich multiplayer role playing game that takes place on a rickety space station in a wacky retro-futuristic setting. It's hard to recommend this game as the learning curve is more like a cliff, but it is far and away the best game that exists for creating unique (and often very funny) stories in. It has a long and complicated open source history that has fragmented it into several unique popular forks, but the most popular one that's fully open source nowadays is tgstation.

it's a clone of SuperHexagon (2012)

The product is dual-licensed -- the Steam version has an EULA, the GitHub repository is AFL Licensed.

The source code of the game is available here: https://github.com/SuperV1234/SSVOpenHexagon/

I was wondering if Open means truly Open - and it does https://github.com/SuperV1234/SSVOpenHexagon

Open Hexagon - Super Hexagon

> It turns out that unless the game is explicitly marked (by Valve reviewers), Steam Deck will use the Windows build + Proton even if a Linux version is available.

I found this which sounds like it's not the default, but is in fact a result of compatibility testing:

> If your game has gone through Steam Deck compatibility testing and the testers reported that the native Linux version didn't work (because of #579), then it might have been flagged to run the Windows binaries via Proton by default, instead of the native Linux version.

per https://github.com/ValveSoftware/steam-runtime/issues/585

> Where is it written that steam-run will magically execute most binaries without patching them?

Somewhere in here: https://github.com/ValveSoftware/steam-runtime

:p

But I do get what you're saying. Once Flakes are default, I hope people start a proper push to clear up documentation and streamline the development process. The end-result is amazing, and the perfect OS/packaging system for my needs. The means of getting there... need a lot of work. I'm along for the ride either way.

I think they have something a bit like a container built into Steam: https://github.com/ValveSoftware/steam-runtime

this is for steamworks API, my understanding is there's a separate SDK for consuming Linux dependencies like glibc. Like Soldier runtime, Sniper runtime, and so on. Am I wrong in thinking these are two separate SDKs? here's the link to the other SDK I'm talking about: https://github.com/ValveSoftware/steam-runtime

I'm not sure we can distribute a flatpak or an appimage through Steam. They have their own controlled environment called Steam Runtime (https://github.com/ValveSoftware/steam-runtime) in which I should compile to be sure it runs everywhere (very similar to what I am doing). Last time, I look at this, it wasn't very clear and they supported only old versions of GCC. But it seems the documentation improved and now that I succeeded in building a modern version of GCC in my own container, maybe I could do that in theirs.

I believe it's usable outside of Steam: https://github.com/ValveSoftware/steam-runtime though the instructions are not particularly clear. There's also a link to the APT repo they use as a reference: https://repo.steampowered.com/steamrt/

Looking at the Flatpak version, if you want to use Proton versions 5.13 or newer with Steam in Flatpak, you need to install Flatpak from backports https://github.com/ValveSoftware/steam-runtime/issues/294 . Using Flatpak saves having to install i386 if that matters to you.

> Game developers would be fine to target a single distro like Ubuntu 22.04.

Valve has its own container-only Linux distribution, called "Soldier Runtime" (https://github.com/ValveSoftware/steam-runtime); especially for games distributed on Steam, it probably makes more sense to target that distribution instead of Ubuntu.