How to Merge Routes
(→Merging Routes) |
m (→Latitude and Longitude) |
||
(23 intermediate revisions by one user not shown) | |||
Line 2: | Line 2: | ||
__TOC__ | __TOC__ | ||
− | |||
<table cellpadding="4" bgcolor=#c1e7e7> | <table cellpadding="4" bgcolor=#c1e7e7> | ||
Line 18: | Line 17: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
− | <td>'''Physical difference between the routes will cause | + | <td>'''Physical difference between the routes will cause problems in the merging process.''' Most of these problems can be overcome</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
<br> | <br> | ||
Line 48: | Line 45: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
+ | ==Latitude, Longitude and Altitude== | ||
+ | <table cellpadding="4" bgcolor=#c1e7e7> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>A common misconception is that the '''Latitude''' and '''Longitude''' of the routes being merged plays a part in the merging process</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | The '''Latitude''' and '''Longitude''' of a route has absolutely no effect on the route itself apart from setting the season of the year along with the date entered into the '''Environment Tools'''. Even then it is only the '''North/South''' component of the entered '''Latitude''' that is important.<br> | ||
+ | |||
+ | A route with its geographic coordinates set in Northern Alaska will happily merge with a route set in outback Australia - but what you do with all the snow and the dust is another problem ;-) | ||
+ | |||
+ | '''Altitude''' differences between the two selected routes, however, can cause issues. See '''Common Problems (and Their Solutions)''' below. | ||
==Route File Sizes== | ==Route File Sizes== | ||
Line 60: | Line 71: | ||
The merging process occurs within your computers on-board memory (RAM). If this is not large enough then your system will also use virtual RAM, i.e. your disk storage space as temporary memory, which is significantly slower. If your system does not have enough memory, both on-board and virtual, then merging large routes will become a problem (i.e. impossible or will take a very long time). | The merging process occurs within your computers on-board memory (RAM). If this is not large enough then your system will also use virtual RAM, i.e. your disk storage space as temporary memory, which is significantly slower. If your system does not have enough memory, both on-board and virtual, then merging large routes will become a problem (i.e. impossible or will take a very long time). | ||
− | The Trainz forums contain several threads where attempts to merge very large routes (hundreds of Megabytes in size) have taken '''days''' to complete or failed to complete at all. In many of these cases the users did not have enough RAM (on-board and virtual) installed in their system. In one documented case, doubling the available on-board RAM from 16GB to 32GB and increasing the Windows virtual memory page size (disk based or virtual RAM) reduced the merge time for two extremely large routes from failing to complete in over 50 hours to successfully completing in 10 hours. | + | The Trainz forums contain several threads where attempts to merge '''very large routes''' (hundreds of Megabytes in size) have taken '''days''' to complete or failed to complete at all. In many of these cases the users did not have enough RAM (on-board and virtual) installed in their system. In one documented case, doubling the available on-board RAM from 16GB to 32GB and increasing the Windows virtual memory page size (disk based or virtual RAM) reduced the merge time for two extremely large routes from failing to complete in over 50 hours to successfully completing in 10 hours. |
− | + | <table cellpadding="4" bgcolor=#c1e7e7> | |
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''In most cases there should be no technical problems in merging routes (and completing the task in minutes) on systems that meet the recommended specs for TANE and TRS19'''</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
==Common Problems (and Their Solutions)== | ==Common Problems (and Their Solutions)== | ||
Line 72: | Line 89: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | Some problems will require you to do a bit (or a lot) of extra work before you can merge two routes into one. But for some problems, the best solution may be to select other routes to merge. | + | Some problems will require you to do a bit (or a lot) of extra work before you can merge two routes into one. <span style="background-color: yellow;"> But for some problems, the best solution may be to select other routes to merge. </span> |
[[file:MergeHeightProblem.JPG|470px|left]] | [[file:MergeHeightProblem.JPG|470px|left]] | ||
Line 82: | Line 99: | ||
*Sometimes textures from the ''base route'' will bleed into the ''to-be-merged route'' particularly if the latter route is not textured. The solution to this can be found in the Trainz Wiki [[file:WikiLink.PNG|link=]] '''[[How to Use Bulk Asset Update/Replace Tool]]'''. | *Sometimes textures from the ''base route'' will bleed into the ''to-be-merged route'' particularly if the latter route is not textured. The solution to this can be found in the Trainz Wiki [[file:WikiLink.PNG|link=]] '''[[How to Use Bulk Asset Update/Replace Tool]]'''. | ||
*The most common problem in the "hard to fix but do-able" category is merging two routes that have been built at different heights or altitudes. This will create a vertical cliff along the merge line, as shown on the left. The solutions to this will vary depending on the height difference. Common solutions are:- | *The most common problem in the "hard to fix but do-able" category is merging two routes that have been built at different heights or altitudes. This will create a vertical cliff along the merge line, as shown on the left. The solutions to this will vary depending on the height difference. Common solutions are:- | ||
− | ** | + | **<span style="background-color: yellow; font-weight: 700;">add extra baseboards</span> between the two routes to create an easy gradient between them. See the "'''Tips'''" box below. If the height difference is large then many additional baseboards will be needed. If the difference is too big then other options may have to be considered. |
− | ** | + | **<span style="background-color: yellow; font-weight: 700;">use a spiral tunnel or ''switchback/zigzag''</span> to build track between the two levels. This will reduce number of extra baseboards. |
− | ** | + | **<span style="background-color: yellow; font-weight: 700;">add portals</span> 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. |
</td> | </td> | ||
</tr> | </tr> | ||
Line 100: | Line 117: | ||
<td>[[file:Stop.PNG|link=]]</td> | <td>[[file:Stop.PNG|link=]]</td> | ||
<td> | <td> | ||
− | 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 | + | 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 can be extremely difficult to change (not impossible but often not worth the time and effort).</td> |
</tr> | </tr> | ||
</table> | </table> | ||
<br clear=all> | <br clear=all> | ||
+ | For the solutions to other problems that have been known to occur, but less frequently than those described above, jump to the section [[file:PageLink.PNG|link=]] '''[[#Uncommon Problems (and Their Solutions)|Uncommon Problems (and Their Solutions)]]''' found at the end of this page. | ||
+ | <br><br> | ||
<table cellpadding="4" bgcolor=#ffffb0> | <table cellpadding="4" bgcolor=#ffffb0> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 113: | Line 132: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
<table width="100%"> | <table width="100%"> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 122: | Line 140: | ||
='''Selecting and Loading the Routes to Merge'''= | ='''Selecting and Loading the Routes to Merge'''= | ||
− | [[file:DotPoint1.JPG|link=]] | + | <table cellpadding="4" bgcolor=#ffffff> <!-- BEGIN Step table --> |
− | <table cellpadding="4" bgcolor=#bbffff> | + | <tr valign="top"> |
+ | <td>[[file:Steps.PNG|link=]]<br><br> | ||
+ | <span style="font-size: 17px; font-weight: 700;">Steps</span></td> | ||
+ | <td>[[file:DotPoint1.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Load the ''Base Route'' Into Surveyor:</span><br> | ||
+ | <table cellpadding="4" bgcolor=#bbffff> <!-- BEGIN Step 1 table --> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Question.PNG|link=]]</td> | <td>[[file:Question.PNG|link=]]</td> | ||
Line 129: | Line 151: | ||
---- | ---- | ||
<br> | <br> | ||
− | 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 this is the case then load the Session. If the Session contains nothing that you need, then only load the Route. | + | 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 this is the case then load the '''Session'''. If the '''Session''' contains nothing that you need, then only load the '''Route'''. |
<br><br> | <br><br> | ||
− | Note that when you add the '''to-be-merged route''' its Route assets and data will be loaded but not any Session assets or data so this is the only opportunity you will have to load any Session assets and data. If the Session attached to the ''Base Route'' contains nothing that you need then load the Route only into Surveyor. | + | Note that when you add the '''to-be-merged route''' its '''Route''' assets and data will be loaded but not any '''Session''' assets or data so this is the only opportunity you will have to load any '''Session assets''' and data. If the '''Session''' attached to the ''Base Route'' contains nothing that you need then load the '''Route''' only into Surveyor. |
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 1 table --> | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 151: | Line 164: | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td> </td> |
− | + | <td>[[file:DotPoint2.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Start the ''Merge Route Tool'' and select and load the Route ''to-be-merged'':</span><br> | |
− | * | + | <table> <!-- BEGIN Step 2 table --> |
− | ::This will open a '''Route Selection''' window (shown below) | + | <tr valign="top"> |
− | *'''Select the route ''to-be-merged''''' | + | <td> |
− | <table cellpadding="4" bgcolor=#c1e7e7> | + | *Select the '''Merge Route''' option in the '''Surveyor Main Menu''' ('''TANE''' - shown below left) or the '''Surveyor Tools Menu''' ('''TRS19/Trainz Plus''' - shown below middle) |
+ | ::This will open a '''Route Selection''' window (shown below right) | ||
+ | *'''Select the route ''to-be-merged'''''. Only the '''Route data''' will be loaded from this route<br> | ||
+ | <table cellpadding="4" bgcolor=#c1e7e7> <!-- BEGIN Step 2 Dot Point Table --> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
<td>'''DLC payware routes cannot be selected for merging'''</td> | <td>'''DLC payware routes cannot be selected for merging'''</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Step 2 Dot Point Table --> |
+ | </td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:MergeMainMenu.JPG|link=]] [[file:MergeToolStartTRS19SP1.png|link=]] [[file:MergeSelectRoute.JPG|link=]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 2 table --> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 168: | Line 190: | ||
----</td> | ----</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Steps Table --> |
<br> | <br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
This will display a "minimap" of the proposed merger (nothing will be merged until after the final step) with some control options. | This will display a "minimap" of the proposed merger (nothing will be merged until after the final step) with some control options. | ||
<br> | <br> | ||
Line 203: | Line 218: | ||
</tr> | </tr> | ||
</table><br> | </table><br> | ||
− | <span style="font-size: 17px; font-weight: 700;">TRS19 | + | <span style="font-size: 17px; font-weight: 700;">TRS19/Trainz Plus</span><br> |
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:MergeMapTRS19SP1.png]]</td> | <td>[[file:MergeMapTRS19SP1.png]]</td> | ||
− | <td>The '''Map Conflict''' tab icon in ''' | + | <td>The '''Map Conflict''' tab icon in '''TRS19''' and '''Trainz Plus'''</td> |
</tr> | </tr> | ||
</table></td> | </table></td> | ||
Line 279: | Line 294: | ||
... the conflict has now been resolved.</td> | ... the conflict has now been resolved.</td> | ||
<td> | <td> | ||
− | <span style="font-size: 17px; font-weight: 700;">TRS19 | + | <span style="font-size: 17px; font-weight: 700;">TRS19/Trainz Plus</span><br> |
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:MergeLayersTRS19SP1.png]]</td> | <td>[[file:MergeLayersTRS19SP1.png]]</td> | ||
− | <td>The '''Layers Conflict''' tab icon in ''' | + | <td>The '''Layers Conflict''' tab icon in '''TRS19''' and '''Trainz Plus'''</td> |
</tr> | </tr> | ||
</table> | </table> | ||
Line 404: | Line 419: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
+ | ='''Uncommon Problems (and Their Solutions)'''= | ||
+ | <table cellpadding="4" bgcolor=#c1e7e7> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''All of these problems occur along baseboard boundaries after the merge but not just on the merge boundary''' - they can appear many baseboards away and can take a lot of searching to find.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | |||
+ | These problems include:- | ||
+ | *'''random needle spikes''' (like tall sewing needles sticking up through your layout) | ||
+ | *'''random inverted needle spikes''' (like someone decided to bore very narrow vertical shafts into your layout) | ||
+ | *'''long straight ditches''' | ||
+ | *'''texture bleeds''' (on bare baseboards) | ||
+ | *'''random dark "splotches"''' (on textured baseboards) | ||
+ | <br> | ||
+ | <table cellpadding="4" bgcolor=#ffffb0> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:NotePad.PNG|link=]]</td> | ||
+ | <td><span style="font-size: 17px; font-weight: 700;">Notes:'''</span><br> | ||
+ | *the texture bleeds are relatively easy to solve after the merge has occurred and that solution can be found in the '''Trainz Wiki''' at [[file:WikiLink.PNG|link=]] '''[[How to Use Bulk Asset Update/Replace Tool]]'''. | ||
+ | *the other issues are more difficult or time consuming to solve '''after the merge'''. A better option is to restart the merge process from the original routes (that is why you should make backup copies first) using the steps described below.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table cellpadding="4" bgcolor=#ffffff> <!-- BEGIN Steps table --> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:Steps.PNG|link=]]<br><br> | ||
+ | <span style="font-size: 17px; font-weight: 700;">Steps</span></td> | ||
+ | <td>[[file:DotPoint1.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Create a Small Dummy Route:</span><br> | ||
+ | <table> <!-- BEGIN Step 1 table --> | ||
+ | <tr valign="top"> | ||
+ | <td>Create a new Trainz route using just two bare baseboards with:- | ||
+ | *an East-West orientation for an East-West merge, or | ||
+ | *a North-South orientation for a North-South merge | ||
+ | Do not worry about the height of the baseboards. Save the route using an easy to remember name such as '''Merge Dummy''' | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table cellpadding="4" bgcolor=#ffffb0> <!-- BEGIN Tips table --> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:PencilTips.PNG|link=]]</td> | ||
+ | <td>If merging is something that you will do often then create your '''Merge Dummy''' route as a 2x2 baseboard square for quickly solving these problems if they should appear. The 2x2 baseboards will work with both East-West and North-South merges</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Tips table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 1 table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td> </td> | ||
+ | <td>[[file:DotPoint2.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Load the First Route:</span><br> | ||
+ | <table> <!-- BEGIN Step 2 table --> | ||
+ | <tr valign="top"> | ||
+ | <td>Load the base route into Surveyor - see the section [[file:PageLink.PNG|link=]] '''[[#Selecting and Loading the Routes to Merge|Selecting and Loading the Routes to Merge]]'''. | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 2 table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td> </td> | ||
+ | <td>[[file:DotPoint3.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Load and Position the Merge Dummy Route:</span><br> | ||
+ | <table> <!-- BEGIN Step 3 table --> | ||
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | #Select the '''Merge Route''' option and load the '''Merge Dummy''' into Surveyor (the images below show a 2x2 baseboard '''Merge Dummy''' route) | ||
+ | #Move the '''Merge Dummy''' route into position so that it will overlap, by one baseboard each, the first route and the yet to be loaded second route | ||
+ | #Resolve any Layer conflicts | ||
+ | #Accept the merge | ||
+ | [[file:MergeDummy1.png|link=|alt=Merge Stage 1]] | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 3 table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td> </td> | ||
+ | <td>[[file:DotPoint4.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Load and Position the Second Route:'''</span><br> | ||
+ | <table> <!-- BEGIN Step 4 table --> | ||
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | #Select the '''Merge Route''' option and load the second route into Surveyor | ||
+ | #Move the second route into its merge position with the first route. It must overlap, by one baseboard, the '''Merge Dummy''' route | ||
+ | #Resolve any Layer conflicts | ||
+ | #Accept the merge | ||
+ | [[file:MergeDummy2.png|link=|alt=Merge Stage 1]] | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 4 table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td> </td> | ||
+ | <td>[[file:DotPoint5.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Delete the Merge Dummy Route'''</span><br> | ||
+ | <table> <!-- BEGIN Step 5 table --> | ||
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | Do not worry if the bare baseboards in the '''Merge Dummy''' route show any texture bleeds because the final step is to:- | ||
+ | *Delete each of the baseboards from the '''Merge Dummy''' route | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Step 5 table --> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td colspan="2"> | ||
+ | ----</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Steps table --> | ||
+ | <br> | ||
+ | <table width="100%"> <!-- BEGIN Back to top --> | ||
+ | <tr valign="top"> | ||
+ | <td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Back to top --> | ||
---- | ---- | ||
---- | ---- | ||
Line 419: | Line 572: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | ---- | |
+ | This page was created by Trainz user '''<span class="plainlinks">[http://online.ts2009.com/mediaWiki/index.php/User:Pware pware]</span>''' in July 2018 and was last updated as shown below. | ||
+ | ---- | ||
[[Category:How-to guides]] | [[Category:How-to guides]] |
Revision as of 07:50, 4 May 2021
The information in this Wiki Page applies to TANE, TRS19 and Trainz Plus.
Contents |
In Summary: | |
Merging allows two (or more) routes to be joined to make a single larger route | |
The Session data from the first route only can be transferred to the new enlarged route | |
Physical difference between the routes will cause problems in the merging process. Most of these problems can be overcome |
Before You Start Merging
Make sure that you have backup copies of all the routes that you are going to merge. |
Before you start merging there are some important points you will need to consider and there may be some preparation work that will have to be performed.
Identify...
|
Latitude, Longitude and Altitude
A common misconception is that the Latitude and Longitude of the routes being merged plays a part in the merging process |
The Latitude and Longitude of a route has absolutely no effect on the route itself apart from setting the season of the year along with the date entered into the Environment Tools. Even then it is only the North/South component of the entered Latitude that is important.
A route with its geographic coordinates set in Northern Alaska will happily merge with a route set in outback Australia - but what you do with all the snow and the dust is another problem ;-)
Altitude differences between the two selected routes, however, can cause issues. See Common Problems (and Their Solutions) below.
Route File Sizes
The success of the merging process will depend on the size of the two routes being merged and the size of your systems available memory |
The merging process occurs within your computers on-board memory (RAM). If this is not large enough then your system will also use virtual RAM, i.e. your disk storage space as temporary memory, which is significantly slower. If your system does not have enough memory, both on-board and virtual, then merging large routes will become a problem (i.e. impossible or will take a very long time).
The Trainz forums contain several threads where attempts to merge very large routes (hundreds of Megabytes in size) have taken days to complete or failed to complete at all. In many of these cases the users did not have enough RAM (on-board and virtual) installed in their system. In one documented case, doubling the available on-board RAM from 16GB to 32GB and increasing the Windows virtual memory page size (disk based or virtual RAM) reduced the merge time for two extremely large routes from failing to complete in over 50 hours to successfully completing in 10 hours.
In most cases there should be no technical problems in merging routes (and completing the task in minutes) on systems that meet the recommended specs for TANE and TRS19 |
Common Problems (and Their Solutions)
Most route mergers will have problems but most of these problems can be easily fixed |
Some problems will require you to do a bit (or a lot) of extra work before you can merge two routes into one. But for some problems, the best solution may be to select other 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 can be extremely difficult to change (not impossible but often not worth the time and effort). |
For the solutions to other problems that have been known to occur, but less frequently than those described above, jump to the section Uncommon Problems (and Their Solutions) found at the end of this page.
A handy tip for merging two routes with different heights is to create a new route that only contains the extra "in-between" baseboards - no scenery, textures or track are needed. The baseboards on one end will have heights that match those of the base route and the baseboards on the other end will have heights that match those of the to-be-merged route. The merge is performed in two stages:-
|
Selecting and Loading the Routes to Merge
Steps |
Load the Base Route Into Surveyor:
|
||||
|
|||||
Start the Merge Route Tool and select and load the Route to-be-merged:
|
|||||
|
This will display a "minimap" of the proposed merger (nothing will be merged until after the final step) with some control options.
The Merge Map
Move the To-Be-Merged Route into its New Position
|
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 below 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. |
|
TRS19/Trainz Plus
|
Delete one of the conflicting layers. Select the layer and click on the Delete icon. |
|
Merge one of the conflicting layers. |
|
|
Steps:
|
|
|
... 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 to accept the merge. This icon will not be clickable unless ALL conflicts have been resolved. If you have problems after clicking Accept, see the sections at the top of this wiki page on File Sizes and Common Problems | |
REJECT: Click to reject the merge. The merging will be cancelled, no routes will be lost or altered. |
Uncommon Problems (and Their Solutions)
All of these problems occur along baseboard boundaries after the merge but not just on the merge boundary - they can appear many baseboards away and can take a lot of searching to find. |
These problems include:-
- random needle spikes (like tall sewing needles sticking up through your layout)
- random inverted needle spikes (like someone decided to bore very narrow vertical shafts into your layout)
- long straight ditches
- texture bleeds (on bare baseboards)
- random dark "splotches" (on textured baseboards)
Notes:
|
|
|||||
Steps |
Create a Small Dummy Route:
|
||||
|
|||||
Load the First Route:
|
|||||
|
|||||
Load and Position the Merge Dummy Route:
|
|||||
|
|||||
Load and Position the Second Route:
|
|||||
|
|||||
Delete the Merge Dummy Route
|
|||||
|
Trainz Wiki
More Tutorials and Guides to Using Trainz |
This page was created by Trainz user pware in July 2018 and was last updated as shown below.