Skip to content
Connected RailsConnected Rails

Placing scenery

Scenery is everything beside the track that the simulation does not read: masts, platforms, buildings, cars, trees, fields, roads, pylons and wind turbines. It is static line content, built the same way on every machine from the line file, so nothing about it has to cross the network in a multiplayer run.

There are two kinds of work. A mod author supplies models as scenery objects (objects/*.ron). A line builder places those objects, and everything the program draws itself (parametric buildings, fields, roads, the wires of power lines), in the route editor. This guide covers both. The complete field lists are in the reference pages it links to.

A scenery object is one RON file under objects/ and a glTF model under assets/. It is addressed as "<mod>:<file stem>", so mods/yourmod/objects/mast.ron becomes yourmod:mast.

  1. Put the model below your mod, for example mods/yourmod/assets/mast.gltf. The model conventions are in the next section.

  2. Write mods/yourmod/objects/mast.ron. Only name and model are required. The model path is relative to mods/, the same as for vehicle and signal models. This is the catenary mast from mast.ron in the example mod:

    (
    name: "Mast",
    model: "example/assets/sig_mast.gltf",
    lateral_offset: -3.5,
    yaw_deg: 0.0,
    height: 0.0,
    tags: ["mast", "catenary", "epoch-4"],
    )
  3. Give it the pose relative to the track. These are defaults that the route editor copies into every placement, and each placement can change them:

    • lateral_offset: metres from the track axis, positive is right of increasing arc length.
    • yaw_deg: degrees about the up axis, clockwise from above. 0 means the model’s front points along the track.
    • height: metres above the railhead.

    An object with a non-zero lateral_offset counts as trackside, and the object tool aligns it to the nearest track. An object without one (a car, a pylon, a landmark) is dropped free where the click is. A trackside object whose offset really is zero, such as a board on the axis of a siding, says so with the tag trackside.

  4. Tag it so the library’s search finds it. Tags are lower case, with words joined by hyphens. epoch-<n> and operator-<name> become the library’s Epoch and Operator filters. Some tags also drive automatic placement: the imagery detection places objects tagged car, and the forest brush plants from stand-… tags. See Tags.

  5. Optional extras for when they matter:

    • autumn_model / winter_model: seasonal variants, each a glTF with its own textures. Whatever is missing falls back to model, and the scenario’s start date picks one. The trees use them:

      autumn_model: Some("trees/assets/adlerfarn_a_herbst.gltf"),
      winter_model: Some("trees/assets/adlerfarn_a_winter.gltf"),
    • footprint: how much ground the object covers, as length along the model’s front-to-back axis and width across it. It makes no difference for hand placement. The imagery detection uses it to pick a model that fits what it measured, for example footprint: Some((length: 4.61, width: 2.18)) on a car (width measured over the mirrors), and for a plant it is the crown.

    • lod_distances: your own level-of-detail bands in metres, finest first. The last entry is the cull distance. Vegetation needs this most.

    See Track objects for all of them.

A scenery model is a glTF with the frame every model in the game uses:

  • Metres, +Y up, front towards −Z. With yaw_deg: 0.0 the −Z axis points along increasing arc length, so +X is the right-hand side of the track.
  • Origin is the point the placement puts at the lateral offset and height. For a trackside object, put it where the model meets the track. The platform has its origin at the track-side edge where the platform starts, on the railhead. Its body runs from z = 0 to z = −210 and extends away from the track along −X, so lateral_offset: -1.65 places it on the left of the line. A building that stands free has its pivot at ground level: the Wolfsburg landmarks are placed with terrain snapping on.
  • Levels of detail are nodes named <name>_LOD0, _LOD1, … and are switched by camera distance. A model without the suffix has one level. Keep each level to one material where you can, because the renderer spawns one entity for each mesh part on each level.
  • Lit windows: a node whose name ends in _NIGHT is shown after dusk and hidden by day. Model a second, emissive pane and call it, say, fenster_NIGHT. Nothing is declared in the RON file.

A platform, a footbridge or a forecourt can bring the paths its people walk on as empty glTF nodes (empties in Blender):

Nodes Meaning
wp_<name>_0, wp_<name>_1, … the vertices of a footpath, in walking order
wa_<name>_0, wa_<name>_1, … the corners of a walk area, in ring order

Custom properties on the _0 node (exported as glTF extras) set the crowd: people, width (a path’s width in metres) and walking_share (for an area, 0 … 1). The nodes sit in the model’s own frame, so the people stand at the nodes’ height (on the platform, not on the ground under it) and move with the object wherever a line puts it. tools/gen_platform.py is the worked example: it writes wp_edge_0 … wp_edge_6 with {"people": 6, "width": 1.0} and wa_middle_0 … wa_middle_3 with {"people": 10, "walking_share": 0.4}. Details and defaults are under Track objects and in People.

  1. Open your line in the route editor (cargo run -p route-editor -- path/to/line.ron).
  2. Open the Library (the content drawer): Ctrl+Space, the Library button in the status bar, or View ▸ Library.
  3. Pick the Scenery objects category. Its count says whether the editor found your mod. Search for the name, the mod or a tag. Hovering a card shows its key (yourmod:mast) and tags.

If the object is missing, check that the mod is enabled in its mod.ron and that the file parses (a broken file is a loading warning, not a crash). To keep building blocks or generated variants out of the list without stopping them from loading, use library: (hide: [...]) in mod.ron. library: (tags: {...}) adds tags to a whole family of files by path. See The library.

  1. Click the card to arm the Place object tool with it, or drag the card onto the map to drop it right there. A drag leaves the library open for the next object.
  2. With the tool armed, a translucent ghost follows the cursor. Ctrl + wheel turns it (15° a notch, 5° with Shift).
  3. Align to track (a tool option) measures the object from the nearest track and turns its front along it. It is on by default for trackside objects and off for everything else. With it off, the object stands where you click with its front to the north. Turn on Snap to terrain to stand an aligned object on the ground instead of the rail plane.
  4. Click to place. The Selection page then edits position, lateral offset, rotation and height. The gizmo moves a placement too: W for arrows along, across and up the track, E for the rotation ring.
  5. For a row, such as catenary masts, select one placement and use Repeat. It stamps copies along the track at a spacing (65 m by default) up to an end position, and each copy can still be edited on its own.

The line stores each placement under objects: with concrete values, either relative to the track or free on the earth:

objects: [
(object: "example:mast", edge: 0, s: 500.0, lateral_offset: -3.5),
(object: "cars:kleinwagen", geo: Some((lat: 52.4234, lon: 10.7865)), yaw_deg: 120.0),
],

The rule check flags a placement outside its track and one that names an object no installed mod has.

For ordinary houses you do not need a model. The Parametric building tool (Lineside equipment group) places an editable recipe instead of a glTF, stored under buildings: on the line.

  1. Pick the tool and choose a Preset (detached house, villa, apartment block, factory hall, multi-storey car park and more).
  2. Click to place it.
  3. Adjust dimensions, floors, facade, roof, windows, balconies and the other parts in the properties panel. Every field stays editable, and Ctrl+C / Ctrl+V copies the complete recipe, including its seed.

Use static objects: for a specific landmark, as the wolfsburg mod does. The recipe fields are listed under Parametric buildings.

A tree is an ordinary scenery object, and a tree mod is nothing more than objects/*.ron files with tree models. The line stores every tree as its own geo-positioned entry under trees:. The bundled trees mod ships the vegetation of Central Europe in three variants each, with four levels of detail and seasonal models, plus repeatable hedge sections.

  • Place tree (Landscape group) plants one tree per click.
  • Forest brush outlines an area. Enter or right-click fills it with single trees, which stay editable one by one.
  • File ▸ Import forest… bakes woods from an Overpass extract in the same way.
  • Marking brush sweeps over trees, objects and parametric buildings, and Delete removes everything it marked in one undo step.

Pick a stand instead of a single species to get a mixed wood. A stand is any stand-… tag on the installed tree objects. To add your own species to an existing wood, give it the tag the other species already carry:

tags: ["laubbaum", "stand-laubwald", "stand-mischwald", "stand-allee"],

See Vegetation and Stands.

Fields belong to the program, not to a mod. A line stores the outline and the crop group, and the date decides what the field looks like.

  • File ▸ Import fields… fetches the parcels inside the module envelope from the state agricultural registers. Nothing is written until Add to the module, and the whole import is one undo step.
  • The Field tool (Landscape group) draws one by hand. Clicks set the corners, Enter or right-click closes the field, and the crop comes from the tool options.

See Fields.

Roads are drawn by the program as well, draped on the terrain.

  • File ▸ Import roads… fetches the highway=* ways inside the envelope from OpenStreetMap. Field tracks and access ways are opt-in checkboxes.
  • The Road tool (Landscape group) lays a centre line by clicks. Enter or right-click finishes it, and the preset (Bundesstraße, Feldweg, …) decides the width, surface and markings.

See Roads.

A power line is one power_lines: entry: the masts are mod objects from mods/pylons, and the program hangs the conductors between them.

  • File ▸ Import overhead lines… fetches power=line and power=minor_line ways from OpenStreetMap and picks a mast type from their tags.
  • The select tool picks a line by any of its pylons. Its panel edits the name, the two mast objects, the mast height and the sag. Delete removes the line with its masts and wires.
  • To place a single mast by hand, use the object tool. The pylons are ordinary scenery objects.

See Overhead lines.

Wind turbines are wind_turbines: entries that use the models of mods/wind. The program yaws the nacelle into the wind and turns the rotor.

  • File ▸ Import wind turbines… takes the positions from OpenStreetMap and the dimensions from the Marktstammdatenregister.
  • A model of your own drives its moving parts through the node names nacelle, rotor and blink.

See Wind turbines.

Place many objects from the aerial imagery

Section titled “Place many objects from the aerial imagery”

File ▸ Detect from imagery… runs a local model over the aerial imagery, either along a corridor beside the track or inside an area drawn with the AI area tool (Imagery group). It places cars as objects and trees as tree entries. It places objects by tag: a model class names a tag such as car, and an installed object with that tag is dropped where the model found one. A crown becomes a tree from the stands or species the tree mods tag. A footprint on your objects lets the detection choose the one that fits. Nothing is written until Commit, and the whole run is one undo step. See Detecting from the aerial imagery.

A finished model should carry baked light before you ship it:

  • Sky occlusion for everything in the open. Soffits, canopies and recesses are otherwise lit as if they stood in a field.

    Terminal window
    blender --background --python tools/lightmap/bake.py -- mods/yourmod/assets/hall.gltf
    python3 tools/lightmap/bake_all.py mods/yourmod

    The model needs a free second UV channel. A regenerated model loses its bake, and bake_all.py --check finds such models.

  • Interior light for sealed rooms lit by their own lamps. Mark the interior materials, add KHR_lights_punctual lamps in candela and an interior_volume box. tools/gen_station_hall.py (example:station_hall) is the example, and --bake bakes it.

See Baked sky occlusion and Baked interior light.