Dearnby & District V2: Man on a Mission Code v1.0

Dearnby & District V2: Man on a Mission Code v1.0

IMPORTANT: This session and the underlying route utilise assets from the Settle and Carlisle DLC pack. Other dependencies can be downloaded from the DLS.

A session for the Dearnby & District v2.0 Revised (TANE) route, demonstrating the use of:
- Enhanced Interlocking Towers, with Track Circuit Blocks to protect single track sections
- Mission Codes
- Mission Code Stops & Timetables

The asset folder includes two jpeg files, showing how the various Interlocking Towers are interconnected from a Mission Code perspective. You may find these helpful if trying to work out where the next path, for a particular mission code, might be located.

Once in Driver, the green RM button, in the top right menu bar, provides access to a number of run-time monitors. Most are useful primarily for diagnosing problems such as stuck trains.
- The Missioncode manager Requests tab provides path request information relating to the currently selected driver.
- The Towers manager can be used to check the activation status for any configured path.
- The Quick Hud manager allows you to customise or disable the custom HUD.

The session itself is not intended to be 100 percent prototypical, but utilises largely a combination of elements from the earlier 1960s and Trainspotter sessions created by Lataxe and Neville_Hill, for versions 1 and 2 of the Dearnby & District route. The primary difference is that all major pathing is controlled explicitly via the EITs and driver Mission Codes, with all diamond crossings protected using EIT exclusive sets.

There are plenty of AI trains to ride along with, and the session includes an optional shunting and driving task. Hitching a ride on the aircraft departing from Ullsmere and St Bennet airfields is a good way to familiarise yourself with the route layout.

Goods and passenger services will run between portals at scheduled intervals, with the stopping passenger trains running according to their assigned timetables. There are also some passenger routes operating point to point. Just like in the real world (in the UK at least), trains may not always keep to their timetables, depending on what signalling hold-ups they might encounter.

Both an excursion train and a commuter service operate on the single track Narrow Gauge line between Dearnby and Dearne on Sea Docks, and a miniature railway runs along the sea front at Badgercombe.

For anyone wanting to participate more actively, there is an optional General Goods delivery task, which should take around 1 to 1.5 hours to complete:

- Seek out driver Dave in the BR ex GWR 7200 class locomotive, located near to the Frowhill South signal box.
- Begin driving forward and you will receive your orders.

There is no heavy hand-holding, point scoring or penalising, and how you choose to complete the tasks, and at what pace, is entirely up to you. Do, however, keep off the main lines when performing tasks within the yards and obey all signals. The only exception is when passing a red signal in order to access a yard track occupied by another stationary consist.

Loading / unloading of goods can be performed using the trains tab properties for each wagon, or by simply issuing an Instantload / InstantUnload driver command. Of course, the real pros out there will always ensure that the brake van is located at the rear of the consist, with its lamps set appropriately, before entering a main line.

If an AI-controlled train appears to be stuck, and having first checked for anything occupying the track ahead of it, use the Mission Code Manager viewer to check for any pending path requests. If there are none, it may be that the MC follow path processing has failed. You should be able to get the train moving again by either clicking on the driver's first pending command (typically of the form Autodrive....) or by inserting a ITMCAssignNextPath driver command.

There are a few driverless locomotives in various locations on the route, together with some wagons and coaches. Away from the main lines, you should be able to control junctions manually o

