Bugs noticed

- Also, a red signal will approach lock when the route is cancelled from it when a train has just passed it (the TC ahead of the signal is occupied). Why is this?

Don't know if its true to real life but seeing 120 seconds approach locking platform 3 (signal 71) to either signal 75 on the UPL or signal 25 on the up main without a train in section.

peterb in post 96575 said:

- Also, a red signal will approach lock when the route is cancelled from it when a train has just passed it (the TC ahead of the signal is occupied). Why is this?

Just this for the moment - this is correct. You'll notice the route drops away anyway a couple of seconds after the first TC clears. It was a recent change to correct a long standing (but unnoticeable to most but the most pedantic) issue with approach locking.

GeoffM in post 96588 said:

peterb in post 96575 said:

- Also, a red signal will approach lock when the route is cancelled from it when a train has just passed it (the TC ahead of the signal is occupied). Why is this?

Just this for the moment - this is correct. You'll notice the route drops away anyway a couple of seconds after the first TC clears. It was a recent change to correct a long standing (but unnoticeable to most but the most pedantic) issue with approach locking.

Was previous practice not prototypical then?

Here's a few issues I've noticed while playing Oxford in 2009 era - so can't say if they extend to other eras too.

- LC locations - I asked callers to call back when a train passes. At Islip, I got an 'oi' after an up train had apparently passed the crossing. In the down direction I had a train 'pass' Islip LC before arriving at the station. I think I also recall someone at Manor Farm calling back when the down train in question was passing Kennington loops. It is difficult to test this, so have logged on Mantis for Geoff to check the locations,
but I cannot confirm or deny the presence of a bug at this point. Mantis 17686.
- At one point, DX59 failed. Trains were initially reporting 'standing at a red signal', waiting a rough two mins, then calling back 'still waiting at unlit signal' and the correct phone call.
- Then, DX55 failed, so I had a train standing at SB2211 off sim. But the train never phoned up requesting permission to SPAD which I thought trains would do? When I told the train to SPAD and it got to DX55, it also behaved in the same way as trains at DX59 above. Above two points are a core code trivial bug relating to the message box. When the train phones up the message is correct. Logged as Mantis 17687.
- Trains also don't appear to phone up to report a ACOA which again I thought was customary? I cannot reproduce this.
- Also, a red signal will approach lock when the route is cancelled from it when a train has just passed it (the TC ahead of the signal is occupied). Why is this? Geoff has already covered this in a previous post.
- I had a train reversing (manually - not using the shunt sig) out of the dock at Oxford. When it got to the end of TC TFR, before points 245, the train incorrectly reported that they were set against the train which they weren't. Plus, this also happened for a train occupying TC TCN, approaching points 277B.Confirmed, with TFR, if you reverse P251 then the train will carry on along the Up Main in the Down Direction. The second one is actually down to 278 points, which again when reversed the train will proceed. Logged on Mantis as there are legitimate reasons to talk a train past the signals over the routes that do not work. Mantis 17688
- The TD didn't step from AW2 to 11 in a standard routing when other trains were qued behind off simI cannot reproduce this either.

Re Mantis 17686: this is the message log from when it just happened again at Islip LC. The caller was asked to call back after train 2L02 (2009 up) crossed.

06:01:26 Islip: Now safe to cross [when crosser called back]
06:03:33 Islip: Sorry
06:03:58 2L02 arrived at Islip on time