How to Use Procedural Track

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
m
m
Line 15: Line 15:
 
<table>
 
<table>
 
<tr valign="top">
 
<tr valign="top">
−
<td align="center" bgcolor="lightcyan">'''Procedural Track'''<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=]]</td>
 
[[image:Procedural-LeftPath.png|link=]][[image:Procedural-RightPath.png|link=]]</td>
−
<td align="center" bgcolor="lightyellow">'''Non Procedural Track'''<br>
+
<td align="center" bgcolor="lightyellow"><span style="font-weight: 700; font-size: 17px;">Non Procedural Track</span><br>
 
[[image:Procedural-NoPath.png|link=]]</td>
 
[[image:Procedural-NoPath.png|link=]]</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
−
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'''.
+
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).
 
[[image:Procedural-CheckPauseOFF.png|link=]]
 
[[image:Procedural-CheckPauseOFF.png|link=]]
 
<table>
 
<table>
 
<tr valign="top">
 
<tr valign="top">
−
<td align="center" bgcolor="lightcyan">'''Procedural Track'''<br>
+
<td align="center" bgcolor="lightcyan"><span style="font-weight: 700; font-size: 17px;">Procedural Track</span><br>
 
[[image:Procedural-FrogsCheckRails.png|link=]]</td>
 
[[image:Procedural-FrogsCheckRails.png|link=]]</td>
−
<td align="center" bgcolor="lightyellow">'''Non Procedural Track'''<br>
+
<td align="center" bgcolor="lightyellow"><span style="font-weight: 700; font-size: 17px;">Non Procedural Track</span><br>
 
[[image:Procedural-NonFrogsCheckRails.png|link=]]</td>
 
[[image:Procedural-NonFrogsCheckRails.png|link=]]</td>
 
</tr>
 
</tr>
Line 43: Line 43:
 
</table>
 
</table>
  
−
Procedural track is laid down in '''Surveyor''' just like any other track. Track junctions are formed in the same way as they are when using non-procedural track assets. The difference is that the additional features shown above (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: 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.
 
<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.
Line 50: Line 50:
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
−
<td>A '''red spline circle''' indicates that the procedural track junction is faulty</td>
+
<td>A '''red track spline circle''' indicates that the procedural track junction is faulty</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 65: Line 65:
 
</table>
 
</table>
  
−
'''WORK IN PROGRESS'''
+
='''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=800>
 +
<tr valign="top">
 +
<td align="center" colspan=2 bgcolor="red"><span style="font-weight: 700; font-size: 17px; color: white;">Incompatible Tracks</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td width=350>[[image:Procedural-NonProceduralJunction.png|link=]]</td>
 +
<td>'''Fault:'''
 +
One of the tracks used to form the junction is not a procedural track<br>
 +
 
 +
'''Solution:'''
 +
*ignore, or
 +
*if possible replace the non procedural track with a procedural track
 +
</td>
 +
</tr>
 +
<tr valign="top">
 +
<td align="center" colspan=2 bgcolor="red"><span style="font-weight: 700; font-size: 17px; color: white;">Curve Too Tight</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:Procedural-CurveTight.png|link=]]</td>
 +
<td>'''Fault:'''
 +
One of the diverging tracks has a curve radius that is too tight<br>
 +
 
 +
'''Solution:'''
 +
*reduce the curve radius
 +
</td>
 +
</tr>
 +
<tr valign="top">
 +
<td align="center" colspan=2 bgcolor="red"><span style="font-weight: 700; font-size: 17px; color: white;">Track Splines Not Level</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:Procedural-SplineHeight.png|link=]]</td>
 +
<td>'''Fault:'''
 +
The spline points that define the junction are not at the same height<br>
 +
 
 +
'''Solution:'''
 +
*adjust the spline heights to create a level junction
 +
</td>
 +
</tr>
 +
<tr valign="top">
 +
<td align="center" colspan=2 bgcolor="red"><span style="font-weight: 700; font-size: 17px; color: white;">Junctions Too Close</span></td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[image:Procedural-JunctionsTooClose.png|link=]]</td>
 +
<td>'''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<br>
 +
 
 +
'''Solution:'''
 +
*adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction
 +
</td>
 +
</tr>
 +
</table>
 +
 
 
----
 
----
 
----
 
----

Revision as of 21:04, 5 June 2021

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.

Contents

What is Procedural Track?

DotPoint.JPG Procedural tracks provide animated switch points plus check rails and frogs at track junctions


Procedural track works just like the standard pre-TANE track (non-procedural track) but provides additional cosmetic features.

Procedural Track
Procedural-LeftPath.pngProcedural-RightPath.png		 Non Procedural Track
Procedural-NoPath.png

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). Procedural-CheckPauseOFF.png

Procedural Track
Procedural-FrogsCheckRails.png		 Non Procedural Track
Procedural-NonFrogsCheckRails.png

These features are built into the track asset and do not have to be manually added when laying track.

Laying Procedural Track

DotPoint.JPG 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.

DotPoint.JPG A red track spline circle indicates that the procedural track junction is faulty
Procedural-ErrorRedSpline.png

Faulty procedural track junctions are indicted in Surveyor by:-

  • solid red track splines, or
  • flashing red/white or red/yellow track splines

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.

Incompatible Tracks
Procedural-NonProceduralJunction.png Fault:

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

Solution:

  • ignore, or
  • 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:

  • reduce the curve radius
Track Splines Not Level
Procedural-SplineHeight.png Fault:

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

Solution:

  • adjust the spline heights to create a level junction
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:

  • adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction

Trainz Wiki

TrainzWiki.png

More Tutorials and Guides to Using Trainz

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=29673"
Personal tools