A railway crossing employed by NSWGR in the mid 20th century. The default fixed road is replaced by the road asset the user connects to it. The fixed road is long enough for the user to run 2 or more railway tracks over it depending on the angle of the tracks w.r.t. the road and the separation distance of the tracks.
The user-laid tracks are assumed to be bi-directional, and so there are no dedicated 'down' or 'up' tracks.
Intended for use as a core element in a kit allowing the assembly of crossings tailored to their locations. The kit comprises the following KUID 368725 assets:
20384 - NSWGR railway crossing boom gate, lefthand
20385 - NSWGR railway crossing boom gate, righthand
20519 - NSWGR railway crossing road gate pair, manual
20523 - NSWGR railway crossing road gate, manual, cw
20524 - NSWGR railway crossing road gate, manual, acw
20386 - NSWGR railway crossing pedestrian gate, remotely operated, lefthand
20387 - NSWGR railway crossing pedestrian gate, remotely operated, righthand
20522 - NSWGR railway crossing pedestrian gate, user operated
20388 - NSWGR railway crossing warning light, post mount, red flash
20389 - NSWGR railway crossing control, single fixed track, sealed road
20517 - NSWGR railway crossing control, single-track fixed road length, no fixed track
20390 - NSWGR railway crossing control, uni-directional double fixed track, 12ft spacing, sealed road
20525 - NSWGR railway crossing control, bi-directional tracks, double-track fixed road length, no fixed tracks
20391 - NSWGR railway crossing pedestrian boards, single track
20392 - NSWGR railway crossing pedestrian boards, double track, 12ft spacing
90077 - NSWGR railway crossing slave
60013 - Operate railway crossing (driver command)
60034 - Operate railway crossing - session rule
Also important for the kit's operation is KUID:76656:70010 'Directional Trigger'.
Some compatible road assets are:
30154 - Tertiary 2L,8m rural road, unsealed, grey dust on gravel, 40mph (65km/hr)
30171 - Tertiary 2L,8m rural road, unsealed, grey dust on gravel, no traffic
30155 - Tertiary 2L,8m rural road, unsealed, brown dust on gravel, 40mph (65km/hr)
30172 - Tertiary 2L,8m rural road, unsealed, brown dust on gravel, no traffic
For correct communication between this control asset the other animated kit components(gates and lights) in use, a naming convention must be followed.
All in-game names given to the kit components have 3 or 4 elements separated by underscores.
The first name element is the location code for the crossing. This can be any alphanumeric, except if the crossing is to be controlled from a lever frame such as <kuid:368725:90030> 'NSWGR mechanical lever frame for a signal box, 18-28 levers, for avatar operation'. In that case the crossing location code must be the same as the location code of the lever frame.
The second name element must be one of 4 keywords that identified the type of kit component: 'crossing control','road-barrier','ped-gate','light'. A boom and a road gate pair are classed as a 'road-barrier'.
There may be more than one crossing at a location, so the third name element is an index commencing at '0' for the first instance, and so on.
Kit components other than the crossing controls can have multiple instances for the one crossing. These instances are indexed by a fourth name element, commencing at '0'.
For example, the first and only railway crossing at Hawkesbury River (location code 'HR') has 2 pedestrian gates. The second gate is referenced as 'HR_ped-gate_0_1'.
The user can select from 2 modes of train detection in each direction (DOWN and UP) for setting the state of the crossing: (a) a directional trigger or (b) a driver schedule command or session rule.
Directional triggers (KUID:76656:70010) are used to detect the approach of a train from the Down or Up directions. 1 or 2 triggers are required for each direction, depending on the track layout. Where more than 2 tracks pass over the crossing, use driver command 'Operate railway crossing' instead of triggers to operate the crossing.
For example, the crossing may be located near the Down end of a passing loop for a single main line. The crossing detection point for an Up train is on the main line before the start of the passing loop, and so only a single trigger is required for the Up direction. 1 or 2 triggers could be used in the Down direction, depending on how long the loop is and the speeds at which trains approach.
A directional trigger placed in advance (600m recommended for trains that approach at 60mph or less) of the crossing must point in the direction towards the crossing and be named in the format <location code>_crossing trigger_<crossing index>_down_a and _b or <location code>_crossing trigger_<crossing index>_up_a and _b. Where a direction requires only a single trigger, omit the '_a/b' suffix.
If crossing operation by driver command or session rule is selected, only one track mark for each direction is required and these can be placed on any of the tracks passing over the crossing. See the 'description' information in the driver command 'Operate railway crossing' for track mark naming requirements.
The distance from the tracks at which Carz will stop when the crossing is closed can be extended beyond the ends of the crossing's fixed road by deployment of 1 or 2 crossing slaves. See the 'decription' information in asset 'NSWGR railway crossing slave' for details.
Once all the kit components to be controlled by an instance of this crossing control asset have been placed on a route and named correctly, open the Properties editor of the crossing control instance and enter the quantities of each type of kit component.
Тип: Переезд