How to Use Procedural Track

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
m
(→‎Laying Procedural Track)
 
(29 intermediate revisions by one user not shown)
Line 1: Line 1:
−
The information in this Wiki Page applies to '''TANE''', '''TRS19''' and '''Trainz Plus'''. This guide covers the use of procedural track in Trainz Surveyor, not how to create procedural track assets.  
+
<table width=1000>
 +
<tr valign="top">
 +
<td>
 +
The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''. This guide covers the use of procedural track in Trainz Surveyor, not how to create procedural track assets - see '''Trainz Wiki Links''' at the bottom of this page.</td>
 +
</tr>
 +
</table>
  
 +
<table>
 +
<tr valign="top">
 +
<td>
 
__TOC__
 
__TOC__
−
='''What is Procedural Track?'''=
+
</td>
−
<table cellpadding="4" bgcolor=#c1e7e7>
+
<td>
 +
<table width=700 bgcolor="lightcyan" cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
−
<td>[[image:DotPoint.JPG|link=]]</td>
+
<td colspan=2><span style="font-size: 17px; font-weight: 700;">In Summary:</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td width=10>[[image:BlueDot10x10.png|link=]]</td>
 +
<td>'''Procedural tracks are specific track splines that have been created for use with Trainz versions from T:ANE onwards'''</td>
 +
</tr>
 +
<tr valign="top">
 +
<td width=10>[[image:BlueDot10x10.png|link=]]</td>
 
<td>'''Procedural tracks provide animated switch points plus check rails and frogs at track junctions'''</td>
 
<td>'''Procedural tracks provide animated switch points plus check rails and frogs at track junctions'''</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729>&nbsp;</td>
 +
<td width=46>&nbsp;</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>[[file:NextDown.png|link=#stepID|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
  
−
Procedural track works just like the standard or non-procedural track that was the only type available before T:ANE. However, it provides additional cosmetic features (animated blades, frogs and check rails) to junctions. These features are built into the track asset and do not have to be manually added when laying track.
+
='''What is Procedural Track?'''=
 +
 
 +
<table width=1000>
 +
<tr valign="top">
 +
<td>
 +
Procedural track works just like the standard (or "non-procedural") track that was the only type available before '''T:ANE'''. However, it provides additional cosmetic features (animated blades plus frogs and check rails) to junctions. These features are built into the track asset and do not have to be manually added when laying track.</td>
 +
</tr>
 +
</table>
 +
<br>
  
 
<table>
 
<table>
 
<tr valign="top">
 
<tr valign="top">
−
<td align="center" bgcolor="lightcyan"><span style="font-weight: 700; font-size: 17px;">Procedural Track</span><br>
+
<td align="center" bgcolor="lightcyan">
 +
<span style="font-weight: 700; font-size: 17px;">Procedural Track</span><br>
 
[[image:Procedural-LeftPath.png|link=]][[image:Procedural-RightPath.png|link=]]
 
[[image:Procedural-LeftPath.png|link=]][[image:Procedural-RightPath.png|link=]]
 
</td>
 
</td>
Line 23: Line 60:
 
</table>
 
</table>
  
−
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 width=1000>
 +
<tr valign="top">
 +
<td>
 +
<table 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 colspan=2><span style="font-size: 17px; font-weight: 700;">Notes:'''</span><br>
−
The switch blade animation will show in both '''Driver''' and '''Surveyor''' but in '''TRS19 Platinum Edition''' and '''Trainz Plus''' the '''Pause''' option in '''Surveyor''' must be checked '''OFF''' (no tick).<br>
+
----
−
[[image:Procedural-CheckPauseOFF.png|link=]]</td>
+
The switch blade animation will show in both '''Driver''' and '''Surveyor''' but in '''TRS19''' and later versions the '''Pause''' option in '''Surveyor''' must be checked '''OFF''' (no tick).</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>&nbsp;</td>
 +
<td>[[image:Procedural-CheckPauseOFF.png|link=]]</td>
 +
<td>
 +
<table bgcolor=#fcbcbc>
 +
<tr valign="top">
 +
<td colspan=2><span style="font-size: 17px; font-weight: 700;">Warning:</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:Stop.PNG|link=]]</td>
 +
<td>If you turn pause '''OFF''' after using the '''UDS''' (available in '''TRS19 Platinum Edition''' and later '''Trainz''' versions) to switch from '''Driver''' to '''Surveyor''' then any consists that were moving in '''Driver''' will immediately start moving in '''Surveyor''' which can result in collisions and derailments
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 40: Line 99:
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
<br>
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729><span id="stepID"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#top|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepErrors|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
  
 +
='''Identifying Procedural Track'''=
  
 +
<table width=1000>
 +
<tr valign="top">
 +
<td>
 +
There is no specific content category, such as "Track, procedural", that can be used to distinguish between procedural and non-procedural track assets. Like many assets it relies on the name given to the asset by the content creator. Most creators seem to have included the characters '''PRO''' in the track name - for example "Protrack", "Procedural" or just "Pro". This can be used to narrow down the search in '''CM'''. A typical '''CM''' custom filter that would have a good chance of identifying most procedural track assets is shown below.</td>
 +
</tr>
 +
</table>
 +
 +
<table width=1000>
 +
<tr>
 +
<td>[[image:Procedural-CMFilter.png|link=]]</td>
 +
<td>
 +
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 +
<tr valign="top">
 +
<td>[[image:PencilTips.PNG|link=]]</td>
 +
<td>All procedural track assets have a '''minimum build version''' of '''4.2''' - but this <span style="font-weight: 700; font-size: 15px;">does not</span> mean that any track with this build number (or above) will be procedural.</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
  
 
='''Laying Procedural Track'''=
 
='''Laying Procedural Track'''=
  
−
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table width=1000 bgcolor="lightcyan" cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
−
<td>[[file:DotPoint.JPG|link=]]</td>
+
<td width=10>[[image:BlueDot10x10.png|link=]]</td>
 
<td>'''The "fall-back" position for procedural track is to act and look like ordinary (non-procedural) track'''</td>
 
<td>'''The "fall-back" position for procedural track is to act and look like ordinary (non-procedural) track'''</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
<br>
 +
<table width=1000>
 +
<tr valign="top">
 +
<td>Procedural tracks are laid down in '''Surveyor''' just like any other track. Track junctions are formed in the same way as they are when using non-procedural tracks. The difference is that the additional features (animated switch blades, frogs and check rails) are automatically added when a track junction is '''correctly''' formed using procedural tracks.
  
−
Procedural tracks are laid down in '''Surveyor''' just like any other track. Track junctions are formed in the same way as they are when using non-procedural tracks. The difference is that the additional features (animated switch blades, frogs and check rails) are automatically added when a track junction is '''correctly''' formed using procedural tracks.
+
<span style="background-color: #ffffb0; font-weight: 700;"> Faulty (incorrectly formed) procedural track junctions will work perfectly well as ''non-procedural'' junctions </span> - they can be switched left and right, and trains will pass over them correctly. But the special features that they have will not appear.</td>
 +
</tr>
 +
</table>
  
−
<span style="background-color: yellow; font-weight: 700;"> Faulty (incorrectly formed) procedural track junctions will work perfectly well as ''non-procedural'' junctions </span> - they can be switched left and right, and trains will pass over them correctly. But the special features that they have will not appear.
+
<table width=1000 bgcolor="lightcyan" cellpadding=2>
−
 
+
<tr valign="top">
−
<table cellpadding="4" bgcolor=#c1e7e7>
+
<td width=10>[[image:BlueDot10x10.png|link=]]</td>
 +
<td>A '''red track spline circle''' or a '''red spline endpoint dot''' in '''Surveyor''' indicates that the procedural track junction is faulty</td>
 +
</tr>
 +
</table>
 +
<br>
 +
<table width=1000>
 
<tr valign="top">
 
<tr valign="top">
−
<td>[[file:DotPoint.JPG|link=]]</td>
+
<td colspan=2 align="center" bgcolor=#0000ff><span style="font-weight: 700; font-size: 15px; color: white;">Surveyor Classic</span></td>
−
<td>A '''red track spline circle''' indicates that the procedural track junction is faulty</td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
  
 +
<table width=1000 bgcolor=#000000 cellpadding=2>
 +
<tr valign="top">
 +
<td>
 +
<table width=996 bgcolor=#ffffff cellpadding=2>
 +
<tr valign="top">
 +
<td width=300>[[image:Procedural-ErrorRedSpline.png|link=]]</td>
 +
<td>Faulty procedural track junctions are indicted in '''Surveyor Classic''' (shown on the left) by:-
 
<table>
 
<table>
 
<tr valign="top">
 
<tr valign="top">
−
<td>[[image:Procedural-ErrorRedSpline.png|link=]]</td>
+
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>solid red track spline circles, or</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>flashing red/white or red/yellow track spline circles</td>
 +
</tr>
 +
<tr valign="top">
 +
<td colspan=2>Another indicator is the absence of the moveable switch blade and the check rails/frogs in the junction.</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
 +
<table width=1000>
 +
<tr valign="top">
 +
<td colspan=4 align="center" bgcolor=#0000ff><span style="font-weight: 700; font-size: 15px; color: white;">Surveyor 2.0</span></td>
 +
</tr>
 +
<tr valign="top">
 
<td>
 
<td>
−
Faulty procedural track junctions are indicted in '''Surveyor''' by:-
+
<table width=304 bgcolor=#000000 cellpadding=2>
−
*solid red track splines, or
+
<tr valign="top">
−
*flashing red/white or red/yellow track splines
+
<td>
 +
<table width=300 bgcolor=#ffffff cellpadding=2>
 +
<tr valign="top">
 +
<td>[[image:Procedural-S20-Normal.png|link=]]<br>
 +
A normal procedural track junction in '''Surveyor 2.0''' is shown as a '''black''' track spline point</td>
 +
</tr>
 +
</table>
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
</td>
 +
<td width=5>&nbsp;</td>
 +
<td>
 +
<table width=304 bgcolor=#000000 cellpadding=2>
 +
<tr valign="top">
 +
<td>
 +
<table width=300 bgcolor=#ffffff cellpadding=2>
 +
<tr valign="top">
 +
<td>[[image:Procedural-S20-NotNormal.png|link=]]<br>
 +
A faulty procedural track junction in '''Surveyor 2.0''' is shown as a <span style="color: red; font-weight: 700;">red</span> track spline point</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
<td>
 +
<table>
 +
<tr valign="top">
 +
<td colspan=2>Faulty procedural track junctions are indicted in '''Surveyor 2.0'''  (shown left and in '''Trainz Plus''' and '''TRS22 Platinum''' only) by:-</td>
 +
</tr>
 +
<tr valign="top">
 +
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>a red spline endpoint dot</td>
 +
</tr>
 +
<tr valign="top">
 +
<td colspan=2>Another indicator is the absence of the moveable switch blade and the check rails/frogs in the junction.</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729><span id="stepErrors"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepID|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#bottom|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
  
 
='''Procedural Track Errors'''=
 
='''Procedural Track Errors'''=
  
−
Some of the most common causes of '''red track splines''' are listed below. But remember, that the presence of a '''red track spline''' does not stop the track junction from working correctly as a '''non procedural''' track junction.
+
<table width=1000>
 +
<tr valign="top">
 +
<td>
 +
Some of the most common causes of '''red track spline circles''' are listed below. <span style="background-color: #ffffb0; font-weight: 700;"> Remember, the presence of procedural track errors will not stop track junctions from working correctly as normal (''non procedural'') track junctions. </span></td>
 +
</tr>
 +
</table>
  
 
<table width=800>
 
<table width=800>
Line 88: Line 276:
  
 
'''Solution:'''
 
'''Solution:'''
−
*ignore, or
+
<table>
−
*if possible replace the non procedural track with a procedural track
+
<tr valign="top">
 +
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>ignore, or</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>if possible replace the non procedural track with a procedural track</td>
 +
</tr>
 +
</table>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 101: Line 297:
  
 
'''Solution:'''
 
'''Solution:'''
−
*Increase the curve radius
+
<table>
 +
<tr valign="top">
 +
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>Increase the curve radius</td>
 +
</tr>
 +
</table>
 +
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 110: Line 312:
 
<td>[[image:Procedural-SplineHeight.png|link=]]</td>
 
<td>[[image:Procedural-SplineHeight.png|link=]]</td>
 
<td>'''Fault:'''
 
<td>'''Fault:'''
−
The spline points that define the junction are not at the same height<br>
+
The spline circles that define the junction are not at the same height<br>
  
 
'''Solution:'''
 
'''Solution:'''
−
*adjust the spline heights to create a level junction
+
<table>
 +
<tr valign="top">
 +
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>adjust the spline heights to create a level junction</td>
 +
</tr>
 +
</table>
 
<br>
 
<br>
−
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 width=450>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0 width=446>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
−
<td>One trick is to move the approach and depart spline points closer to the junction spline (if possible) to reduce the length of track that has to be made level</td>
+
<td>One trick is to move the approach and depart spline circles closer to the junction spline circle (if possible) to reduce the length of track that has to be made level</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 133: Line 346:
  
 
'''Solution:'''
 
'''Solution:'''
−
*ignore, or
+
<table>
−
*adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction
+
<tr valign="top">
 +
<td width=10>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>ignore, or</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:DotPoint.JPG|10px|link=]]</td>
 +
<td>adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction</td>
 +
</tr>
 +
</table>
 
<br>
 
<br>
−
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 width=450>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffb0 width=446>
 
<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>This requirement can make it difficult or even impossible to use procedural junctions in yards that have very dense track junction layouts. Ignoring the "problem" may be the only option here.</td>
−
This requirement can make it difficult or even impossible to model yards that have very dense track junction layouts. Ignoring the "problem" mey be the only option here.</td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 146: Line 369:
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729><span id="bottom"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepErrors|alt=Next Up|Top]]</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>&nbsp;</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
  
 
----
 
----
Line 151: Line 386:
  
 
='''Trainz Wiki'''=
 
='''Trainz Wiki'''=
−
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:TrainzWiki.png|link=]]</td>
 
<td>[[file:TrainzWiki.png|link=]]</td>
Line 162: Line 397:
 
</td>
 
</td>
 
</tr>
 
</tr>
 +
</table>
 +
<table>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>

Latest revision as of 18:25, 19 September 2023

The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22. This guide covers the use of procedural track in Trainz Surveyor, not how to create procedural track assets - see Trainz Wiki Links at the bottom of this page.

Contents
In Summary:
BlueDot10x10.png Procedural tracks are specific track splines that have been created for use with Trainz versions from T:ANE onwards
BlueDot10x10.png Procedural tracks provide animated switch points plus check rails and frogs at track junctions


      Next Down Bottom

[edit] What is Procedural Track?

Procedural track works just like the standard (or "non-procedural") track that was the only type available before T:ANE. However, it provides additional cosmetic features (animated blades plus frogs and check rails) to junctions. These features are built into the track asset and do not have to be manually added when laying track.


Procedural Track
Procedural-LeftPath.pngProcedural-RightPath.png

Non Procedural Track
Procedural-NoPath.png
NotePad.PNG Notes:
The switch blade animation will show in both Driver and Surveyor but in TRS19 and later versions the Pause option in Surveyor must be checked OFF (no tick).
  Procedural-CheckPauseOFF.png
Warning:
Stop.PNG If you turn pause OFF after using the UDS (available in TRS19 Platinum Edition and later Trainz versions) to switch from Driver to Surveyor then any consists that were moving in Driver will immediately start moving in Surveyor which can result in collisions and derailments
Procedural Track
Procedural-FrogsCheckRails.png		 Non Procedural Track
Procedural-NonFrogsCheckRails.png


  Top Next Up Next Down Bottom

[edit] Identifying Procedural Track

There is no specific content category, such as "Track, procedural", that can be used to distinguish between procedural and non-procedural track assets. Like many assets it relies on the name given to the asset by the content creator. Most creators seem to have included the characters PRO in the track name - for example "Protrack", "Procedural" or just "Pro". This can be used to narrow down the search in CM. A typical CM custom filter that would have a good chance of identifying most procedural track assets is shown below.
Procedural-CMFilter.png
PencilTips.PNG All procedural track assets have a minimum build version of 4.2 - but this does not mean that any track with this build number (or above) will be procedural.

[edit] Laying Procedural Track

BlueDot10x10.png The "fall-back" position for procedural track is to act and look like ordinary (non-procedural) track


Procedural tracks are laid down in Surveyor just like any other track. Track junctions are formed in the same way as they are when using non-procedural tracks. The difference is that the additional features (animated switch blades, frogs and check rails) are automatically added when a track junction is correctly formed using procedural tracks. Faulty (incorrectly formed) procedural track junctions will work perfectly well as non-procedural junctions - they can be switched left and right, and trains will pass over them correctly. But the special features that they have will not appear.
BlueDot10x10.png A red track spline circle or a red spline endpoint dot in Surveyor indicates that the procedural track junction is faulty


Surveyor Classic
Procedural-ErrorRedSpline.png Faulty procedural track junctions are indicted in Surveyor Classic (shown on the left) by:-
DotPoint.JPG solid red track spline circles, or
DotPoint.JPG flashing red/white or red/yellow track spline circles
Another indicator is the absence of the moveable switch blade and the check rails/frogs in the junction.


Surveyor 2.0
Procedural-S20-Normal.png
A normal procedural track junction in Surveyor 2.0 is shown as a black track spline point
 
Procedural-S20-NotNormal.png
A faulty procedural track junction in Surveyor 2.0 is shown as a red track spline point
Faulty procedural track junctions are indicted in Surveyor 2.0 (shown left and in Trainz Plus and TRS22 Platinum only) by:-
DotPoint.JPG a red spline endpoint dot
Another indicator is the absence of the moveable switch blade and the check rails/frogs in the junction.


  Top Next Up Next Down Bottom

[edit] Procedural Track Errors

Some of the most common causes of red track spline circles are listed below. Remember, the presence of procedural track errors will not stop track junctions from working correctly as normal (non procedural) track junctions.
Incompatible Tracks
Procedural-NonProceduralJunction.png Fault:

One of the tracks used to form the junction is not a procedural track

Solution:

DotPoint.JPG ignore, or
DotPoint.JPG if possible replace the non procedural track with a procedural track
Curve Too Tight
Procedural-CurveTight.png Fault:

One of the diverging tracks has a curve radius that is too tight

Solution:

DotPoint.JPG Increase the curve radius
Track Splines Not Level
Procedural-SplineHeight.png Fault:

The spline circles that define the junction are not at the same height

Solution:

DotPoint.JPG adjust the spline heights to create a level junction


PencilTips.PNG One trick is to move the approach and depart spline circles closer to the junction spline circle (if possible) to reduce the length of track that has to be made level
Junctions Too Close
Procedural-JunctionsTooClose.png Fault:

A second junction has been added that is too close to the first and there is not enough room for the frogs/check rails to be added to the first junction

Solution:

DotPoint.JPG ignore, or
DotPoint.JPG adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction


NotePad.PNG This requirement can make it difficult or even impossible to use procedural junctions in yards that have very dense track junction layouts. Ignoring the "problem" may be the only option here.
  Top Next Up    

[edit] Trainz Wiki

TrainzWiki.png

More Tutorials and Guides to Using Trainz

Related Content Creation Guides

This page was created by Trainz user pware in June 2021 and was last updated as shown below.

Retrieved from "https://online.ts2009.com/mediaWiki/index.php?title=How_to_Use_Procedural_Track&oldid=38791"
Personal tools