Identify

• the route that will be the base route. This route will form the backbone of the combined routes. This will usually be the larger route or the route that contains Session data that you want to keep in the merge.
• the route that will be the merged route. This route will be joined to the base route.
• the orientation (North-South or East-West) of the routes to be merged. Are they the same or different?
• the baseboards in both route where they will be joined. The join must be along the edges of both routes.
• the height of the baseboards in both routes at the merge point. Are the matching baseboards from both routes the same height or different?
• the names of the layers in both routes. Are there any layers in the merged route that have the same name as layers in the base route?
• the layers in both routes that contain the tracks and the track objects (signals, switches, speed signs, etc).

• The easiest and most common problems will be fixed as part of the merging process itself.

• The most common problem in the "hard to fix but do-able" category is when the two routes have been built at different heights or altitudes as shown on the left. The solutions to this will vary depending on the height difference. Common solutions are:-
  • add extra baseboards between the two routes that will create an easy gradient from the base route level to the merged route level. These additional baseboards are usually added to the base route before the merge is attempted. If the height difference is large then many additional baseboards may be needed. If the difference is too big then other options may have to be considered.
  • use a spiral tunnel or switchback/zigzag on a single extra baseboard to bring the track to the correct level. This will reduce number of extra baseboards.
  • add portals to both routes so that a consist entering the portal on one route will emerge from the portal on the other route. Portals can have their own issues and this solution may not suit everyone and every layout.

• Another problem can occur if a layer containing track from the merged route ends up below the base route layer that also contains track. This can be fixed by merging the lower track layer into the higher base route track layer either during the merging process or afterwards using the Layer Tools in Surveyor.

• The most common problem in the "impossible to fix" category is when both routes have different orientations (N-S and E-W) and you were hoping to join them end-to-end in the same direction to make an even longer route. Once a route has been created its orientation cannot be changed.

A handy trick is to create a new layout that just contains the extra "in-between" baseboards. The baseboards on one side will have heights that match those of the base route at the merge point and the baseboards on the other side will have heights that match those of the merged route at the merge point. The merge is performed in two stages:- Base route merged with the new bridging layout. Base route + bridging baseboards merged with the selected merged baseboard. This avoids having to alter the original base route and merged route.

Selecting and Loading the Routes to Merge

• Load the Base Route into Surveyor

Should you load the Route or the Session?

The answer depends on whether or not the Session contains assets (scenery, consists) and settings (rules, driver commands, industry and wagon loads, weather, time of day, etc) that you want to continue to use in the new merged Route and its Session. If the Session contains nothing that you need then load the Route only into Surveyor. Note that when you add the merged route its Route assets and data will be loaded but not its Session assets or data.

Select the Merge Route option in the Surveyor Main Menu This will open a Route Selection window. Select the route to be merged This will be the merged route and only its Route data will be loaded DLC routes cannot be selected for merging

This will merge the two routes and display a "minimap" of the new combined routes with some control options.

The Merge Map

The two tabs shown on the left are the:- Terrain Tab which is automatically selected when the MiniMap is first displayed. This shows the baseboards of the merged route superimposed on the baseboards of the base route. A red background colour on this tab, as shown in the figure on the left, indicates that the two routes have baseboards that are in conflict - they are overlapping. The overlapping baseboards are shown in red on the MiniMap. Layers Tab. This shows the layers that have been copied from both routes. A red background colour on this tab indicates that the two routes have layers that are in conflict. In Terrain View:- You can zoom the MiniMap in and out using the mouse control wheel. There appears to be no keyboard zoom control. You can move the centre of focus (the centre of the MiniMap view) by moving the mouse pointer to a new position and clicking with the right button. The four arrows shown at the top, bottom and both sides of the map display can be clicked to move the merged route in the direction shown by each arrow.

Move the Merged Route into its New Position

Click on the direction arrows shown at the top, bottom and sides of the MiniMap window to move the merged route into its correct position. Each click will move the merged route one baseboard in the selected direction. In the example shown on the left, clicking the Left arrow 5 times moved the merged route 5 baseboards to the left to a position where there were no overlapping baseboards and all terrain conflicts were resolved. A route merge will not proceed until ALL the terrain and layer conflicts have been eliminated.

The Layers Map

Click the Layers Tab to show the layers loaded from the two routes.

A route merge will not proceed until ALL the terrain and layer conflicts have been eliminated.

In the example shown on the left two of the layers, one from each route, are using the same name "route-layer". This causes a conflict that must be resolved before the merge can be completed. There are three simple options for solving this problem:- Rename one of the conflicting layers. Double click on the layer name to enter a new name. The conflict has now been resolved.

Delete one of the conflicting layers. Select the layer and click on the Delete icon.

CAUTION: Deleting a layer will delete all its contents. After clicking the Delete Icon ... ... the conflict has now been resolved.

Merge one of the conflicting layers. Select the layer and click on the Merge icon (next to the Delete Icon).

Then select the layer it will be merged into and click the Tick Icon. After merging ... ... the conflict has now been resolved.

Accept or Reject

Once all the conflicts have been resolved, the final step in the merging process can take place.

	ACCEPT: Click the Tick Icon to accept the merge. This icon will not be usable unless ALL conflicts have been resolved.
	REJECT: Click the Cross Icon to reject the merge. The merging will be cancelled, no routes will be lost or altered.

Trainz Wiki

• How to Guides
• Session Rules List (Alphabetical) with Parameters
• Session Rules List (Categories) With Parameters

Route Creation Tutorials:

Session Creation Tutorials: