Getting Into the Proton Bus Simulator Mod Scene
Running bus simulators through Proton on Linux works fine for the base games. OMSI 2, Bus Simulator 21, and similar titles launch and play without major issues. The real complexity shows up when you start digging into the modding ecosystem and the auto-scene that's grown around these games. Most people approach this expecting it to be straightforward, and it isn't, mostly because the Linux compatibility layer introduces a few quirks that Windows-only mod managers don't account for. The mod scene for bus simulators on Proton is surprisingly active. You've got community-created routes, livery packs, vehicle replacements, and traffic AI mods. The auto-scene specifically refers to AI traffic improvements — replacing default pedestrian and car spawns with more realistic behavior. These mods come from various sources: Steam Workshop (if the game supports it through Proton), GitHub repos, dedicated mod forums, and Discord communities. The best single source is usually the game's own subreddit or a dedicated Discord server where mod authors post updates. Installing mods through Proton requires knowing where your Windows prefix lives. Run protontricks on the game to access the virtual drive, then navigate to where the game installs its data. For OMSI 2, that's typically inside your Steam library under the OMSI_2 folder. Copy mod files into the appropriate subdirectories — usually Addons or Config. Don't place everything in the root; the game will ignore properly nested folders but will crash on malformed paths.
I hit a specific problem once when trying to run a large traffic AI overhaul mod alongside a route pack for OMSI 2. The game would load fine but AI vehicles would flicker in and out of existence every few seconds, and the frame rate dropped to something unplayable around 15 fps. The issue turned out to be that the Proton runtime was caching the previous physics state between sessions, and the two mods were conflicting on object spawning orders. My workaround was deleting the steamapps/common/OMSI 2/MAP/_cache folder entirely and forcing the game to regenerate it fresh, then launching with PROTON_USE_VULKAN=1 set as an environment variable before the game executable. That combo stabilized everything. It took about three minutes to clean the cache and the performance recovered to roughly 50-55 fps on a Radeon RX 6700 XT.
Mod Management Without a Native Manager
Most bus simulators don't have native Linux mod managers. People tend to use manual folder organization or Windows tools like WINE directly. There's a tool called ProtonUp-Qt that helps install Winetricks components, but it doesn't manage in-game mods. For actual mod handling, most people in the scene just maintain their own folder structure and use a simple text file as a manifest of what's installed and which versions they're running. I keep a JSON file in my game's root directory listing every mod, its source URL, and the install date. It sounds tedious until you need to troubleshoot a crash six months later and remember which three mods were active at the time. Another practical approach is creating symlinks from a central mod repository into the game's addon folders. This lets you enable or disable mods by toggling the symlink rather than manually copying files back and forth. On a system with limited storage, this also means you only maintain one copy of each mod regardless of how many different games might use it.
Get the Full Details
Common Pitfalls and What Actually Works
The biggest mistake beginners make is assuming mods designed for the native Windows version will work identically through Proton. They mostly do, but there are edge cases. Texture files in certain formats like EXR or older PXR variants may not decode correctly through the Wine layers, resulting in black or magenta textures in-game. The fix is usually to convert those textures to PNG or TGA beforehand using a tool like ImageMagick or GIMP. This adds maybe ten minutes to your workflow but prevents hours of troubleshooting why half your mod looks broken. Another counter-intuitive thing: newer isn't always better when it comes to Proton versions. The default Steam Deck Proton version (9.x series) works well for most bus simulators, but some older titles like OMSI 2 actually run more stably on Proton 7.0-6. The game was built on an older DirectX layer and the newer VKD3D-Proton translations occasionally introduce subtle rendering bugs. Test multiple Proton versions if a mod isn't behaving right. Checking protondb.com for community reports on your specific game will usually tell you which version others have found most stable. The auto-scene mods, particularly AI traffic overhauls, sometimes require specific Microsoft C++ redistributables to be installed via Winetricks. If AI vehicles aren't spawning at all, check whether d3dx9, vcrun2015, and dotnet48 are present in your prefix. Protontricks makes this check easy — just right-click the game and select "Install wine components," then search for those packages.
Limitations Worth Acknowledging
Not every mod works through Proton. Some mods rely on anti-cheat systems that actively block Wine prefixes. Others depend on Windows-specific registry entries that the game's launcher writes during initial setup, and those don't carry over reliably when running through compatibility layers. If a mod requires launching an external configurator tool, that tool almost certainly won't run under Proton unless it's been explicitly tested. In those cases, you're usually stuck running the game natively on Windows or using a separate Windows VM with GPU passthrough, which is a significant commitment for just one game. Performance overhead from Proton varies by game but typically adds somewhere between 5 and 15 percent compared to native Windows, depending on your hardware and whether the game uses DX12 or Vulkan. OMSI 2 sees minimal overhead because it's a lighter game. Bus Simulator 21 with heavy mod loads can see more noticeable impact, especially during dense city scenarios with lots of AI traffic. If you're running on integrated graphics or an older GPU, this overhead might be the difference between playable and unplayable framerates. The mod communities themselves can be fragmented. You'll find active discussion on Reddit, Discord, and dedicated forums, but there's no centralized index. Searching for "OMSI 2 Linux mods" or "bus simulator 21 proton mod" will surface relevant threads, but you'll often need to dig through several pages of results. Bookmarking the most useful subreddits and joining the main game Discords is genuinely the most efficient way to stay current on new releases and compatibility notes.
