Learn why Train Sim Modeler cannot export directly to Train Simulator Classic and follow the correct rolling-stock creation workflow.
Train Sim Modeler is a legacy 3D modelling package built mainly for Microsoft Train Simulator, not Train Simulator Classic. It cannot export TSC-ready rolling stock directly. For TSC, create or import the mesh in a compatible 3D package, then use TSC’s asset pipeline to compile geometry, build blueprints and test it in-game.
Is Train Sim Modeler compatible with Train Simulator Classic?
Train Sim Modeler can be useful as a source-modelling or recovery tool, but its original simulator output is incompatible with Train Simulator Classic. The similarly named games use different geometry, texture, configuration and physics systems.
| Tool or format | Intended purpose | Use with TSC |
|---|---|---|
| Train Sim Modeler | Creating models for older train simulators, especially Microsoft Train Simulator | Use editable models only if they can be transferred into a compatible modern modelling package |
| MSTS shape and configuration files | Compiled rolling stock for Microsoft Train Simulator | Cannot be copied into TSC or referenced by a TSC blueprint |
| TSC asset pipeline | Compiling geometry, textures, animations and blueprints for the RailWorks engine | Required for native Train Simulator Classic rolling stock |
A 3D mesh is only one part of a TSC vehicle. Complete rolling stock also needs materials, textures, level-of-detail models, wheel and bogie pivots, coupling positions, collision data, physics and a compiled blueprint. A drivable locomotive additionally needs propulsion simulation, controls, cab assets and sounds.
How do you create rolling stock for Train Simulator Classic?
- Decide between a reskin and a new model. Use a reskin when an existing vehicle has the correct body, bogies and proportions. Build a new model when the silhouette, windows, running gear or cab differs. Our explanation of how TSC reskins depend on an installed base model shows why a texture replacement cannot change the underlying geometry.
- Create a provider and product source tree. Keep editable files beneath a path such as
RailWorks\Source\YourProvider\YourProduct\RailVehicles\. Exported game assets go beneath the matchingRailWorks\Assets\structure. Do not treat compiled files inAssetsas your master project: updates, cache operations or re-exports can replace them. - Build the model to real dimensions. Follow the axis and unit conventions required by the chosen TSC exporter. Put wheel pivots at axle centres, bogie pivots at their actual rotation points and the vehicle origin where the exporter expects it. Separate moving components from the body and add sensible lower-detail meshes for distance rendering.
- Prepare TSC-compatible materials. UV-map the model and assign shaders supported by Train Simulator Classic rather than leaving generic materials from the modelling application. Check smoothing, transparency and texture paths before export; unsupported materials are a common cause of invisible or incorrectly rendered parts.
- Export geometry and animations. The usual source pipeline passes geometry and animation data through TSC-compatible exporter formats before Blueprint Editor compiles them into game assets such as
.GeoPcDx. The exact exporter depends on the modelling package, but an MSTS.sshape is not a substitute. - Create the rolling-stock blueprints. Choose the appropriate wagon or engine blueprint and reference the exported geometry. Enter the vehicle dimensions, mass, collision geometry, bogies, wheel radii, couplings, braking data and other simulation properties. A locomotive then needs its engine simulation and associated cab, controls, lights and sound references. Our guide to compiling source assets with Blueprint Editor covers the source folders, references and export process in detail.
- Export and test one vehicle first. Enable the provider and product for the test route, place the vehicle in a simple scenario and inspect it from every angle. Check rail height, wheel rotation, bogie movement, curve clearance, coupling gaps, braking and level-of-detail transitions before building a full train.
- Build a consist and package the finished files. Once the individual vehicle behaves properly, follow our method for assembling and testing rolling stock in a consist. For distribution or backup, package the completed project as an RWP with Utilities, including every original asset while excluding third-party dependencies you cannot redistribute.
Can an old Train Sim Modeler project be converted?
An editable Train Sim Modeler project may provide a useful starting mesh, but conversion is normally a rebuild of the asset setup rather than a one-button export. Transfer the model through a format supported by both applications, then repair its scale, smoothing, UV mapping, part hierarchy, pivots and materials in the TSC-compatible modelling package.
Animations and configuration must be recreated for Train Simulator Classic. MSTS vehicle configuration does not translate into a TSC engine or wagon blueprint, and old material definitions do not become TSC shaders automatically.
Only convert work you created or have permission to modify and distribute. Possessing a compiled model from another simulator does not grant rights to extract, alter or release it.
Why does new rolling stock fail to appear or work?
| Symptom | Likely cause | What to check |
|---|---|---|
| Vehicle is absent from the scenario browser | The blueprint did not export, has the wrong category, or its provider and product are disabled | Review Blueprint Editor errors, blueprint type and the route’s provider settings |
| Vehicle places but is invisible | Incorrect geometry reference, failed geometry export or unsupported material | Confirm that the compiled geometry exists and that its blueprint path matches exactly |
| Textures are blank, black or missing | Texture compilation failed or the material points to the wrong source | Check texture names, source paths, shader assignment and exported texture files |
| Wheels orbit or bogies turn incorrectly | Bad pivots, hierarchy or wheel dimensions | Return to the source model; blueprint values cannot repair an incorrectly centred mesh |
| Couplings overlap or leave a large gap | Vehicle length, pivot or coupling positions are wrong | Measure from the model origin and test both ends with several existing vehicles |
| It works only on the developer’s PC | An undeclared texture, sound, cab or child-object dependency was omitted | Test the package in a clean provider folder and document every required add-on |
A mistake we see constantly is editing generated files until the vehicle appears to work, while leaving the source blueprint wrong. Correct the source project and export it again. That keeps future revisions reproducible and prevents the next compilation from erasing the fix.