How to Merge Routes
(→The Merging Process) |
|||
Line 13: | Line 13: | ||
*Identify | *Identify | ||
**which route will be the '''base route''' that 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. | **which route will be the '''base route''' that 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 ''' | + | **the route that will be the '''merged route''' that 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 orientation (North-South or East-West) of the routes to be merged. Are they the same or different? | ||
**exactly where the merge will occur in both routes. | **exactly where the merge will occur in both routes. | ||
− | **the height of the baseboards in the ''base route'' and the '' | + | **the height of the baseboards in the ''base route'' and the ''merged route'' at the merge point. Are they '''exactly the same height?''' |
==Common Problems== | ==Common Problems== | ||
Line 24: | Line 24: | ||
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td>[[file:MergeHeightProblem.JPG]]<br>''This is "fixable"''</td> |
<td>The most common problem in the "hard to fix" category is when the two routes have been built at different heights or altitudes. The solutions to this will vary depending on the height difference. Common solutions:- | <td>The most common problem in the "hard to fix" category is when the two routes have been built at different heights or altitudes. The solutions to this will vary depending on the height difference. Common solutions:- | ||
− | *add extra baseboards to the ''base route'' that will create a gradual gradient from the ''base route'' level to the '' | + | *add extra baseboards to the ''base route'' that will create a gradual gradient from the ''base route'' level to the ''merged route'' level |
*use a spiral tunnel on a single extra merging baseboard to bring the track to the correct level | *use a spiral tunnel on a single extra merging baseboard to bring the track to the correct level | ||
*add portals to both routes so that a consist entering the portal on one route will emerge from the portal on the other route</td> | *add portals to both routes so that a consist entering the portal on one route will emerge from the portal on the other route</td> | ||
Line 34: | Line 34: | ||
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. | 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. | ||
− | =''' | + | ='''Selecting and Loading the Routes to Merge'''= |
*'''Load the ''Base Route'' into Surveyor''' | *'''Load the ''Base Route'' into Surveyor''' | ||
::Should you load the '''Route''' or the '''Session'''?<br><br> | ::Should you load the '''Route''' or the '''Session'''?<br><br> | ||
− | ::The answer depends on whether or not a Session has been created for the ''base route'' and if that 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 Session. If the Session contains nothing that you need then load the Route only into Surveyor. Note that when you add the ''' | + | ::The answer depends on whether or not a Session has been created for the ''base route'' and if that 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 Session. If the Session contains nothing that you need then load the Route only into Surveyor. Note that when you add the '''merged route''' only the Route assets and data will be loaded, no Session assets or data will be loaded. |
<table width="700"> | <table width="700"> | ||
Line 48: | Line 48: | ||
*'''Select the route to be merged'''<br> | *'''Select the route to be merged'''<br> | ||
[[file:MergeSelectRoute.JPG]]<br> | [[file:MergeSelectRoute.JPG]]<br> | ||
− | ::This will be the ''' | + | ::This will be the '''merged route''' and only its Route data will be loaded |
<table cellpadding="4" bgcolor=#c1e7e7> | <table cellpadding="4" bgcolor=#c1e7e7> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 59: | Line 59: | ||
</table> | </table> | ||
This will merge the two routes and display a "minimap" of the new combined routes with some control options. | This will merge the two routes and display a "minimap" of the new combined routes with some control options. | ||
+ | |||
+ | ='''The Merge Map'''= | ||
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:MergeMiniMapComplexTerrain01.JPG]]</td> | <td>[[file:MergeMiniMapComplexTerrain01.JPG]]</td> | ||
− | <td>The MiniMap has similar controls to | + | <td>The '''Merge MiniMap''' has similar controls to the MiniMaps in the Driver and Surveyor. |
*The two tabs shown on the left are the:- | *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 '' | + | **'''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. | **'''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. | ||
Line 83: | Line 85: | ||
The merge will not proceed until '''ALL''' the conflicts have been eliminated. | The merge will not proceed until '''ALL''' the conflicts have been eliminated. | ||
+ | *'''Move the ''merged route'' into its new position''' | ||
*'''Move the ''merged route'' into its new position''' | *'''Move the ''merged route'' into its new position''' |
Revision as of 21:58, 4 July 2018
Contents |
Merging Routes
The Merge Routes option in the Surveyor Main Menu allows two different routes to be joined together. |
Before You Start Merging
Before you start the merge there are some important points you will need to consider and there may be some preparation work that will have to be performed.
- Identify
- which route will be the base route that 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 that 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?
- exactly where the merge will occur in both routes.
- the height of the baseboards in the base route and the merged route at the merge point. Are they exactly the same height?
Common Problems
Most route mergers will have problems. Some problems will be identified and fixed during the merging process. Others may require you to do a bit (or a lot) of extra work before you can merge two routes into one. For some problems the best solution is to select different routes to merge.
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.
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 a Session has been created for the base route and if that 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 Session. If the Session contains nothing that you need then load the Route only into Surveyor. Note that when you add the merged route only the Route assets and data will be loaded, no Session assets or data will be loaded.
- Should you load the Route or the Session?
This will merge the two routes and display a "minimap" of the new combined routes with some control options.
The Merge Map
The Merge MiniMap has similar controls to the MiniMaps in the Driver and Surveyor.
In Terrain View:-
In the example shown on the left, the terrain conflict can be removed by moving the merged route to the left (clicking the left arrow) until the last red baseboard disappears. |
The merge will not proceed until ALL the conflicts have been eliminated.
- Move the merged route into its new position
- Move the merged route into its new position