How to Merge Routes
(added Latitude and Longitude) |
m |
||
(7 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | The information in this Wiki Page applies to '''TANE''', '''TRS19''' | + | The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''. |
__TOC__ | __TOC__ | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td colspan=2><span style="font-size: 17px; font-weight: 700;">In Summary:</span></td> | <td colspan=2><span style="font-size: 17px; font-weight: 700;">In Summary:</span></td> | ||
Line 18: | Line 18: | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
<td>'''Physical difference between the routes will cause problems in the merging process.''' Most of these problems can be overcome</td> | <td>'''Physical difference between the routes will cause problems in the merging process.''' Most of these problems can be overcome</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''Payware (DLC) routes cannot be selected as a route to be merged</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
− | + | <table> <!-- BEGIN Nav Buttons Table --> | |
+ | <tr valign="top"> | ||
+ | <td width=729><span id="stepBefore"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepSelecting|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
='''Before You Start Merging'''= | ='''Before You Start Merging'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 32: | Line 44: | ||
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. | 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. | ||
− | <table | + | <table bgcolor=#000000 width=900> |
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table bgcolor=#ffffe0> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
<td><span style="font-size: 17px;">'''Identify...'''</span><br> | <td><span style="font-size: 17px;">'''Identify...'''</span><br> | ||
+ | *if either of the routes is a payware route. Payware routes cannot be used in a merge. | ||
*the route that will be the '''base route'''. This route will form the ''backbone'' of the merged routes. It 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 '''base route'''. This route will form the ''backbone'' of the merged routes. It 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 '''to-be-merged route'''. This route will be joined to the ''base route''. | *the route that will be the '''to-be-merged route'''. This route will be joined to the ''base route''. | ||
Line 42: | Line 58: | ||
*the height of the baseboards in both routes at the merge point. Are they the '''same height or different heights?''' | *the height of the baseboards in both routes at the merge point. Are they the '''same height or different heights?''' | ||
*any layers in the two routes that have the same name. | *any layers in the two routes that have the same name. | ||
− | *which layers in both routes contain the tracks and the track objects (signals, switches, speed signs, etc).</td> | + | *which layers in both routes contain the tracks and the track objects (signals, switches, speed signs, etc). |
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | ==Latitude | + | ==Latitude, Longitude and Altitude== |
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 54: | Line 74: | ||
</table> | </table> | ||
<br> | <br> | ||
− | The '''Latitude''' and '''Longitude''' of a route has absolutely no effect on the route itself apart from setting the season of the year | + | 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 ;-) | 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== | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 71: | Line 93: | ||
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= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 81: | Line 103: | ||
==Common Problems (and Their Solutions)== | ==Common Problems (and Their Solutions)== | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 111: | Line 133: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#fcbcbc> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Stop.PNG|link=]]</td> | <td>[[file:Stop.PNG|link=]]</td> | ||
Line 121: | Line 143: | ||
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. | 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> | <br><br> | ||
− | <table | + | <table bgcolor=#000000> |
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table bgcolor=#ffffe0 width=900> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
Line 127: | Line 152: | ||
*the ''new bridging route'' is merged with the ''Base route''. | *the ''new bridging route'' is merged with the ''Base route''. | ||
*the selected ''to-be-merged route'' is merged with the ''Base + bridging route''. | *the selected ''to-be-merged route'' is merged with the ''Base + bridging route''. | ||
− | This avoids having to add the extra baseboards to the original routes.</td> | + | This avoids having to add the extra baseboards to the original routes. |
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
− | + | ||
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
+ | <table> <!-- BEGIN Nav Buttons Table --> | ||
+ | <tr valign="top"> | ||
+ | <td width=729><span id="stepSelecting"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepBefore|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepMergeMap|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
='''Selecting and Loading the Routes to Merge'''= | ='''Selecting and Loading the Routes to Merge'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> <!-- BEGIN Step table --> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Steps.PNG|link=]]<br><br> | <td>[[file:Steps.PNG|link=]]<br><br> | ||
<span style="font-size: 17px; font-weight: 700;">Steps</span></td> | <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> | <td>[[file:DotPoint1.JPG|link=]] <span style="font-size: 17px; font-weight: 700;">Load the ''Base Route'' Into Surveyor:</span><br> | ||
− | <table cellpadding= | + | <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 167: | Line 200: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
− | *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) | + | *Select the '''Merge Route''' option in the '''Surveyor Main Menu''' ('''TANE''' - shown below left) or the '''Surveyor Tools Menu''' ('''TRS19/Trainz Plus/TRS22''' - shown below middle) |
::This will open a '''Route Selection''' window (shown below right) | ::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> | *'''Select the route ''to-be-merged'''''. Only the '''Route data''' will be loaded from this route<br> | ||
− | <table cellpadding= | + | <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> | ||
Line 192: | Line 225: | ||
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> | ||
− | <table | + | <table> <!-- BEGIN Nav Buttons Table --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td width=729><span id="stepMergeMap"></span> </td> |
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepSelecting|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepLayers|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Nav Buttons Table --> |
− | + | ||
='''The Merge Map'''= | ='''The Merge Map'''= | ||
<table> | <table> | ||
Line 207: | Line 243: | ||
*'''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. | ||
<br> | <br> | ||
− | <table cellpadding=" | + | <table bgcolor=#000000 cellpadding="2"> |
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table cellpadding=4 bgcolor=#ffffb0> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:NotePad.PNG|link=]]</td> | <td>[[file:NotePad.PNG|link=]]</td> | ||
<td><span style="font-size: 17px;">'''Notes:'''</span><br> | <td><span style="font-size: 17px;">'''Notes:'''</span><br> | ||
+ | ---- | ||
*You can zoom the MiniMap in and out using the mouse control wheel. There appears to be no keyboard zoom control. | *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. | *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 '''''to-be-merged route''''' in the direction shown by each arrow.</td> | *The four arrows shown at the top, bottom and both sides of the map display can be clicked to move the '''''to-be-merged route''''' in the direction shown by each arrow.</td> | ||
</tr> | </tr> | ||
− | </table><br> | + | </table> |
− | <span style="font-size: 17px; font-weight: 700;">TRS19/Trainz Plus</span><br> | + | </td> |
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <span style="font-size: 17px; font-weight: 700;">TRS19/Trainz Plus/TRS22</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 '''TRS19''' | + | <td>The '''Map Conflict''' tab icon in '''TRS19''', '''Trainz Plus''' and '''TRS22'''</td> |
</tr> | </tr> | ||
− | </table></td> | + | </table> |
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 232: | Line 277: | ||
<td>[[file:MergeMiniMapComplexTerrain02.JPG|link=]]</td> | <td>[[file:MergeMiniMapComplexTerrain02.JPG|link=]]</td> | ||
<td> | <td> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Steps.PNG|link=]]</td> | <td>[[file:Steps.PNG|link=]]</td> | ||
Line 247: | Line 292: | ||
In the example shown on the left, clicking the '''Left''' arrow 5 times moved the ''to-be-merged route'' 5 baseboards to the left to a position where there were no overlapping baseboards and all terrain conflicts were resolved. | In the example shown on the left, clicking the '''Left''' arrow 5 times moved the ''to-be-merged route'' 5 baseboards to the left to a position where there were no overlapping baseboards and all terrain conflicts were resolved. | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 257: | Line 302: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table | + | <table> <!-- BEGIN Nav Buttons Table --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td width=729><span id="stepLayers"></span> </td> |
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepMergeMap|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepProblems|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Nav Buttons Table --> |
='''The Layers Map'''= | ='''The Layers Map'''= | ||
Click the '''Layers Tab''' to show the layers loaded from the two routes. | Click the '''Layers Tab''' to show the layers loaded from the two routes. | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 276: | Line 325: | ||
There are three simple options for solving this problem:- | There are three simple options for solving this problem:- | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint1.JPG|link=]]</td> | <td>[[file:DotPoint1.JPG|link=]]</td> | ||
Line 292: | Line 341: | ||
... 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/Trainz Plus</span><br> | + | <span style="font-size: 17px; font-weight: 700;">TRS19/Trainz Plus/TRS22</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 '''TRS19''' | + | <td>The '''Layers Conflict''' tab icon in '''TRS19''', '''Trainz Plus''' and '''TRS22'''</td> |
</tr> | </tr> | ||
</table> | </table> | ||
Line 303: | Line 352: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint2.JPG|link=]]</td> | <td>[[file:DotPoint2.JPG|link=]]</td> | ||
Line 314: | Line 363: | ||
<td> | <td> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#fcbcbc> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Stop.PNG|link=]]</td> | <td>[[file:Stop.PNG|link=]]</td> | ||
Line 331: | Line 380: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint3.JPG|link=]]</td> | <td>[[file:DotPoint3.JPG|link=]]</td> | ||
Line 337: | Line 386: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr> | <tr> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 357: | Line 406: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:MergeMiniMapLayersConflictMerge01.JPG|link=]]</td> | <td>[[file:MergeMiniMapLayersConflictMerge01.JPG|link=]]</td> | ||
− | <td><table cellpadding= | + | <td><table cellpadding=4 bgcolor=#fcbcbc> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Stop.PNG|link=]]</td> | <td>[[file:Stop.PNG|link=]]</td> | ||
Line 363: | Line 412: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr> | <tr> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 391: | Line 440: | ||
</table> | </table> | ||
<br> | <br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
='''Accept or Reject'''= | ='''Accept or Reject'''= | ||
Line 412: | Line 455: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table | + | <table> <!-- BEGIN Nav Buttons Table --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td width=729><span id="stepProblems"></span> </td> |
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepLayers|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Nav Buttons Table --> |
− | + | ||
='''Uncommon Problems (and Their Solutions)'''= | ='''Uncommon Problems (and Their Solutions)'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 433: | Line 479: | ||
*'''random dark "splotches"''' (on textured baseboards) | *'''random dark "splotches"''' (on textured baseboards) | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffb0> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:NotePad.PNG|link=]]</td> | <td>[[file:NotePad.PNG|link=]]</td> | ||
<td><span style="font-size: 17px; font-weight: 700;">Notes:'''</span><br> | <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 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> | *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> | ||
Line 442: | Line 489: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> <!-- BEGIN Steps table --> |
<tr> | <tr> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 461: | Line 508: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
− | <table | + | <table bgcolor=#000000 width=904> <!-- BEGIN Tips Tabe --> |
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table bgcolor=#ffffe0 width=900> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <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> | <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> | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> <!-- END Tips table --> | </table> <!-- END Tips table --> | ||
Line 550: | Line 603: | ||
</table> <!-- END Steps table --> | </table> <!-- END Steps table --> | ||
<br> | <br> | ||
− | <table | + | <table> <!-- BEGIN Nav Buttons Table --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td width=729><span id="bottom"></span> </td> |
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepProblems|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END Nav Buttons Table --> |
---- | ---- | ||
---- | ---- | ||
+ | |||
='''Trainz Wiki'''= | ='''Trainz Wiki'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:TrainzWiki.png|link=]]</td> | <td>[[file:TrainzWiki.png|link=]]</td> |
Revision as of 12:07, 13 June 2022
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22.
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 | |
Payware (DLC) routes cannot be selected as a route to be merged |
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.
|
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.
|
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/TRS22
|
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.