How to Use Procedural Track

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The information in this Wiki Page covers the use of procedural track in Surveyor (Classic and Surveyor 2.0) and applies to TANE, TRS19, Trainz Plus and TRS22. This guide does not show how to create procedural track assets. For information on creating procedural track assets see the Trainz Wiki Links at the bottom of this page.

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

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

Non Procedural Track

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).   Warning: 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

Non Procedural Track

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.

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.

Laying Procedural Track

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.

A red track spline circle or a red spline endpoint dot in Surveyor indicates that the procedural track junction is faulty

Surveyor Classic

Faulty procedural track junctions are indicted in Surveyor Classic (shown on the left) by:- Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 solid red track spline circles, or Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 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
A normal procedural track junction in Surveyor 2.0 is shown as a black track spline point		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:- Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 a red spline endpoint dot Another indicator is the absence of the moveable switch blade and the check rails/frogs in the junction.

Procedural Track Errors

Some of the most common causes of red track spline circles (in Surveyor Classic) and red spline endpoint dots (in Surveyor 2.0) 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
	Fault: One of the tracks used to form the junction is not a procedural track Solution: Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 ignore, or Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 if possible replace the non procedural track with a procedural track
Curve Too Tight
	Fault: One of the diverging tracks has a curve radius that is too tight Solution: Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Increase the curve radius
Track Splines Not Level
	Fault: The spline circles that define the junction are not at the same height Solution: Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 adjust the spline heights to create a level junction 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
	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: Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 ignore, or Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 adjust the placement of the second junction to allow the frogs/check rails to be added to the first junction 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.

---

---

Trainz Wiki

More Tutorials and Guides to Using Trainz How to Guides Driver Commands List Session Rules List (Alphabetical) with Parameters Session Rules List (Categories) With Parameters

Related Content Creation Guides How to Build Procedural Track For TANE

---

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

---