What is Abacus Train Sim Modeler, and how do I create Train Simulator Classic rolling stock?
What Abacus Train Sim Modeler does, why its MSTS output will not work in TSC, and how to build native Train Simulator Classic rolling stock.
Abacus Train Sim Modeler is a legacy 3D modelling tool designed chiefly for Microsoft Train Simulator, not Dovetail Games' Train Simulator Classic (TSC). It cannot produce native TSC rolling stock directly; build or transfer the mesh into a compatible modelling workflow, then compile geometry, textures, blueprints and physics through TSC's developer tools.
What exactly is Abacus Train Sim Modeler?
Train Sim Modeler was Abacus' dedicated model-building package for creating locomotives, wagons and scenery for older train simulators, particularly Microsoft Train Simulator (MSTS). It combined basic modelling, texturing, part hierarchy and simulator-specific export functions in one application.
That made it useful in the MSTS era, but Train Simulator Classic is not a renamed version of MSTS. TSC belongs to the later RailWorks-based simulator family and uses a different asset pipeline.
A model is also only one part of a working vehicle. TSC stock needs compatible materials and textures, correctly placed wheels and bogies, coupling positions, collision and vehicle dimensions, physics data and compiled blueprints. A drivable locomotive usually adds propulsion simulation, controls, cab assets, sounds, lights and sometimes scripts.
Is Train Sim Modeler compatible with Train Simulator Classic?
No: Train Sim Modeler cannot directly export a complete, native vehicle for Train Simulator Classic.
| Tool or format | Original purpose | Use in TSC |
|---|---|---|
| Abacus Train Sim Modeler | Building assets for MSTS-era simulators | An editable project may supply a starting mesh, but it still requires transfer and rebuilding |
| MSTS shape and vehicle files | Compiled geometry and configuration for Microsoft Train Simulator | Cannot be copied into TSC, referenced by a TSC blueprint or made compatible by renaming files |
| TSC source and blueprint pipeline | Compiling RailWorks-family geometry, textures, animation and simulation data | Required for native Train Simulator Classic rolling stock |
The similar names cause another search mix-up: iTrain is model-railway control software, not Abacus Train Sim Modeler and not an asset exporter for TSC.
Should I reskin, convert or build a new TSC model?
Choose the least complicated option that can reproduce the real vehicle's geometry and that you have permission to use.
| Approach | Choose it when | Main limitation |
|---|---|---|
| Reskin an existing TSC vehicle | The donor already has the correct body, windows, bogies and proportions | A texture change cannot correct the silhouette, running gear or cab geometry, and users still need the donor asset |
| Transfer an editable Train Sim Modeler project | You own the source or have permission, and its mesh can be moved into a compatible modelling package | Materials, pivots, hierarchy, animation and simulator configuration normally need rebuilding |
| Create new geometry | No suitable donor exists or the vehicle differs visibly in shape and running gear | Requires the most modelling, research and testing work |
Our explanation of how TSC reskins use and depend on donor vehicles helps establish whether repainting is enough. For a first original project, an unpowered wagon is considerably more manageable than a locomotive with a working cab and traction simulation.
How do I create rolling stock for Train Simulator Classic?
Native TSC stock is created through a modelling application, a compatible TSC exporter, the simulator's source folders and Blueprint Editor.
- Set up the supported tools. TSC's development utilities compile and test assets; they do not replace the 3D modelling application. Confirm that your chosen modeller has an exporter suitable for its version and for TSC. An ordinary FBX or OBJ file is useful for transferring a mesh between modelling programs, but TSC does not load it directly as rolling stock. Our overview of the tools required for a TSC stock project explains how the modeller, exporter, Blueprint Editor and game fit together.
- Create your provider and product structure. Keep editable source work under a path such as
RailWorks\Source\<Provider>\<Product>\RailVehicles\. Compiled game assets are generated beneath the correspondingRailWorks\Assets\<Provider>\<Product>\tree. Choose unique provider and product names and retain the Source folder as the master project. - Model at real scale. Follow the unit and axis conventions required by the selected exporter. Place axle pivots at wheel centres, bogie pivots on their real rotation points and the vehicle origin where the export workflow expects it. Separate components that must rotate or animate, and provide sensible lower-detail geometry for distance rendering.
- Build TSC-compatible materials. UV-map the mesh, prepare source textures and assign shaders understood by Train Simulator Classic. Generic materials from the modelling program do not automatically become valid TSC materials. Check normals, smoothing, transparency and texture references before export; mistakes here commonly produce invisible, black or incorrectly lit parts.
- Export geometry and animation. In the conventional TSC pipeline, the exporter produces source geometry and animation data, commonly using formats such as
.IGSand.IA. Blueprint Editor then compiles these into game assets such as.GeoPcDx. An MSTS.sshape cannot replace this stage. - Create the correct blueprint. Start with a wagon blueprint for unpowered stock or the relevant engine blueprint for a locomotive. Reference the exported geometry and configure dimensions, mass, wheels, bogies, couplings, braking and other simulation properties. Engines also require suitable traction or power simulation and references for their cab, controls, sounds and lights. Our Blueprint Editor workflow for compiling rolling stock covers provider paths, blueprint selection, export and testing in more detail.
- Test one vehicle before making variants. Enable its provider and product in the test route's object filter, place it in a simple scenario and inspect it on straight and curved track. Check rail height, wheel rotation, bogie movement, clearances, coupling gaps, braking, lights and level-of-detail changes. Fix faults in the source model or blueprint and export again.
- Build a consist and test dependencies. Once one vehicle behaves correctly, use the scenario tools to test several copies, mixed formations and both vehicle orientations. Our guide to assembling and testing TSC consists covers the next stage.
- Package only files you may distribute. Include the compiled assets created for the project and document any donor vehicles, cabs, sounds or other dependencies. Do not bundle third-party assets merely because they are present in your installation. Keep the editable Source project separately so later corrections remain reproducible.
Can an old Train Sim Modeler project be converted?
Sometimes, but conversion is a reconstruction of the simulator-specific setup rather than a one-button export.
Move the editable mesh through an interchange format supported by both the old and replacement modelling applications. Then inspect scale, triangulation, normals, smoothing, UV mapping, hierarchy and every pivot. Old material definitions must be replaced with TSC-compatible shaders, while MSTS animations and vehicle configuration must be recreated through TSC geometry, animation and blueprint data.
A compiled MSTS model is not equivalent to an editable source project. Extraction may lose hierarchy or material information, and having the compiled files does not grant permission to modify or release somebody else's work. Convert only assets you created or have explicit rights to use.
Why does new TSC rolling stock fail to appear or work?
Most failures come from an unsuccessful export, a broken asset reference or model origins and pivots that do not match the blueprint.
| Symptom | Likely cause | What to check |
|---|---|---|
| Vehicle is absent from the stock list | The blueprint failed to compile, uses the wrong stock type, or its provider and product are disabled | Read the Blueprint Editor output, confirm the blueprint type and enable the product in the route's object filter |
| Vehicle can be placed but is invisible | The geometry reference is wrong, compilation failed or no valid material is rendering | Confirm that the compiled geometry exists and that the blueprint references the exact provider, product and asset path |
| Textures are blank, black or missing | A source texture failed to compile or the material points to the wrong asset | Check texture names, source paths, shader assignment, transparency settings and compiled texture files |
| The body sits above or below the rails | The model origin, wheel radius or blueprint dimensions are incorrect | Measure the source model rather than trying to correct a large modelling error with arbitrary blueprint values |
| Wheels orbit the axle or bogies swing incorrectly | Bad pivots, hierarchy or animation setup | Correct the source model; the blueprint cannot repair an off-centre mesh pivot |
| Couplings overlap or leave an excessive gap | Vehicle length, origin or front and rear coupling positions are wrong | Measure from the model origin and test both ends against several compatible vehicles |
| The package works only on its creator's PC | A texture, cab, sound, script or child-object dependency was omitted | Audit every referenced provider and product, then test the package on a clean installation if one is available |
A mistake we see repeatedly is editing generated files under Assets until the vehicle appears to work while leaving the source blueprint wrong. Correct the Source project and export it again. Clear TSC's blueprint cache only after fixing the underlying paths or files; clearing the cache cannot repair an invalid blueprint.