Learn how to find, install and play Train Simulator Classic mission packs, including Workshop, .rwp and manual installs plus dependency fixes.
In Train Simulator Classic, “mission packs” are normally scenario packs. Find one written for a route and rolling stock you own, install it through Steam Workshop, an .rwp package or supplied folders, then select the matching scenario type under Drive. Missing dependencies are the main reason an installed mission does not appear or load.
A mission is not a separate game mode. It is an authored scenario containing instructions, timings, traffic and objectives for an existing route. A scenario pack may contain several Career, Standard or Free Roam scenarios, but it does not usually include the route, locomotives or other commercial assets they use.
How do I find compatible Train Simulator Classic missions?
Choose a mission pack only after confirming that you own its exact route and required rolling stock. Similar route names, extensions and remastered editions are not always interchangeable.
- Required route: Check the full route name and any extensions named by the author.
- Required trains: Look for every locomotive, coach, wagon and reskin dependency. A reskin still requires its original model.
- Asset packs: Older scenarios may depend on shared scenery or rolling-stock collections that are no longer bundled with every route.
- Scenario type: Note whether the missions are Career, Standard, Free Roam or Workshop scenarios; this determines where they appear in the Drive menu.
- Installation format: Identify whether the download uses Workshop,
.rwp, a manual ZIP archive or a dedicated installer.
Our checklist for choosing reliable free scenarios and add-ons explains how to assess downloads and their requirements before changing the simulator's files.
How do I install a Train Simulator Classic mission pack?
Use the installation method supplied by the author; converting or renaming a package rarely works. Close Train Simulator Classic before installing local files so that it does not retain an outdated scenario catalogue.
| Package type | Installation method | Best used when |
|---|---|---|
| Steam Workshop | Subscribe and allow Steam to download it | The scenario is published through Workshop |
| Steam DLC | Steam installs and updates it automatically | The missions are sold or supplied as official DLC |
.rwp | Install through Utilities.exe Package Manager | The author provides a RailWorks package |
| ZIP or folders | Merge the supplied Assets and Content folders manually | The download has no packaged installer |
Steam Workshop installation
- Read the requirements. Workshop installs the uploaded scenario, not every route or paid item named in its description.
- Subscribe using the correct Steam account. It must be the account that owns Train Simulator Classic and the required DLC.
- Wait for Steam's download to finish. Do not launch the simulator while an update or Workshop download is still pending.
- Restart the simulator. An open copy may not detect a newly downloaded scenario until its next launch.
Installing an .rwp package
- Locate the RailWorks installation folder. It is the folder containing
RailWorks.exe,Utilities.exe,AssetsandContent. - Run
Utilities.exe. Open Package Manager and choose its installation option. - Select the downloaded
.rwpfile. Allow the package manager to finish before closing it. - Start Train Simulator Classic. Check the scenario type and route named in the pack's instructions.
If Package Manager reports an error or the package does not appear, follow our detailed procedure for installing and troubleshooting .rwp files. Do not extract an .rwp as though it were an ordinary ZIP archive.
Manual ZIP or folder installation
- Extract the archive to a temporary folder. Read its included instructions before copying anything.
- Inspect the folder structure. A correctly prepared download normally contains
Content,Assetsor a wrappingRailWorksfolder. - Merge it with the real RailWorks folder. Copy
ContentandAssetsinto the folder containing the simulator executable. - Check for accidental nesting. The result must not be
RailWorks\RailWorks\ContentorContent\Content. - Avoid unnecessary overwrites. Back up any existing file that the instructions explicitly tell you to replace.
A scenario itself normally ends up below Content\Routes\<route GUID>\Scenarios\<scenario GUID>. Do not move it to a different route folder because the long identifier looks unfamiliar. If the pack also contains a complete route, use the fuller route and expansion-pack installation checks before launching it.
How do I play an installed mission pack?
Open Drive, choose the scenario category specified by the pack, select the required route and then choose the mission by name. A Standard scenario will not appear under Career, and authored missions do not normally belong in Quick Drive.
- Check the supplied documentation. Note the displayed mission names, scenario type, route and intended locomotive.
- Open the correct Drive category. Workshop content may first appear in a Workshop area or filter, depending on the menu revision.
- Select the route and mission. Scenario-pack names are not always shown; individual missions may have separate service names.
- Read the briefing and task list. Follow stopping points, coupling instructions, direction changes and scheduled times in the stated order.
For the controls used to locate scenarios and complete their objectives, see our practical guide to selecting and playing Train Simulator Classic scenarios.
Why is the installed mission missing or not loading?
A missing route, train or asset pack causes most mission-pack failures; reinstalling the scenario alone will not replace those dependencies. Match the symptom before changing files.
| Symptom | Likely cause | What to check |
|---|---|---|
| Mission is not listed | Wrong scenario category, missing route or incorrect folder nesting | Check Career, Standard and Workshop separately, then verify the route and installation path |
| “Can't load” or broken-consist message | Required locomotive, coach, wagon or reskin base is absent | Compare the message with the pack's complete rolling-stock list |
| Invisible trains or missing textures | Missing asset provider or an incorrectly installed Assets folder | Confirm every asset dependency and look for nested folders |
| Loading screen crash | Incomplete download, damaged dependency or incompatible legacy content | Reinstall the pack, verify owned base content and test another scenario on the same route |
| Mission loads but objectives do not advance | An instruction was missed or completed out of sequence | Review the task list, stopping marker, reverser position and coupling order |
If all files and dependencies are present, use Train Simulator Classic's Clear Cache command, usually found among its Settings or Tools options, and restart the simulator. A cache clear can refresh the scenario and asset catalogue, but it cannot install a missing route or train. Clearing it repeatedly before checking the requirements is a mistake we see constantly.