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 width=700>

<table cellpadding=4 bgcolor=#c1e7e7>

<td>[[file:DotPoint.JPG|link=]]</td>

<td>'''Procedural tracks are specific track splines that have been created for use with Trainz versions from T:ANE onwards '''</td>

<td>[[file:DotPoint.JPG|link=]]</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, 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 align="center" bgcolor="lightcyan"><span style="font-weight: 700; font-size: 17px;">Procedural Track</span><br>

<td>If you turn pause '''OFF''' after using the '''UDS''' (available in '''TRS19 Platinum Edition''' and later 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

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.

<table>

<table bgcolor=#000000 width=600>

<td>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.</td>

<table cellpadding=4 bgcolor=#c1e7e7>

<td>[[file:DotPoint.JPG|link=]]</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.

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

 

<table cellpadding=4 bgcolor=#c1e7e7>

<td>[[file:DotPoint.JPG|link=]]</td>

<td>A '''red track spline circle''' in '''Surveyor Classic''' indicates that the procedural track junction is faulty</td>

<table>

Faulty procedural track junctions are indicted in '''Surveyor''' by:-

*solid red track spline circles, or

*flashing red/white or red/yellow track spline circles

<table cellpadding=4 bgcolor=#c1e7e7>

<td>[[file:DotPoint.JPG|link=]]</td>

<td>A '''red track spline "dot"''' in '''Surveyor 2.0''' indicates that the procedural track junction is faulty</td>

<td>[[file:DotPoint.JPG|link=]]</td>

<td>'''Surveyor 2.0''' is a feature of '''Trainz Plus''' (available to subscribers only) and '''TRS22''' for those who have an annual '''Trainz Plus''' subscription</td>

<br>

<table width=650>

<td width=300>[[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>

<td width=50>&nbsp;</td>

<td width=300>[[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. A better indicator is the absence of the moveable switch blade and the check rails/frogs.</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>

*ignore, or

*if possible replace the non procedural track with a procedural track

*Increase the curve radius

*adjust the spline heights to create a level junction

*ignore, or

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