github-issue-templates
steam-runtime
Our great sponsors
github-issue-templates | steam-runtime | |
---|---|---|
4 | 86 | |
3,977 | 1,145 | |
- | 1.2% | |
3.6 | 6.6 | |
8 days ago | 6 months ago | |
Shell | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
github-issue-templates
-
Despite having just 5.8% sales, over 38% of bug reports come from Linux
From https://news.ycombinator.com/item?id=19686470 :
> GitHub and GitLab support task checklists in Markdown and also project boards [...]
> GitHub and GitLab support (multiple) Issue and Pull Request templates:
> Default: /.github/ISSUE_TEMPLATE.md || Configure in web interface
> /.github/ISSUE_TEMPLATE/Name.md || /.gitlab/issue_templates/Name.md
> Default: /.github/PULL_REQUEST_TEMPLATE.md || Configure in web interface
> /.github/PULL_REQUEST_TEMPLATE/Name.md || /.gitlab/merge_request_templates/Name.md
> There are template templates in awesome-github-templates [1] and checklist template templates in github-issue-templates [2].
steam-runtime
-
One Game, by One Man, on Six Platforms: The Good, the Bad and the Ugly
> 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
-
Chromebook Plus: more performance and AI capabilities
> 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.
-
i386 in Ubuntu Won't Die
I think they have something a bit like a container built into Steam: https://github.com/ValveSoftware/steam-runtime
-
How do you build games for Steam Linux 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
- Steam Desktop Client Update, Now with working hardware acceleration on linux!
-
Wine 8.1
> 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.
-
8 years ago, Linux's creator Linus Torvalds said, "Valve will save the Linux Desktop"
They ended up creating a common runtime for game devs targetting Steam on Linux: https://github.com/ValveSoftware/steam-runtime
-
How does Steam on Flatpak work?
Valve has a rather long document on the design of their runtime that goes into a hell of a lot of detail. The short answer is: graphics. It has to pass the host's graphics drivers through to the runtime, and a graphics driver built as part of a distro today may very well not run against the potentially ancient glibc living in the Steam runtime.
-
Win32 Is the Only Stable ABI on Linux
FWIW, these days Valve tries to solve same problems with their steam runtime[0][1]. Still doesn't seem easy, but looks like almost workable solution.
[0] https://github.com/ValveSoftware/steam-runtime
-
GLIBC update broke EAC for most games that use it
Haha I don't mind the downvotes. I know I'm right. And they know it's true. This issue in particular is part of the many reasons Steam had to come up with the "Steam Linux Runtime", a concept completely absent on Windows. 🤡
What are some alternatives?
flatpak - Linux application sandboxing and distribution framework
dxvk-native - D3D9/11 but it runs natively on Linux!
Proton - Compatibility tool for Steam Play based on Wine and additional components
flathub - Issue tracker and new submissions
SDL - Simple Directmedia Layer
steam-for-linux - Issue tracking for the Steam for Linux beta client
cmake-init-vcpkg-example - cmake-init generated executable project with vcpkg integration
dockcross - Cross compiling toolchains in Docker images
steamtinkerlaunch - Linux wrapper tool for use with the Steam client for custom launch options and 3rd party programs [Moved to: https://github.com/sonic2kk/steamtinkerlaunch]
amazing-github-template - 🚀 Useful README.md, LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, GitHub Issues, Pull Requests and Actions templates to jumpstart your projects.
JDK - JDK main-line development https://openjdk.org/projects/jdk
code-review-checklist - This code review checklist helps you be a more effective and efficient code reviewer.