Learn how to run Train Simulator Classic on Linux with Steam Proton, choose the right executable, install DLC and fix common launch problems.
Yes, Train Simulator Classic can run on Linux through Steam’s Proton compatibility layer, but there is no native Linux version and Dovetail Games does not officially support this setup. Core routes often work, while individual DLC, older add-ons, video playback and specialist controllers can still cause problems.
How do you install Train Simulator Classic on Linux?
The simplest method is to install the Linux Steam client and make Steam run Train Simulator Classic through Proton.
- Check your graphics drivers. Proton translates the simulator’s Windows graphics calls to Vulkan, so install the appropriate Vulkan driver components for your graphics card. Some distributions also require 32-bit driver libraries for Steam and older software.
- Enable Steam Play. Open Steam’s compatibility settings and enable Steam Play for other titles if Train Simulator Classic cannot be installed normally. The wording can vary between Steam client versions.
- Force a Proton version. Open the simulator’s Properties page, select Compatibility and force the latest stable Proton release offered by Steam. Start with stable Proton rather than changing several settings at once.
- Install the game through Steam. The library and verification process follows the normal Steam method described in our Steam installation and file-verification walkthrough, although Linux and Proton use different folder paths.
- Choose the 64-bit edition. If Steam presents a choice, use Train Simulator Classic 64-bit for normal play. Try the 32-bit executable only when an older add-on specifically fails under 64-bit.
- Test a bundled route first. Run a simple Quick Drive or included scenario before installing Workshop items and manual add-ons. This separates a Proton problem from missing route assets or third-party content.
The first launch may take longer while Proton creates its Windows-style prefix and processes shaders. Do not interrupt it merely because the initial loading screen pauses for a while.
Will Train Simulator Classic DLC and mods work on Linux?
Steam DLC usually installs through Proton without extra work, but third-party content is less predictable because old installers, dependency chains and Windows-oriented utilities may not behave correctly.
| Content | What to expect on Linux |
|---|---|
| Steam routes and locomotives | Normally download with the base game, though each route can expose different graphics or scripting issues. |
| Steam Workshop scenarios | Subscriptions generally download normally. Missing commercial DLC remains the most common reason a scenario fails; our Workshop subscription and dependency guidance explains how to check it. |
| Manual add-ons | Files can be installed into the RailWorks directory, but Windows installers and package utilities must operate inside the game’s Proton environment. |
| Older rolling stock | May depend on legacy components, fonts, scripts or installers that need extra attention. |
| Specialist controllers | Keyboard and ordinary gamepad input are generally easier. RailDriver and other USB hardware should not be assumed to work without additional Linux configuration. |
A mistake we see constantly is running an add-on installer in a separate Wine environment. The installer then writes assets somewhere Train Simulator Classic cannot see. Where manual extraction is supported, preserve the original folder names and capitalisation under RailWorks/Assets and RailWorks/Content; see our advice on add-on dependencies and installation locations before adding a large collection.
The Proton prefix is normally associated with Steam application ID 24010, under a path ending in steamapps/compatdata/24010/pfx. Its exact location changes with custom Steam libraries and sandboxed Steam installations, so use Steam’s local-files browser to locate RailWorks rather than assuming one fixed Linux path.
Why will Train Simulator Classic not launch through Proton?
Most Linux launch failures come from an unsuitable Proton build, incomplete Vulkan support, damaged game files or an add-on loaded before the clean simulator has been tested.
- Return to stable Proton: remove custom launch commands and select Steam’s latest stable Proton release. If that fails, test Proton Experimental as a separate comparison.
- Verify the game files: use Steam’s file-verification tool before deleting anything. This repairs missing core files without removing every route.
- Test without manual add-ons: temporarily move recently installed assets out of
RailWorks, especially if the simulator worked before they were added. - Check Vulkan support: a working Linux desktop driver does not necessarily mean that all Vulkan and 32-bit components required by Steam are installed.
- Reset the Proton prefix only as a last resort: back up settings and user-created content first, then allow Steam to create a fresh prefix. Deleting it can remove Windows-side preferences and locally stored files.
For crashes that also occur on Windows, such as failures caused by corrupt scenarios, memory pressure or conflicting assets, work through our Train Simulator Classic crash checks rather than repeatedly changing Proton versions.
Should you use Proton, a virtual machine or dual boot?
Proton is the best starting point for ordinary Linux play, while dual booting Windows remains the safer choice for maximum add-on and specialist-hardware compatibility.
- Choose Proton if you mainly use Steam routes, accept occasional troubleshooting and want to stay within Linux.
- Choose dual boot if you rely on a large library of old installers, route-building utilities, RailDriver or add-ons whose publishers support only Windows.
- Avoid a basic virtual machine for normal play. Train Simulator Classic needs effective 3D acceleration, and a typical virtual GPU adds more compatibility and performance problems than Proton. A properly configured GPU-passthrough system is possible but far more involved.
SteamOS devices use the same broad Proton approach, but their controller mapping, power limits and storage layout introduce separate considerations. On any Linux system, keep a known-working Proton version assigned to the game once your routes are stable; an unnecessary compatibility-layer change can break a setup that was already functioning.