Dearnby & District V2: Man on a Mission Code v1.0
• config.txt 130.49KB
• interlocking towers (main lines).jpg 80.97KB
• interlocking towers (narrow gauge).jpg 38.90KB
• moamc1.jpg 362.67KB
• moamc2.jpg 302.32KB
• moamc3.jpg 321.24KB
• profile.amd 24.29KB
• profile.dat 1.15MB
• profile.lyr 28 bytes
• profile.not 24.70KB
• profile_-10_4.obs 33.71KB
• profile_-10_4.vtx 350 bytes
• profile_-11_4.obs 13.49KB
• profile_-11_4.trk 28 bytes
• profile_-11_4.vtx 198 bytes
• profile_-12_4.obs 5.76KB
• profile_-1_-2.vtx 20 bytes
• profile_-1_-7.vtx 20 bytes
• profile_-1_-8.vtx 20 bytes
• profile_-1_0.obs 20 bytes
• profile_-1_0.trk 20 bytes
• profile_-1_0.vtx 20 bytes
• profile_-1_1.obs 20 bytes
• profile_-1_4.obs 23.76KB
• profile_-1_4.trk 28 bytes
• profile_-1_4.vtx 118 bytes
• profile_-1_5.obs 48.83KB
• profile_-1_5.trk 20 bytes
• profile_-1_5.vtx 320 bytes
• profile_-1_6.obs 28 bytes
• profile_-1_7.trk 20 bytes
• profile_-1_7.vtx 20 bytes
• profile_-2_3.vtx 20 bytes
• profile_-2_4.obs 5.92KB
• profile_-2_4.trk 28 bytes
• profile_-2_4.vtx 308 bytes
• profile_-2_5.obs 66.87KB
• profile_-2_5.trk 28 bytes
• profile_-2_5.vtx 990 bytes
• profile_-3_4.obs 41.26KB
• profile_-3_4.trk 20 bytes
• profile_-3_4.vtx 660 bytes
• profile_-3_5.obs 18.03KB
• profile_-3_5.trk 20 bytes
• profile_-3_5.vtx 370 bytes
• profile_-3_6.obs 28 bytes
• profile_-4_-1.trk 20 bytes
• profile_-4_-1.vtx 20 bytes
• profile_-4_-2.vtx 20 bytes
• profile_-4_3.vtx 20 bytes
• profile_-4_4.obs 59.13KB
• profile_-4_4.trk 20 bytes
• profile_-4_4.vtx 650 bytes
• profile_-4_5.obs 117.59KB
• profile_-4_5.trk 28 bytes
• profile_-4_5.vtx 860 bytes
• profile_-4_6.obs 28 bytes
• profile_-4_6.vtx 20 bytes
• profile_-5_-1.trk 20 bytes
• profile_-5_-1.vtx 20 bytes
• profile_-5_-10.vtx 20 bytes
• profile_-5_-2.trk 20 bytes
• profile_-5_-2.vtx 20 bytes
• profile_-5_-3.trk 20 bytes
• profile_-5_-3.vtx 20 bytes
• profile_-5_-4.vtx 20 bytes
• profile_-5_-5.vtx 20 bytes
• profile_-5_-6.trk 20 bytes
• profile_-5_-6.vtx 20 bytes
• profile_-5_-7.vtx 20 bytes
• profile_-5_-8.trk 20 bytes
• profile_-5_-8.vtx 20 bytes
• profile_-5_-9.trk 20 bytes
• profile_-5_-9.vtx 20 bytes
• profile_-5_0.vtx 20 bytes
• profile_-5_1.trk 20 bytes
• profile_-5_1.vtx 20 bytes
• profile_-5_2.vtx 20 bytes
• profile_-5_3.trk 20 bytes
• profile_-5_3.vtx 20 bytes
• profile_-5_4.obs 2.76KB
• profile_-5_4.trk 28 bytes
• profile_-5_4.vtx 118 bytes
• profile_-5_5.obs 23.52KB
• profile_-5_5.trk 28 bytes
• profile_-5_5.vtx 390 bytes
• profile_-5_6.trk 20 bytes
• profile_-5_6.vtx 20 bytes
• profile_-6_-2.trk 20 bytes
• profile_-6_-2.vtx 20 bytes
• profile_-6_2.obs 20 bytes
• profile_-6_2.trk 20 bytes
• profile_-6_2.vtx 20 bytes
• profile_-6_3.vtx 20 bytes
• profile_-6_4.obs 2.25KB
• profile_-6_4.trk 20 bytes
• profile_-6_4.vtx 290 bytes
• profile_-6_5.obs 6.07KB
• profile_-6_5.trk 20 bytes
• profile_-6_5.vtx 540 bytes
• profile_-6_6.obs 28 bytes
• profile_-7_2.obs 20 bytes
• profile_-7_2.trk 20 bytes
• profile_-7_2.vtx 20 bytes
• profile_-7_3.obs 20 bytes
• profile_-7_4.obs 181.34KB
• profile_-7_4.trk 28 bytes
• profile_-7_4.vtx 1.05KB
• profile_-7_5.obs 28 bytes
• profile_-7_5.trk 20 bytes
• profile_-8_2.obs 20 bytes
• profile_-8_2.trk 20 bytes
• profile_-8_2.vtx 20 bytes
• profile_-8_3.obs 20 bytes
• profile_-8_4.obs 7.39KB
• profile_-8_4.trk 20 bytes
• profile_-8_4.vtx 330 bytes
• profile_-8_5.obs 20 bytes
• profile_-9_4.obs 25.14KB
• profile_-9_4.trk 28 bytes
• profile_-9_4.vtx 128 bytes
• profile_0_-1.obs 74.94KB
• profile_0_-1.trk 28 bytes
• profile_0_-1.vtx 1.46KB
• profile_0_-2.obs 57.05KB
• profile_0_-2.trk 28 bytes
• profile_0_-2.vtx 1.45KB
• profile_0_-3.obs 11.65KB
• profile_0_-3.trk 28 bytes
• profile_0_-3.vtx 790 bytes
• profile_0_-4.obs 88.51KB
• profile_0_-4.trk 28 bytes
• profile_0_-4.vtx 1.31KB
• profile_0_-5.obs 52.04KB
• profile_0_-5.trk 28 bytes
• profile_0_-5.vtx 890 bytes
• profile_0_-6.obs 52.18KB
• profile_0_-6.trk 28 bytes
• profile_0_-6.vtx 1.19KB
• profile_0_-7.obs 12.45KB
• profile_0_-7.trk 28 bytes
• profile_0_-7.vtx 328 bytes
• profile_0_-8.obs 8.88KB
• profile_0_-8.trk 20 bytes
• profile_0_-8.vtx 20 bytes
• profile_0_0.obs 45.15KB
• profile_0_0.trk 28 bytes
• profile_0_0.vtx 610 bytes
• profile_0_1.obs 84.76KB
• profile_0_1.trk 28 bytes
• profile_0_1.vtx 940 bytes
• profile_0_2.obs 18.96KB
• profile_0_2.trk 28 bytes
• profile_0_2.vtx 320 bytes
• profile_0_3.obs 5.46KB
• profile_0_3.trk 20 bytes
• profile_0_3.vtx 88 bytes
• profile_0_4.obs 42.77KB
• profile_0_4.trk 28 bytes
• profile_0_4.vtx 4.68KB
• profile_0_5.obs 28.90KB
• profile_0_5.trk 20 bytes
• profile_0_5.vtx 12.36KB
• profile_0_6.obs 264.71KB
• profile_0_6.trk 28 bytes
• profile_0_6.vtx 2.21KB
• profile_0_7.obs 131.31KB
• profile_0_7.trk 28 bytes
• profile_0_7.vtx 3.26KB
• profile_0_8.obs 28 bytes
• profile_0_8.vtx 20 bytes
• profile_1_-1.obs 20 bytes
• profile_1_-2.obs 28 bytes
• profile_1_-3.obs 20 bytes
• profile_1_-4.obs 28 bytes
• profile_1_-5.obs 20 bytes
• profile_1_-6.obs 20 bytes
• profile_1_-7.obs 20 bytes
• profile_1_0.obs 28 bytes
• profile_1_0.trk 20 bytes
• profile_1_0.vtx 20 bytes
• profile_1_1.obs 14.75KB
• profile_1_1.trk 28 bytes
• profile_1_1.vtx 68 bytes
• profile_1_10.trk 20 bytes
• profile_1_10.vtx 20 bytes
• profile_1_2.obs 74 bytes
• profile_1_2.trk 20 bytes
• profile_1_2.vtx 222 bytes
• profile_1_3.obs 166 bytes
• profile_1_3.trk 20 bytes
• profile_1_3.vtx 222 bytes
• profile_1_4.obs 134 bytes
• profile_1_4.trk 20 bytes
• profile_1_4.vtx 20 bytes
• profile_1_5.obs 149 bytes
• profile_1_5.trk 20 bytes
• profile_1_5.vtx 222 bytes
• profile_1_6.obs 5.58KB
• profile_1_6.trk 28 bytes
• profile_1_6.vtx 832 bytes
• profile_1_7.obs 570 bytes
• profile_1_7.trk 20 bytes
• profile_1_7.vtx 20 bytes
• profile_1_8.obs 28 bytes
• profile_1_9.trk 20 bytes
• profile_1_9.vtx 20 bytes
• profile_2_-11.trk 20 bytes
• profile_2_-11.vtx 20 bytes
• profile_2_1.obs 28 bytes
• profile_2_1.trk 20 bytes
• profile_2_1.vtx 222 bytes
• profile_2_10.vtx 20 bytes
• profile_2_2.obs 20 bytes
• profile_2_2.trk 20 bytes
• profile_2_2.vtx 20 bytes
• profile_2_3.obs 28 bytes
• profile_2_3.trk 20 bytes
• profile_2_3.vtx 222 bytes
• profile_2_4.obs 74 bytes
• profile_2_4.trk 20 bytes
• profile_2_4.vtx 20 bytes
• profile_2_5.obs 20 bytes
• profile_2_5.trk 20 bytes
• profile_2_6.obs 58 bytes
• profile_2_7.obs 58 bytes
• profile_2_7.vtx 20 bytes
• profile_3_-11.trk 20 bytes
• profile_3_-11.vtx 20 bytes
• profile_3_10.trk 20 bytes
• profile_3_10.vtx 20 bytes
• profile_5_1.obs 20 bytes
• profile_7_15.trk 20 bytes
• profile_7_15.vtx 20 bytes
• profile_8_14.trk 20 bytes
• profile_8_14.vtx 20 bytes
• profile_8_15.vtx 20 bytes
• profile_index.obs 520 bytes
• profile_index.rlr 16 bytes
• profile_index.trk 292 bytes
• profile_index.vtx 516 bytes
• thumbnail.jpg 128.43KB