Dearnby & District V2.0 Revised Trainspotter Session

Dearnby & District V2.0 Revised Trainspotter Session

The original, amazingly detailed route of Dearnby & DISTRICT V2 was by neville_hill (<kuid:304444:101412>). This was revised by lataxe (Ludd) (<kuid:497137:102088>) to make it suitable for EIT session builders IN TANE. My version of the route (<kuid2:186943:103050:1>) is identical to that of Neville Hill and Lataxe, except that mine works with TRS19 build 111951 (NOT earlier builds).

Dearnby & District Version 2 Revised is a small but complex fictional route containing many stations, yards, docks and other facilities, set in the UK Western Region in the 1950-60s. It contains some fast mainline, both two and four track, as well as single track branch lines. There are also: a 2ft narrow gauge line and 15inch gauge miniature railway.

There are also two airfields providing respectively: a short but fast flight around Dearnby; a slower aerial tour of the whole route. There is also a ferry running from Dearne-on-Sea to Badgercombe Bay, with attendant rail links.

The revised versions of the route are more or less the same as the original Version 2 D&D route but are configured for session builders, with no consists other than a very few scenery items in the route layer; and with the various portals into and out of the route unpopulated. This provides a blank canvas for session builders.

The route may be entered and exited via various portals.

A schematic diagram of the route is available as a pdf file at https://drive.google.com/file/d/1GujDCBIQ9DbPLIUpoEMdQJMfmDT_fTai/view?usp=sharing

This new session, which is for build 119531 (not earlier builds), is derived very closely from the Trainspotter session <kuid:304444:101428> by Neville Hill for the original route. The main difference is that the main-line trains in this session are controlled by the powerful Enhanced Interlocking Towers / Mission Codes system developed by Pierre Guy. Diamond and other track crossings are protected using the Exclusive Sets feature of EIT; and also where lines ahead are clear trains can get the junctions set as they need them and the signals cleared earlier than usually happens with Trainz AI drivers.

In this session each of the 6 emitting portals has around 6 different trains which it emits in order, at 9 minute intervals. After all trains have been emitted by a portal the cycle repeats. After a train has been emitted it proceeds on its way, according to the commands specified for it in Quick Portal Manager, until consumed by a receiving portal. As in Neville’s session there are also 7 main-line trains which are present on the layout at the start and are never consumed, but continue indefinitely in their own circular route.

It is perfectly possible to use the EIT/MC system in different ways. For this session I have chosen to assign sufficient mission codes to a train to take it to its next stop – usually at a station platform. Once it has done whatever it needs to do there (e.g. unloading/loading passengers) it is assigned the mission codes needed to take it to its next stop. For example, a train which doesn’t stop at the next station (A) but does stop at the one after (B) would have two mission codes, e.g. “Station A up platform” and “Station B Platform 3 stop” for that leg of its journey. The paths a train needs are automatically assigned to it by EIT based on the train’s current mission codes, using the follow-on path facility.

This is not an interactive session, but of course you can hop on board any train, or just watch what’s going on with the roaming camera. To keep track of trains (or rather drivers) and their interactions with paths it is helpful to use the monitor provided with EIT: Tools menu (spanner)/Run time monitors/View towers manager/trains.

Because of the complexity of the underlying code you may very occasionally experience a glitch, normally only after the session has been running for a few hours. Glitches usually show up as either

* a train is stuck at a stop signal and is not waiting for the next path which it needs to continue its journey. If you manually give it an ITMCAssignNe

