The ecosystem of games on Linux It has been growing for years.But it also suffers from a fundamental problem: too many projects working separately on the same challenges. In that context appears el Open Gaming Collective (OGC), a new organization that seeks to bring order and coordinate efforts among several of the most active initiatives in the Linux gaming scene.
This group was born with a clear idea: Stop reinventing the wheel in each gaming-oriented distribution and to advance together on key components such as the kernel, drivers, input tools, and the graphical gaming environment. This can be especially relevant for users who are increasingly opting for Linux-based PCs and handheld consoles as an alternative to Windows and proprietary systems.
What exactly is the Open Gaming Collective?
The Open Gaming Collective presents itself as a collaborative working group that brings together developers from some of the most gaming-focused Linux platforms. Its main objective is coordinate the development of critical components so that there are not ten teams solving the same problem in isolation, but a common base on which everyone can build.
The announcements published on official forums and blogs of the projects involved repeat the same idea: for too long, Gaming on Linux has been excessively fragmentedEach distribution applied its own patches to the kernel, maintained its own input tools, and packaged essential elements like GameScope in its own way, multiplying the work and generating differences in behavior between systems that, at their core, pursued the same gaming experience.
The projects that have joined the OGC
The group starts with a core membership that, in practice, already formed the heart of the Linux gaming ecosystem. Among the names that have been made public are:
- Bazzite (Universal Blue)A Linux distribution based on Fedora, designed to offer a solid gaming experience on both desktop and handheld consoles. Although its creators prefer not to call it a "distro" in the traditional sense, in practice it functions as a complete system, very popular as an alternative to SteamOS on devices like the Lenovo Legion Go.
- Chimera OS, a "console" focused system that boots directly into a living room-style interface and is designed so that the user only has to turn on the computer and play.
- nobara, a project also based on Fedora, well known in the gaming scene for integrating optimizations, patches and tools designed to play without the need for extensive manual configuration.
- Playtron and their Playtron OS system, which focuses on a unique gaming environment and is developing an operating system entirely dedicated to video games.
- Fyra Labs, responsible for projects such as Ultramarine, who contribute their experience in Fedora systems and in integrating modern technologies into the desktop.
- PikaOS, a proposal that has carved out a niche by focusing on performance and getting the most out of current hardware for gaming.
- ShadowBlip and ASUS Linux, initiatives closely linked to the support of specific hardware, such as ASUS gaming devices, which require specific adjustments to function optimally under Linux.
According to the explanations shared by the developers, There is no rigid hierarchy within the OGCAlthough Bazzite has been one of the projects that has stepped forward to announce the creation of the group, they point out that the idea is to operate with an approach of equality among the participants, sharing knowledge and work without a single "leader" setting the course.
Main objective: to reduce fragmentation of gaming on Linux
The raison d'être of the OGC is to address one of the most frequently mentioned problems when discussing Linux as a gaming platformFragmentation. Each distribution intended for gaming had spent years applying its own patches to the kernel, custom-packaging graphics drivers, adjusting compatibility with controllers, steering wheels and other peripherals, and assembling its own solutions to manage input on portable consoles.
This approach meant that efforts were duplicated time and time againOne team would work on compatibility with a specific handheld console model, another would add support for a particular steering wheel, a third would fix problems with certain Bluetooth controllers… and many of these changes weren't shared systematically. The result was that some games or devices would work fine on one distribution but not on another, without a clear explanation for the end user.
The proponents of the OGC are proposing a change of model: centralize work on key components such as the kernel, input tools, and essential packages like GameScope, and then distribute those improvements to all participating distributions. This way, a fix made for one platform can be ported much more directly to the others, avoiding the feeling that each project is working independently.
The "OGC Kernel": a shared effort at the heart of the system
One of the pillars of the initiative is the creation of a shared kernel across projects, known internally as the "OGC Kernel". Instead of each distribution maintaining its own branch of the Linux kernel with specific patches for handheld consoles, recent GPUs, or gaming peripherals, the goal is for those changes to be developed and tested in a common repository.
With this approach, the aim is that features such as Secure Boot supportThe improved compatibility with game controllers and joysticks, or the support for steering wheels and other accessories, does not have to be implemented repeatedly on each system, but is instead integrated once into that single kernel and can be used by all distributions that adhere to the project.
OGC officials also insist that their strategy is clearly "upstream first"This means that patches included in the OGC Kernel will be prepared from the outset with the intention of being submitted for review and inclusion in the official Linux kernel. Therefore, the goal is not to create a closed branch parallel to the main project, but rather to use collective effort to accelerate the integration of gaming-oriented improvements into the standard kernel version used by the entire community.
Open Gaming Collective wants to unify how controllers and input are managed: InputPlumber
Another of the most visible changes for users, especially in the case of Bazzite, has to do with the tools that manage input on portable consolesUntil now, Bazzite used its own solution called HHD (Handheld Daemon) to control aspects such as the response of the integrated controls, fan management, RGB lighting, or the behavior of the triggers and joysticks.
With the entry into the Open Gaming Collective, it has been decided abandon HHD and migrate to InputPlumberThis is an entry-level framework already used by other gaming-focused systems such as SteamOS, ChimeraOS, Nobara, Playtron GameOS, Manjaro Handheld Edition, and CachyOS Handheld Edition. This move is not just a technical change, but a clear commitment to a de facto standard within the Linux environment for portable devices.
For the user, the idea is that the functions they were used to with HHD integrate as much as possible into the Steam interface itself (Steam UI) and its associated tools. Parameters such as RGB lighting or fan control would be presented through more homogeneous menus, and for those options that cannot be integrated there, a simple visual overlay is planned, along the lines of what Bazzite users already knew, but supported by InputPlumber.
The developers have emphasized that, for those with particularly sensitive hardware or hardware dependent on specific libraries, There will be the possibility of maintaining previous versions for a while. They talk about a rollback and version locking system that will allow them to stay on previous libraries while they fix potential issues, something important to avoid leaving users with less common devices stranded.
Open Gaming Collective and cooperation on Valve's graphics stack and packages
Beyond the kernel and the input, the Open Gaming Collective also wants to coordinate work on the graphics stack and tools that revolve around Steam and ProtonOne of the points highlighted is the shared use and joint improvement of GameScope, the compositor used by many distributions to offer a more controlled full-screen game mode with console-like behavior.
In this field, the intention is that Bug fixes and optimizations are shared systematicallyInstead of each project applying its own patches to games, graphics drivers, or video stack components, issues such as performance differences between distributions or graphics glitches that only appear on a specific system and hardware combination should gradually decrease over time.
Bazzite has also expressed its willingness to share with the OGC the patches they have developed for Valve packagesThe idea is that the adjustments that have been incorporated to improve the experience with Steam and its tools should not be confined to a single distro, but should benefit all those that are part of the collective and, through the upstream approach, eventually reach the rest of the Linux community.
Practical changes to Bazzite and tests with new launchers
Bazzite's entry into the Open Gaming Collective is not just a statement of intent; it comes with several concrete changes to their roadmapIn addition to adopting the OGC Kernel and replacing HHD with InputPlumber, the team has begun experimenting with new game launcher options.
One of the movements that has been mentioned is the test of Faugus Launcher as a possible replacement for LutrisFaugus, a veteran tool for managing games from multiple stores and platforms on Linux, is currently being considered as an experiment. Bazzite's developers have indicated that if they ultimately decide to make the switch and establish Faugus as the default launcher, they will provide at least six months' notice to give users time to adjust.
These types of decisions show the extent to which Collaboration in the OGC does not imply giving up the personality of each distributionWhile the kernel, drivers, and low-level infrastructure are shared, each project remains free to decide how it organizes its interface, what tools it pre-installs, or what experience it offers the user when turning on the device.
One small problem and one big problem yet to be solved
As someone who games on Linux, a couple of things come to mind. First, Valve isn't part of the Open Gaming Collective, and SteamOS will continue to operate independently. Therefore, neither the OGC distributions will directly benefit from Valve's collaboration nor will SteamOS benefit from the OGC's.
The other problem is that of anti-cheat technologies: nothing can be done if they are implemented at the kernel level, so this will continue no matter how many forces come together.
Open Gaming Collective: one step closer to a less complex Linux for gaming
The creation of Open Gaming Collective This reflects a shift in mindset within the Linux gaming ecosystem: moving away from dispersing resources on repetitive tasks and towards a common technical layer that serves as the foundation for multiple systems. With shared efforts in the kernel, InputPlumber input, driver management, and the refinement of tools like GameScope, the platform is moving towards a scenario where Choosing a distro is more a matter of taste than basic compatibility.If the collaboration continues and the improvements truly reach the upstream, both European gamers and developers will find a more stable, consistent, and easier-to-adopt Linux for gaming, whether on desktop or portable consoles.