Doncaster Station FAQ

Just to ask, can you check if the overlap from D308 to D298 on the up Scunthorpe is a track section too long. I'm sure you could run trains up to D298 while trains were arriving into P1 & P3

I can confirm that it is possible to signal a train from D308 to D298 and signal a train into 1 or 3 at the same time currently in the PSB.

francisoldfield in post 154450 said:

Possible bug with 5Z11/12

5Z11 arrived on time and became 5Z12 but despite F2 list showing it departing at 1127 it won't move with the road or anything. It is now 1140 and I haven't had a call saying it will be delayed. Not sure why it won't go.

I have taken a look at your save, the departure time is listed as 1227.

I’m currently working my way through the 2019 timetable and have come across a slight problem shortly after 10.15.
4R79 has recently left the Down Decoy sidings and is heading for Adwick via the DG line.

According to the train’s tt it goes via WS1. However, if I set the route into WS1 from the train's current location (see screenshot), I can’t get to the DG line. I'm going to alter the tt and then set the route for the train via WS2.
But is this me misreading the timetable or is the tt incorrect?

I’ve had a look through the FAQ posts and can’t see anything reported about this.
.....

The station Freight Roads DG & 2WG are alternatives and can be swapped without penalty or need to edit the schedule.

A number of trains that leave platform 1 and head towards Retford, according to the tt, are to be sent via the ESL and not the Down Fast, even though there's no sign of a train approaching Doncaster from the North.

Is there a particular reason for this.

Just wondered.

bugsy in post 154512 said:

A number of trains that leave platform 1 and head towards Retford, according to the tt, are to be sent via the ESL and not the Down Fast, even though there's no sign of a train approaching Doncaster from the North.

Is there a particular reason for this.

Just wondered.

In the 2019 timetable there a number of services which are overtaken at Doncaster by non stoppers, and use the ESL which you've probably already encountered. The likelyhood is that the trains you've questioned were planned that way for consistency to maintain the timetable pattern, or because it leaves an available non stop path in, Whether utilised or not.

If nothing else is about, there's nothing to stop you running them FL out of Doncaster

2W34 in post 154356 said:

Just a quick one, does anyone know the origin of how the “Decoy” yards ended up with that name? Anything to do with confusing the Luftwaffe in WW2 perhaps?

The area was built on marshland (Carrs - hence potteric Carr, black carr, Carr loco, loversall Carr, Carr hill and Bessecarr). The gentry went hunting for ducks and similar game in Decoys (hides) which gave the area its name. The yards predate both world wars

I'm playing the 2019 TT, chained to Donacaster North. 4M25 has entered from Shaftholme. In the North sim, it shows as running through Donacster UF line as its final location. However on entering Doncaster Station sim, the Doncaster location is skipped and the next location is Hexthorpe Jn with no routing information or passing time for Doncaster shown. Through the TT editor I can see the train does indeed match the North sim and agrees on it running through the UF but the sim has somehow skipped it before the train has even reached D814 signal.

Using the 2019 TT in a 'normal' scenario with lots of freight entering early. None of it is waiting booked time anywhere with TTs stepping up on arrival - this is happening at Doncaster station and various junctions, subsequently no call is made with the option to 'await booked time'.

The junction speed at loversall carr in the UP direction seems to be incorrect. It should be 70 all the way along the UP East Slow and out of Loversall carr at 70mph also. Trains are slowing to 40.

Thanks.

1A70 has just received an ACOA in the above circumstance - save available from afterwards (time of screenshot), or a snapshot from approx four minutes earlier (0930 for my reference). My suspicion is that having cleared the crossing from D274, 6D76 has caused it but I couldn't say for certain.

Additionally, 4V78 has the same issue in the 2019 TT as I reported earlier this week for 4M25.