Dearnby & District V2.0 Revised Trainspotter Session
• config.txt 58.46KB
• profile.amd 36.94KB
• profile.dat 753.80KB
• profile.lyr 32 bytes
• profile.not 7.06KB
• profile_-10_4.obs 33.92KB
• profile_-10_4.trk 28 bytes
• profile_-10_4.vtx 148 bytes
• profile_-10_5.obs 28 bytes
• profile_-10_5.vtx 28 bytes
• profile_-11_4.obs 11.63KB
• profile_-11_4.trk 28 bytes
• profile_-11_4.vtx 378 bytes
• profile_-11_5.obs 28 bytes
• profile_-12_4.obs 3.99KB
• profile_-12_4.trk 28 bytes
• profile_-12_4.vtx 28 bytes
• profile_-12_5.obs 28 bytes
• profile_-1_-2.vtx 28 bytes
• profile_-1_-7.vtx 28 bytes
• profile_-1_-8.vtx 28 bytes
• profile_-1_0.obs 28 bytes
• profile_-1_0.trk 28 bytes
• profile_-1_0.vtx 28 bytes
• profile_-1_1.obs 28 bytes
• profile_-1_4.obs 19.99KB
• profile_-1_4.trk 28 bytes
• profile_-1_4.vtx 118 bytes
• profile_-1_5.obs 32.25KB
• profile_-1_5.trk 28 bytes
• profile_-1_5.vtx 118 bytes
• profile_-1_6.obs 28 bytes
• profile_-1_7.trk 28 bytes
• profile_-1_7.vtx 28 bytes
• profile_-2_3.vtx 28 bytes
• profile_-2_4.obs 5.72KB
• profile_-2_4.trk 28 bytes
• profile_-2_4.vtx 308 bytes
• profile_-2_5.obs 34.03KB
• profile_-2_5.trk 28 bytes
• profile_-2_5.vtx 218 bytes
• profile_-2_6.obs 28 bytes
• profile_-3_4.obs 47.53KB
• profile_-3_4.trk 28 bytes
• profile_-3_4.vtx 318 bytes
• profile_-3_5.obs 14.61KB
• profile_-3_5.trk 28 bytes
• profile_-3_5.vtx 168 bytes
• profile_-3_6.obs 28 bytes
• profile_-4_-1.trk 28 bytes
• profile_-4_-1.vtx 28 bytes
• profile_-4_-2.vtx 28 bytes
• profile_-4_3.vtx 28 bytes
• profile_-4_4.obs 60.51KB
• profile_-4_4.trk 28 bytes
• profile_-4_4.vtx 258 bytes
• profile_-4_5.obs 36.25KB
• profile_-4_5.trk 28 bytes
• profile_-4_5.vtx 468 bytes
• profile_-4_6.obs 28 bytes
• profile_-4_6.vtx 28 bytes
• profile_-5_-1.trk 28 bytes
• profile_-5_-1.vtx 28 bytes
• profile_-5_-10.vtx 28 bytes
• profile_-5_-2.trk 28 bytes
• profile_-5_-2.vtx 28 bytes
• profile_-5_-3.trk 28 bytes
• profile_-5_-3.vtx 28 bytes
• profile_-5_-4.vtx 28 bytes
• profile_-5_-5.vtx 28 bytes
• profile_-5_-6.trk 28 bytes
• profile_-5_-6.vtx 28 bytes
• profile_-5_-7.vtx 28 bytes
• profile_-5_-8.trk 28 bytes
• profile_-5_-8.vtx 28 bytes
• profile_-5_-9.trk 28 bytes
• profile_-5_-9.vtx 28 bytes
• profile_-5_0.vtx 28 bytes
• profile_-5_1.trk 28 bytes
• profile_-5_1.vtx 28 bytes
• profile_-5_2.vtx 28 bytes
• profile_-5_3.trk 28 bytes
• profile_-5_3.vtx 28 bytes
• profile_-5_4.obs 2.74KB
• profile_-5_4.rlr 28 bytes
• profile_-5_4.trk 28 bytes
• profile_-5_4.vtx 118 bytes
• profile_-5_5.obs 16.65KB
• profile_-5_5.trk 28 bytes
• profile_-5_5.vtx 188 bytes
• profile_-5_6.obs 28 bytes
• profile_-5_6.trk 28 bytes
• profile_-5_6.vtx 28 bytes
• profile_-6_-2.trk 28 bytes
• profile_-6_-2.vtx 28 bytes
• profile_-6_2.obs 28 bytes
• profile_-6_2.trk 28 bytes
• profile_-6_2.vtx 28 bytes
• profile_-6_3.obs 28 bytes
• profile_-6_3.vtx 28 bytes
• profile_-6_4.obs 1.59KB
• profile_-6_4.trk 28 bytes
• profile_-6_4.vtx 88 bytes
• profile_-6_5.obs 4.14KB
• profile_-6_5.trk 28 bytes
• profile_-6_5.vtx 148 bytes
• profile_-6_6.obs 28 bytes
• profile_-7_2.obs 28 bytes
• profile_-7_2.trk 28 bytes
• profile_-7_2.vtx 28 bytes
• profile_-7_3.obs 28 bytes
• profile_-7_4.obs 120.44KB
• profile_-7_4.rlr 28 bytes
• profile_-7_4.trk 28 bytes
• profile_-7_4.vtx 688 bytes
• profile_-7_5.obs 28 bytes
• profile_-7_5.trk 28 bytes
• profile_-8_2.obs 28 bytes
• profile_-8_2.trk 28 bytes
• profile_-8_2.vtx 28 bytes
• profile_-8_3.obs 28 bytes
• profile_-8_4.obs 6.99KB
• profile_-8_4.trk 28 bytes
• profile_-8_4.vtx 128 bytes
• profile_-8_5.obs 28 bytes
• profile_-9_4.obs 36.88KB
• profile_-9_4.trk 28 bytes
• profile_-9_4.vtx 128 bytes
• profile_-9_5.obs 28 bytes
• profile_0_-1.obs 76.04KB
• profile_0_-1.trk 28 bytes
• profile_0_-1.vtx 318 bytes
• profile_0_-2.obs 76.76KB
• profile_0_-2.trk 28 bytes
• profile_0_-2.vtx 318 bytes
• profile_0_-3.obs 3.63KB
• profile_0_-3.trk 28 bytes
• profile_0_-3.vtx 208 bytes
• profile_0_-4.obs 82.37KB
• profile_0_-4.trk 28 bytes
• profile_0_-4.vtx 368 bytes
• profile_0_-5.obs 36.58KB
• profile_0_-5.trk 28 bytes
• profile_0_-5.vtx 308 bytes
• profile_0_-6.obs 79.26KB
• profile_0_-6.trk 28 bytes
• profile_0_-6.vtx 448 bytes
• profile_0_-7.obs 27.11KB
• profile_0_-7.trk 28 bytes
• profile_0_-7.vtx 328 bytes
• profile_0_-8.obs 7.39KB
• profile_0_-8.trk 28 bytes
• profile_0_-8.vtx 28 bytes
• profile_0_-9.obs 28 bytes
• profile_0_-9.vtx 28 bytes
• profile_0_0.obs 7.48KB
• profile_0_0.rlr 28 bytes
• profile_0_0.trk 28 bytes
• profile_0_0.vtx 218 bytes
• profile_0_1.obs 64.33KB
• profile_0_1.trk 28 bytes
• profile_0_1.vtx 168 bytes
• profile_0_2.obs 5.05KB
• profile_0_2.trk 28 bytes
• profile_0_2.vtx 118 bytes
• profile_0_3.obs 11.34KB
• profile_0_3.trk 28 bytes
• profile_0_3.vtx 88 bytes
• profile_0_4.obs 48.15KB
• profile_0_4.trk 28 bytes
• profile_0_4.vtx 188 bytes
• profile_0_5.obs 14.21KB
• profile_0_5.trk 28 bytes
• profile_0_5.vtx 588 bytes
• profile_0_6.obs 180.88KB
• profile_0_6.trk 28 bytes
• profile_0_6.vtx 1.25KB
• profile_0_7.obs 90.46KB
• profile_0_7.trk 28 bytes
• profile_0_7.vtx 708 bytes
• profile_0_8.obs 28 bytes
• profile_0_8.vtx 28 bytes
• profile_1_-1.obs 28 bytes
• profile_1_-2.obs 28 bytes
• profile_1_-3.obs 28 bytes
• profile_1_-4.obs 28 bytes
• profile_1_-5.obs 28 bytes
• profile_1_-6.obs 28 bytes
• profile_1_-7.obs 28 bytes
• profile_1_-8.obs 28 bytes
• profile_1_-8.trk 28 bytes
• profile_1_-8.vtx 28 bytes
• profile_1_0.obs 28 bytes
• profile_1_0.trk 28 bytes
• profile_1_0.vtx 28 bytes
• profile_1_1.obs 32.70KB
• profile_1_1.trk 28 bytes
• profile_1_1.vtx 68 bytes
• profile_1_10.trk 28 bytes
• profile_1_10.vtx 28 bytes
• profile_1_2.obs 74 bytes
• profile_1_2.trk 28 bytes
• profile_1_2.vtx 28 bytes
• profile_1_3.obs 166 bytes
• profile_1_3.trk 28 bytes
• profile_1_3.vtx 38 bytes
• profile_1_4.obs 134 bytes
• profile_1_4.trk 28 bytes
• profile_1_4.vtx 28 bytes
• profile_1_5.obs 149 bytes
• profile_1_5.trk 28 bytes
• profile_1_5.vtx 28 bytes
• profile_1_6.obs 2.50KB
• profile_1_6.trk 28 bytes
• profile_1_6.vtx 48 bytes
• profile_1_7.obs 524 bytes
• profile_1_7.trk 28 bytes
• profile_1_7.vtx 28 bytes
• profile_1_9.trk 28 bytes
• profile_1_9.vtx 28 bytes
• profile_2_-11.trk 28 bytes
• profile_2_-11.vtx 28 bytes
• profile_2_1.obs 28 bytes
• profile_2_1.trk 28 bytes
• profile_2_1.vtx 38 bytes
• profile_2_10.vtx 28 bytes
• profile_2_2.obs 28 bytes
• profile_2_2.trk 28 bytes
• profile_2_2.vtx 28 bytes
• profile_2_3.obs 28 bytes
• profile_2_3.trk 28 bytes
• profile_2_3.vtx 28 bytes
• profile_2_4.obs 74 bytes
• profile_2_4.trk 28 bytes
• profile_2_4.vtx 28 bytes
• profile_2_5.obs 28 bytes
• profile_2_5.trk 28 bytes
• profile_2_6.obs 58 bytes
• profile_2_7.obs 88 bytes
• profile_2_7.vtx 28 bytes
• profile_3_-11.trk 28 bytes
• profile_3_-11.vtx 28 bytes
• profile_3_10.trk 28 bytes
• profile_3_10.vtx 28 bytes
• profile_5_1.obs 28 bytes
• profile_7_15.trk 28 bytes
• profile_7_15.vtx 28 bytes
• profile_8_14.trk 28 bytes
• profile_8_14.vtx 28 bytes
• profile_8_15.vtx 28 bytes
• profile_index.obs 596 bytes
• profile_index.rlr 31 bytes
• profile_index.trk 376 bytes
• profile_index.vtx 466 bytes
• thumbnail.jpg 128.43KB