Linux Gaming Roadmap: The Complete MusaBase Guide Series 2026
Linux gaming used to be a punchline. Install a game, hope for the best, accept that most things would not work. That era is over. Thanks to Valve's investment in Proton, the open source community behind Wine, and tools like Bottles, the majority of Windows games now run on Linux. Some of them run better on Linux than they do on Windows.
I have been gaming on Linux for over a year now, on the same hardware, side by side with Windows. I have run everything from Red Dead Redemption 2 to Spider-Man: Miles Morales to Need for Speed Heat. Some surprised me. Some frustrated me. All of it taught me how Linux gaming actually works in the real world, not just in theory.
This page covers the complete MusaBase Linux gaming series. Whether you are just starting out with Steam and Proton, running Epic and GOG games through Bottles, going deeper with raw Wine, or trying to squeeze every frame out of your GPU with CoreCtrl and MangoHud, there is a guide here for that.
This is part of the MusaBase Linux series. All guides are tested on real hardware with an AMD RX 580 and Intel i5-4460 running Arch Linux.
| Guide | What It Covers | Best For | Difficulty |
|---|---|---|---|
| Steam and Proton | Running Steam games on Linux | Most Linux gamers | Beginner |
| Bottles | Epic, GOG, and standalone .exe games | Non-Steam library owners | Beginner |
| Wine | Full manual control over compatibility | Advanced users and troubleshooters | Advanced |
| CoreCtrl and MangoHud | GPU overclocking and performance monitoring | Anyone who wants more FPS | Intermediate |
| Linux vs Windows Gaming | Real-world performance comparison | Anyone deciding whether to switch | Reading only |
New to Linux gaming? Start with Steam and Proton. Everything else builds on top of that foundation.
Part 1: Steam and Proton
Proton is Valve's compatibility layer built on top of Wine. It is what makes Steam games work on Linux without you having to configure anything manually. You enable it once in Steam settings, and your entire Steam library becomes available to play. That simple. Most games just work. Some need a specific Proton version. A few do not work at all because of kernel-level anti-cheat. But the majority of your Steam library will run, and many titles run just as well as they do on Windows.
Why Proton Changed Everything for Linux Gaming
Before Proton, running a Windows game on Linux meant setting up Wine manually, finding the right configuration, installing dependencies, and hoping for the best. Proton packaged all of that into something Steam handles automatically. Valve also built Proton-GE, a community fork with extra patches for games and codecs that the official Proton version does not cover. Installing Proton-GE through ProtonUp-Qt takes two minutes and unlocks compatibility for a wider range of games. The guide covers both.
What the Guide Covers
Enabling the multilib repository on Arch Linux, installing Steam with the correct 32-bit libraries, enabling Proton for your entire Steam library, installing and managing custom Proton versions with ProtonUp-Qt, checking game compatibility on ProtonDB before you buy, and setting per-game launch options to solve specific compatibility issues. The guide also covers how to use Proton Experimental for games that need cutting-edge fixes before they land in the stable release.
Quick Facts
- 🎮 Game Source: Steam library only
- ⚙️ Setup Time: ~20 minutes
- 📊 Difficulty: Beginner
- ✅ Works With: Most Steam titles
- ❌ Does Not Work With: Games with kernel-level anti-cheat (Valorant, Fortnite, Call of Duty)
- 🔧 Best Tool For: Anyone starting Linux gaming for the first time
🔗 Full Guide: How to Run Windows Games on Linux Using Steam and Proton
Part 2: Bottles (Non-Steam Games)
Steam is not the only game store. A huge portion of the Windows game library lives on Epic Games, GOG, EA App, and various standalone installers. Proton does not cover those because Proton only works inside Steam. That is where Bottles comes in. Bottles is a graphical tool that creates isolated Wine environments (called bottles) for each game or application. You install your Epic or GOG game inside a bottle, configure the right runner, and launch it. It is the closest thing to a plug-and-play experience for non-Steam Windows games on Linux.
Why Bottles Instead of Just Wine
Wine gives you full control but requires manual configuration for everything. Bottles wraps that same Wine technology in a graphical interface that handles prefix creation, runner management, dependency installation, and application launching for you. You can install Proton-GE, Soda, or Sys-Wine as runners inside Bottles. For most non-Steam games, Bottles is the right starting point before going to raw Wine. I used it for Epic Games titles for most of the year and it handled the majority of them without any terminal work at all.
What the Guide Covers
Installing Bottles via Flatpak, creating your first gaming bottle with the right runner, installing and running Epic Games titles through Heroic Games Launcher inside Bottles, handling GOG games and standalone .exe installers, managing dependencies like Visual C++ runtimes and DirectX components through the Bottles interface, and troubleshooting the most common issues like missing DLLs and launcher authentication problems.
Quick Facts
- 🎮 Game Source: Epic, GOG, EA, standalone installers, any .exe
- ⚙️ Setup Time: ~15 minutes
- 📊 Difficulty: Beginner to Intermediate
- ✅ Works With: Most non-Steam Windows games
- 🔧 Best Tool For: Users with large Epic or GOG libraries
🔗 Full Guide: How to Run Non-Steam Games on Linux with Bottles (Epic, GOG, EXEs)
Part 3: Wine (Manual Control)
Steam and Bottles are convenient. But sometimes you want raw control. Wine is the core compatibility layer that everything else is built on. Proton is Wine with Valve's patches. Bottles is a graphical interface around Wine. When you use Wine directly, you are working with the foundation itself. You create your own Wine prefixes, install exactly the components each game needs, configure DXVK and VKD3D yourself, and run games from the terminal with full visibility into what is happening. When I first ran a game with raw Wine, I was nervous. I typed the command, held my breath, and it worked. It was not pretty at first, but understanding exactly what was happening under the hood was addictive.
Why Learn Wine Directly
When Bottles fails or Steam cannot run something, Wine is what you fall back to. Understanding Wine also makes you better at using Bottles and Proton because you understand what they are actually doing. Wine is also where you install DXVK for DirectX 9 to 11 translation to Vulkan and VKD3D-Proton for DirectX 12. These translation layers are the reason Linux gaming performance has caught up with Windows in so many titles. With DXVK enabled, Ori and the Will of the Wisps went from constant stuttering to buttery smooth at double the FPS. That difference is real and the Wine guide shows you exactly how to set it up.
What the Guide Covers
Installing Wine system-wide on Linux with multilib support, the difference between stable Wine and wine-staging, creating Wine prefixes manually and through WineGUI, installing DXVK and VKD3D-Proton for DirectX support, installing Visual C++ runtimes, .NET frameworks, DirectX components, and fonts using Winetricks, running games from both the terminal and WineGUI, and understanding how Wine architecture relates to Proton and Bottles so you can make informed choices about which tool to use for each situation.
Quick Facts
- 🎮 Game Source: Any Windows executable
- ⚙️ Setup Time: ~1 hour for full setup
- 📊 Difficulty: Advanced
- ✅ Works With: Most Windows games and applications
- 🔧 Best Tool For: Users who want full control or need to troubleshoot compatibility issues that Bottles and Proton cannot solve
🔗 Full Guide: Windows Games on Linux with Wine: DXVK, Prefix and Performance
CoreCtrl and MangoHud: GPU Overclocking and Performance Monitoring
On Windows, MSI Afterburner is the standard tool for GPU overclocking and in-game performance monitoring. It does not run on Linux. The Linux equivalents are CoreCtrl for GPU overclocking and power management, and MangoHud for the in-game performance overlay that shows FPS, CPU usage, GPU temperature, VRAM usage, and frame times in real time. Together they cover everything MSI Afterburner does, and in some ways they give you more control, especially if you are on an AMD GPU where the open-source drivers expose more tuning options than AMD's own Windows software does.
Why This Matters for Gaming Performance
Knowing your actual FPS, frame times, and GPU temperature while playing changes how you configure your games. MangoHud gives you that information directly on screen without alt-tabbing. CoreCtrl lets you push your GPU's clock speeds and power limits to get more performance out of the same hardware. On my RX 580, CoreCtrl unlocked meaningful performance headroom that the default AMD driver settings left on the table. The guide covers the full setup including enabling the right kernel parameters for CoreCtrl to work with AMD GPUs.
What the Guide Covers
Installing CoreCtrl and configuring it to launch with administrator privileges at startup, enabling the amdgpu.ppfeaturemask kernel parameter that unlocks AMD GPU overclocking options, setting up GPU profiles for gaming versus idle, installing MangoHud and enabling it globally for all Vulkan and OpenGL games or per-game through Steam launch options, configuring the MangoHud overlay layout to show exactly the information you care about, and using both tools together for a complete performance tuning and monitoring workflow.
Quick Facts
- 🖥️ GPU Support: AMD (best support), NVIDIA (MangoHud works, CoreCtrl limited)
- ⚙️ Setup Time: ~30 minutes
- 📊 Difficulty: Intermediate
- 🔧 Best For: Anyone who wants MSI Afterburner functionality on Linux
🔗 Full Guide: MSI Afterburner Alternative on Linux: CoreCtrl and MangoHud for AMD GPUs
Linux vs Windows Gaming: A Year of Real Testing
After a full year of gaming on both Linux and Windows on the same hardware, I wrote down exactly what I found. Not what the benchmarks say. Not what the marketing says. What actually happened when I sat down to play Red Dead Redemption 2, Spider-Man: Miles Morales, Ori and the Will of the Wisps, Quantum Break, and Need for Speed Heat on both operating systems and compared them side by side.
The short version: Linux won on smoothness for Vulkan-native titles. Windows won for launcher-heavy games and anything with kernel-level anti-cheat. Neither is a clear winner across the board. The full comparison has the actual numbers, the specific launch options I used, and the honest explanation of why each result happened the way it did.
🔗 Full Comparison: Gaming on Linux vs Windows: A Year of Gaming on Both OS
Which Tool Should You Use?
This is the most common question people have when they start gaming on Linux. Here is the honest answer based on a year of actually using all of them.
- If your game is on Steam: Use Steam with Proton. Enable Proton in Steam settings, check ProtonDB for your specific game, and install Proton-GE if the default version does not work. This covers the majority of the Windows gaming library and requires the least setup of any option here.
- If your game is on Epic, GOG, or EA: Use Bottles. Create a gaming bottle, use Heroic Games Launcher inside it for Epic titles, and handle GOG and standalone installers through Bottles directly. The graphical interface handles most of the configuration for you.
- If Bottles fails or you need full control: Use Wine directly. Create a manual prefix, install DXVK and VKD3D, and run the game from the terminal. This is more work but it is also where you can solve problems that Bottles cannot.
- If you want to squeeze more performance out of your GPU: Set up CoreCtrl and MangoHud regardless of which tool you use for running games. These work alongside all of the above.
- If you are not sure whether Linux gaming is worth it for your library: Read the Linux vs Windows comparison first. It covers exactly which types of games work well, which do not, and what the real performance difference looks like on mid-range hardware.
One practical tip I will add from experience: always check ProtonDB before spending time configuring a game. If the community reports say a game runs perfectly on Proton, you can skip the Wine and Bottles setup entirely and just use Steam. If it says borked, save yourself the frustration and boot into Windows for that one title.
Frequently Asked Questions About Gaming on Linux
Can I play Valorant, Fortnite, or Call of Duty on Linux?
No. These games use kernel-level anti-cheat systems (Vanguard, Easy Anti-Cheat, Ricochet) that do not work under Wine or Proton. Unless the developer explicitly enables Linux support, they will not run. This is the single biggest limitation of Linux gaming and it is not something that can be fixed from the Linux side. Check Are We Anti-Cheat Yet for the current status of specific games. Some titles like The Finals and Hunt: Showdown have enabled Proton support, so the list is slowly growing.
Is Linux gaming performance close to Windows?
For Vulkan-native games with DXVK or VKD3D, yes. In my own testing, Spider-Man: Miles Morales ran 30 to 40 percent faster on Linux than on Windows on the same hardware. RDR2 ran 15 to 20 percent faster during open world traversal on Linux. The Mesa drivers for AMD GPUs are exceptionally well optimized for Vulkan workloads. For games that rely on Windows-specific launchers or unconventional engines, Windows still has an advantage. The comparison guide has the full numbers.
Do I need Arch Linux specifically to follow these guides?
No. The gaming concepts apply to any Linux distribution. Package names and install commands differ between distributions, but Proton works the same way on Ubuntu as it does on Arch, and Wine configuration is identical everywhere. The guides use Arch Linux commands but note the differences for other distributions where relevant.
What is the difference between Proton, Bottles, and Wine?
Wine is the core compatibility layer that translates Windows API calls into Linux calls. Proton is Valve's gaming-focused fork of Wine with extra patches, bundled inside Steam. Bottles is a graphical interface that manages Wine environments for non-Steam games. Think of it this way: Wine is the engine, Proton is a tuned version of that engine built into Steam, and Bottles is a dashboard that makes the engine easier to operate for games outside Steam.
Does GPU brand matter for Linux gaming?
Yes, it matters a lot. AMD GPUs have significantly better Linux support than NVIDIA. The open-source Mesa drivers for AMD are actively developed, well-optimized for Vulkan, and work out of the box on any Linux distribution. NVIDIA requires proprietary drivers that have historically had friction with Wayland and kernel updates. If you are buying a GPU specifically for Linux gaming, AMD is the safer choice. If you already have NVIDIA, it works but expect more configuration.
How do I know if a specific game runs on Linux?
Check ProtonDB for Steam games. The community reports on ProtonDB include the exact Proton version, launch options, and any workarounds needed for each game. For multiplayer games with anti-cheat, check Are We Anti-Cheat Yet. These two resources together cover the vast majority of what you need to know before trying to run a specific title on Linux.
Can I use my existing Windows game saves on Linux?
If the game uses Steam Cloud saves, yes, they sync automatically. For local saves, you can usually copy them from the Windows prefix location to the Linux equivalent. The Wine guide covers where to find save files inside Wine prefixes. For Steam games specifically, Linux stores saves in a different location than Windows but Steam handles the sync so you generally do not need to do anything manually.
🎮 Ready to Start Gaming on Linux?
Start with the Steam and Proton guide if you have a Steam library. Add Bottles for Epic and GOG titles. Set up CoreCtrl and MangoHud for performance monitoring whenever you are ready. The guides are written to be followed in that order but each one also works independently if you have a specific need.
Linux gaming has come further in the last three years than in
the previous decade. It is not perfect, the anti-cheat situation
is still frustrating, and some games will never work. But for
most gaming libraries it is genuinely viable now, and for AMD
GPU owners on Vulkan-heavy titles it is sometimes better than
Windows. Give it a real try before deciding it is not for you.
101 out, I'll see you in the next one! 🚀