A railway crossing employed by NSWGR in the mid 20th century. This asset represents the crossing railway track and road and has the configurable control script for the crossing.
Model based on a level crossing in operation at Hawkesbury River, NSW in the 1950s.
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
20386 - NSWGR railway crossing pedestrian gate, lefthand
20387 - NSWGR railway crossing pedestrian gate, righthand
20388 - NSWGR railway crossing warning light, post mount, red flash
20389 - NSWGR railway crossing control, single track
20390 - NSWGR railway crossing control, double track, 12ft spacing
20391 - NSWGR railway crossing pedestrian boards, single track
20392 - NSWGR railway crossing pedestrian boards, double track, 12ft spacing
60013 - Operate railway crossing (driver command)
Also important for the kit's operation is KUID:76656:70010 'Directional Trigger'.
Remote control of the crossing using a lever frame is possible using KUID:368725:90030 'NSWGR mechanical lever frame for a signal box, 18-28 levers, for avatar operation'.
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, but if crossing protection signals (see below) are to be selected then the crossing location code must be the same as the location code for the local signals.
The second name element must be one of 4 keywords that identified the type of kit component: 'crossing control','boom','ped-gate','light'.
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 directional trigger or a driver schedule command.
A directional trigger (KUID:76656:70010) 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>_crossingtrigger_<crossing index>_down or <location code>_crossing trigger_<crossing index>_up.
The crossing can be protected by a signal in each direction (DOWN and UP). These signals must be close to the crossing to stop trains just before they traverse the crossing. When the crossing gates are open to road traffic, the crossing script forces the protecting signals to the STOP state.
As mentioned above, the location codes for the crossing and the signals must be the same. In the crossing-control asset's properties editor the user may elect to select from a list a protection signal in neither, either or both the DOWN and UP directions.
Тип: Переезд