Three Bridges SX 2019 01 09

Now up to 14:45 with this excellent TT and have an issue with the 0Y70 run-round at Redhill. Loco is sat at GPS T1320 with route set into P2 but the signal never clears. Loco eventually called in and was talked past said signal.

Possible bug ?

Now up to 14:30 with this TT and have 2O40 not moving up to the blocks in P1 at Redhill causing its next working 2V67 to overhang the station starting signal T493. Using F2 and instructing this train to shunt forward clears the problem but why doesn't it move up to the blocks of its own accord ?

A save from 14:20 just before 2O40 arrives at Redhill is also available if anyone needs to try and recreate this issue.

I've also 3S92 duplicated with one entering from Crystal Palace immediately behind the other at 14:40 sim time. There was a similar instance prior to this but I forgot to note the details.

Hilton Junction in post 120876 said:

Firstly I'll apologise if this should have been a stand alone thread.

I'm running the 2019 timetable & have train 6O47 in P1 at Haywards Heath. The loco was signalled ahead of signal T345 per the timetable notes. The Light Engine has detached & is in the spur waiting to run round & re-couple.

Hopefully my save has attached correctly & you will be able to see that I cannot set the route for the engine to run round due to the track remaining set from signal T345 across the points giving access to Down Siding South. I manually cancelled the route from T345 but the track will not drop out to allow me to shunt the engine. I've run the sim forward to 04:37 & the track still will not drop out.

Am I doing something wrong or will this need a fix?

This has already been noted in another thread, the issue is with getting the train to stop in exactly the right place with the loco beyond the platform starter, and the wagons in the platform with enough space for the loco to rejoin at rear. It's a tight move in reality, but SimSig seems to have some variation between runs where the train exactly stops. Some fiddling is being done with the next version of the timetable and sim to ensure this happens reliably.

Be aware, train 6V60 has another timetable similar to the above. At a recent Multiplayer session, 6V60's ARS timetable at Haywards Heath caused the host, consternation as the timetable was not suitable for the length of this train. ARS detached the loco and sent it into the Down Sidings but could not run around. The player at the station was not aware of the situation until it was to late to correct the errors.

Hi, I am loving the simulation Three Bridges.

I have encountered a couple of issues with the 2019 timetable:

One is that most Redhill-Reigate trains are routed into the DPL. I run them through platform 2 subsequently giving me an incorrect platform point in the performance analysis. Could I ask where they are supposed to be routed to avoid this? And why they aren't just booked into platform 2 anyway?

Another issue that I have found is that all trains coming from Lancing to Brighton are running late (4 minutes at Hove) and get more and more delayed while the train behind which is going to London is running on time but eventually being delayed by the service in front. I have played seven and a half hours and not a single one ran on time!

Any Assistance would be greatly appreciated.

Many thanks in advance.

Platform conflict at Gatwick Airport:-
2O54/1V71 use Platform 5 arriving at 2253, for 2318 dep.
1C70 and 5B75 both booked to use the same platform, departing at 2309 and passing at 2316 respectively.

Platform conflict at East Croydon:-
3S92 booked to use Platform 4, arriving at 2304 for 2307 dep.
3Y90 booked to pass Platform 4 at 2305.

Platform conflict at Haywards Heath:-
3Q22 uses Platform 4 between 2318-2357.
3S93 booked to use Platform 4 between 2336-2346.