Gameplay Niddertalbahn Modern Timetable - Released

Released
I am happy to say that the timetable is finally released! It's available to download here:
https://www.trainsimcommunity.com/m...reations/i4165-niddertalbahn-modern-timetable
Please leave any feedback or suggestions in this thread and I'll do my best to implement what I can.

Original:
I thought a good route to get a hang of the timetable editor would be Niddertalbahn. I'm getting started on creating a modern day (2022-23) timetable, I intend to use the 642 when that gets released but until then the 628 will be placeholder. I aim to get AI traffic into the timetable, Bad Vilbel will be the biggest challenge as it has regular S-Bahn, regional and IC/ICE services calling and passing through. Intially, the focus will be getting all the player services in and making sure that works.

I've got my first service in the timetable but already I'm having issues after a simulation whereby it's stuck at Eichen.

The other thing I'm unsure of is where trains are stabled overnight? There's about 5 services that start their day at Stockheim but I'm guessing the stock isn't stabled there overnight, does anyone know where the stock comes from in the morning?

 

I'm very confused as to why the train is getting stuck at Eichen, the path is set for the train and the instruction is set up the same as all the rest. In the spoiler is the relevent part of the log file.

Spoiler: Log file text

TS2Editor: TOD: +04:23:41.250, Progress: 7.10%, Avg Frame Time: 0.41ms, Total Time: +00:00:38, Active Services: 1
TS2: Trigger door lock state 0 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
LogTSWAI: AI has been stopped for 60.049370s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:24:39.700, [TargetSpeedCondition] Stop Arrived at Instruction, [Service] RB 34 (15701) - Stockheim to Bad Vilbel, [Location] Lat: 50.28329, Lon: 8.94316, [CurrentVelocity] 0.00m/s
TS2Dispatcher: Status for service RB 34 (15701) - Stockheim to Bad Vilbel: Acquired (entered) route 3 from FAST_F to FAST_B, Acquired route 0 from FAST_B to FECH_F, Acquired route 1 from FECH_F to FECH_B2, Acquired route 0 from FECH_B2 to FECH_B,
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel completed instruction (LoadUnload) 6 at 2023.10.20-04.25.00
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel started instruction 7 at 2023.10.20-04.25.00
TS2Dispatcher: SetSignalAspect FAST_B from Hp1 to Hp0 (showing Hp1 previously showing Hp0), route ix: 0, Junction(s) Set, occupation count: 1
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 0 (13) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Requesting route 0 at signal FECH_B to signal FHWD_B for service: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 0 (31) on route 0 for signal FECH_B to signal FHWD_B for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 1 (32) on route 0 for signal FECH_B to signal FHWD_B for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Assigning route 0 at signal FECH_B to signal FHWD_B for service: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: SetSignalAspect FECH_B from Hp0 to Hp1 (showing Hp0 previously showing Hp1), route ix: 0, Junction(s) Set, occupation count: 0
TS2Dispatcher: SetSignalAspect FECH_B2 from Hp0 to Hp1 (showing Hp0 previously showing Hp1), route ix: 0, Junction(s) Set, occupation count: 0
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 1 (14) on route 0 for signal FAST_B to signal FECH_F
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is departing from marker Altenstadt (Hess) Platform 1 .
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 3 (12) on route 2 for signal FAST_DEx to signal FAST_B
TS2Dispatcher: Releasing Section: 3 (12) on route 2 for signal FAST_DEx to signal FAST_B for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 0 (13) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Releasing route 0 at signal FAST_B to signal FECH_F for service: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Releasing Section: 0 (13) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 2 (15) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 3 (16) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 4 (17) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 1 (14) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Releasing Section: 1 (14) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 3 (16) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Releasing Section: 2 (15) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Releasing Section: 3 (16) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 5 (18) on route 0 for signal FAST_B to signal FECH_F
TS2Editor: TOD: +04:25:56.150, Progress: 7.27%, Avg Frame Time: 0.37ms, Total Time: +00:00:39, Active Services: 1
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 4 (17) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Releasing Section: 4 (17) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Releasing Level Crossing LevelCrossingAltenstadtMain for service RB 34 (15701) - Stockheim to Bad Vilbel. New Acquisition Count: 0
TS2Dispatcher: Level crossing Level Crossing Altenstadt Main @ Lat: 50.28316, Lon: 8.93996 transitioning from state ELevelCrossingState::Closed to state ELevelCrossingState:pening (after 0.996094.2 seconds)
TS2Dispatcher: Level crossing Level Crossing Altenstadt Main @ Lat: 50.28316, Lon: 8.93996 transitioning from state ELevelCrossingState:pening to state ELevelCrossingState:pen (after 2.988281.2 seconds)
TS2Dispatcher: Level crossing LevelCrossingAltenstadtMain reached sleep state. Acqusition count: 0
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is approaching marker Höchst (Nidder) Platform 1 and is stopping there.
TS2Editor: TOD: +04:28:00.250, Progress: 7.42%, Avg Frame Time: 0.40ms, Total Time: +00:00:40, Active Services: 1
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is departing from marker Höchst (Nidder) Platform 1.
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel arrived at instruction 7 at 2023.10.20-04.28.20
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel completed instruction(Go To) 7 at 2023.10.20-04.28.20
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel started instruction 8 at 2023.10.20-04.28.20
TS2: Trigger door lock state 0 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 0 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Trigger door lock state 1 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel completed instruction (LoadUnload) 8 at 2023.10.20-04.29.00
TS2: Service RB 34 (15701) - Stockheim to Bad Vilbel started instruction 9 at 2023.10.20-04.29.00
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is approaching marker Höchst (Nidder) Platform 1 and is passing thru.
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is departing from marker Höchst (Nidder) Platform 1.
TS2Editor: TOD: +04:30:06.850, Progress: 7.58%, Avg Frame Time: 0.39ms, Total Time: +00:00:41, Active Services: 1
LogTS2PassengerInfoSystem: Service RB 34 (15701) - Stockheim to Bad Vilbel is approaching marker Eichen (Nidder) Platform 1 and is stopping there.
TS2Dispatcher: SetSignalAspect FECH_F from Hp1 to Hp0 (showing Hp1 previously showing Hp0), route ix: 1, Junction(s) Set, occupation count: 1
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 0 (19) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Requesting route 2 at signal FHWD_B to signal FHWD_N4 for service: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 0 (33) on route 2 for signal FHWD_B to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 1 (34) on route 2 for signal FHWD_B to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquired Level Crossing LevelCrossingKm194 for service RB 34 (15701) - Stockheim to Bad Vilbel. New Acquisition Count: 1
TS2Dispatcher: Assigning route 1 on (shunt) signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} as part of route 2 on signal: FHWD_B
TS2Dispatcher: Acquiring Section: 0 (35) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 1 (36) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 2 (37) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 3 (38) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 4 (39) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 5 (40) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquiring Section: 6 (41) on route 1 for signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Acquired route 1 at signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for service: RB 34 (15701) - Stockheim to Bad Vilbel setting junctions
TS2Dispatcher: Acquired route 2 at signal FHWD_B to signal FHWD_N4 for service: RB 34 (15701) - Stockheim to Bad Vilbel setting level crossings
TS2Dispatcher: Level crossing Level Crossing Km 19.4 @ Lat: 50.23596, Lon: 8.87754 transitioning from state ELevelCrossingState:pen to state ELevelCrossingState::Warning (after 0.996094.2 seconds)
TS2Dispatcher: Setting junction {1735A9E8-4017-6080-EF8C-5E9A03C16CF4} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Setting junction {9919A379-412E-31FD-DDF5-8DAEABA2995C} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Setting junction {F88A90C1-43B7-22A6-2732-EB89555E0237} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Setting junction {1735A9E8-4017-6080-EF8C-5E9A03C16CF4} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Setting junction {9919A379-412E-31FD-DDF5-8DAEABA2995C} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Setting junction {F88A90C1-43B7-22A6-2732-EB89555E0237} to state 1 for service [RB 34 (15701) - Stockheim to Bad Vilbel] due to route acquisition
TS2Dispatcher: Assigning route 1 at signal {DFB11927-4E50-F154-6C4F-2DA688A6B3BC} to signal FHWD_N4 for services: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: SetSignalAspect from Hp0 to Sh1 (showing Hp0 previously showing Sh1), route ix: 1, Junction(s) Set, occupation count: 0
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 5 (18) on route 0 for signal FAST_B to signal FECH_F
TS2Dispatcher: Releasing Section: 5 (18) on route 0 for signal FAST_B to signal FECH_F for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 1 (20) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Level crossing Level Crossing Km 19.4 @ Lat: 50.23596, Lon: 8.87754 transitioning from state ELevelCrossingState::Warning to state ELevelCrossingState::Closing (after 5.976562.2 seconds)
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 0 (19) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing route 1 at signal FECH_F to signal FECH_B2 for service: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Releasing Section: 0 (19) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 2 (21) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 3 (22) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Level crossing Level Crossing Km 19.4 @ Lat: 50.23596, Lon: 8.87754 transitioning from state ELevelCrossingState::Closing to state ELevelCrossingState::Closed (after 5.976562.2 seconds)
TS2Dispatcher: Level crossing LevelCrossingKm194 reached sleep state. Acqusition count: 1
TS2Dispatcher: Assigning route 2 at signal FHWD_B to signal FHWD_N4 for services: RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: SetSignalAspect FHWD_B from Hp0 to Hp2 (showing Hp0 previously showing Hp2), route ix: 2, Junction(s) Set, occupation count: 0
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 1 (20) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 1 (20) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 4 (23) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 2 (21) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 2 (21) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 3 (22) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 3 (22) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 5 (24) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 6 (25) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 4 (23) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 4 (23) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 5 (24) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 5 (24) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 7 (26) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 6 (25) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 6 (25) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel entered section 8 (27) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Service: RB 34 (15701) - Stockheim to Bad Vilbel exited section 7 (26) on route 1 for signal FECH_F to signal FECH_B2
TS2Dispatcher: Releasing Section: 7 (26) on route 1 for signal FECH_F to signal FECH_B2 for service RB 34 (15701) - Stockheim to Bad Vilbel
TS2Editor: TOD: +04:32:05.150, Progress: 7.73%, Avg Frame Time: 0.42ms, Total Time: +00:00:42, Active Services: 1
LogTSWAI: AI has been stopped for 60.049370s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:32:32.700, [TargetSpeedCondition] Stop Destination, [Service] RB 34 (15701) - Stockheim to Bad Vilbel, [Location] Lat: 50.25572, Lon: 8.91722, [CurrentVelocity] 0.00m/s
TS2Dispatcher: Status for service RB 34 (15701) - Stockheim to Bad Vilbel: Acquired (entered) route 1 from FECH_F to FECH_B2, Acquired route 0 from FECH_B2 to FECH_B, Acquired route 0 from FECH_B to FHWD_B, Acquired route 2 from FHWD_B to FHWD_N4,
LogTSWAI: AI has been stopped for 120.102730s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:33:32.750, [TargetSpeedCondition] Stop Destination, [Service] RB 34 (15701) - Stockheim to Bad Vilbel, [Location] Lat: 50.25572, Lon: 8.91722, [CurrentVelocity] 0.00m/s
TS2Dispatcher: Status for service RB 34 (15701) - Stockheim to Bad Vilbel: Acquired (entered) route 1 from FECH_F to FECH_B2, Acquired route 0 from FECH_B2 to FECH_B, Acquired route 0 from FECH_B to FHWD_B, Acquired route 2 from FHWD_B to FHWD_N4,
LogTSWAI: AI has been stopped for 180.156387s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:34:32.800, [TargetSpeedCondition] Stop Destination, [Service] RB 34 (15701) - Stockheim to Bad Vilbel, [Location] Lat: 50.25572, Lon: 8.91722, [CurrentVelocity] 0.00m/s
TS2Dispatcher: Status for service RB 34 (15701) - Stockheim to Bad Vilbel: Acquired (entered) route 1 from FECH_F to FECH_B2, Acquired route 0 from FECH_B2 to FECH_B, Acquired route 0 from FECH_B to FHWD_B, Acquired route 2 from FHWD_B to FHWD_N4,
TS2Editor: TOD: +04:34:34.900, Progress: 7.92%, Avg Frame Time: 0.33ms, Total Time: +00:00:43, Active Services: 1
LogTSWAI: AI has been stopped for 240.210052s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:35:32.850, [TargetSpeedCondition] Stop Destination, [Service] RB 34 (15701) - Stockheim to Bad Vilbel, [Location] Lat: 50.25572, Lon: 8.91722, [CurrentVelocity] 0.00m/s
TS2Dispatcher: Status for service RB 34 (15701) - Stockheim to Bad Vilbel: Acquired (entered) route 1 from FECH_F to FECH_B2, Acquired route 0 from FECH_B2 to FECH_B, Acquired route 0 from FECH_B to FHWD_B, Acquired route 2 from FHWD_B to FHWD_N4,
LogTSWAI: AI has been stopped for 300.250214s

 

Still struggling to understand why the train is essentially stuck, I've tried removing instructions from the timetable to see if it was a certain station causing issues but the problem just moves elsewhere. Having now relinked everything the train won't even leave the initial station. The log just says the following:
LogTSWAI: AI has been stopped for 240.210052s
LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +04:35:32.850, [TargetSpeedCondition] Stop Destination, [Service] RB 34 (15701) - Stockheim to Bad Vilbel

Does anyone have any ideas what "Stop Destination" means for target speed condition? Any help/suggestions are most welcome.

EDIT - Managed to get the issue sorted by deleting half the instructions and re-adding them. No idea what I managed to do to cause it to do what it did.

 

Sometimes I see services get stuck when the go to condition is set to "overlap" rather than "within" for a platform.

 

The first diagram is now in the timetable and succesfully simulated, once you get the first service set up the process onwards is a lot quicker with being able to copy, paste and then adjust the timings with the propagation tool. I've split the layers up into 245 and 642 operated services, 245 services will be utilizing double 628s until a suitable loco is released (218 or 245) and I'm intially setting 642 services up with 628s but will replace these when the 642 is releasd.

One of the interesting things with the 245 diagrams is they join two together, after morning peak, in Frankfurt and then they'll operate the evening peak RB34/RB48 service to Stockheim and Nidda which split at Bad Vilbel. I've managed to get two diagrams (one of the diagrams is the morning peak service from Nidda, which is AI only) to join in the Frankfurt Portal and then they'll return to Bad Vilbel and split with the respective services going to their destinations. There's two services in the evening which do this, so they'll both be in there.

I'm very happy the editor has been released with timetable tool, it's something I've been wanting to put utilise for a while. Intially, I was planning ECW but thought it would be a little ambitious for a first attempt. Must say that I'm very impressed with how Joe managed to get London - Brighton timetable together and working, figuring out the diagrams for this timetable was time consuming enough!

Couple of images below of the first diagram in the editor and the diagrams I got together in Excel.

 

I've hit a bit of a stumbling block in the timetable now, I've got an issue with a train stopping before the Frankfurt Portal with error of "Stop Off Path", wasn't sure if the portal joins were causing problems but I've removed these and it still gets stuff in the same location. The service with this issue is an AI RB 48 (this later joins one of the other services) from Karben GG Portal which is routed through platform 4 as a via point (for some reason, it sets the direct through as being through platform 3) and then to Frankfurt Portal. This service was previously working so I don't understand why its suddenly stopped working.

 

Managed to fix the issue with the RB 48 AI, I changed the formation from a single 628 to a double 628 at some point and for some reason this broke it. Took me about 2 days to discovered what the issue was, but now I've changed it back to a single 628 it's happy. After a few other changes and trying to figure out how call-on dependency works, I've now got all the 245 diagrams into the timetable. The first 642 diagram is also in, and now I'm working on the second diagram which involves a lot of splitting and joining. Very satisfying but also very frustrating at times!

 

So now all the player services are in the timetable, excluding a few more obscure services, fixed a few issues with splits/joins which cropped up.
A new issue I face now is one of the services which terminates at Bad Vilbel is locking a route up at Stockheim (despite having completed the service and being stabled at Bad Vilbel, the opposite end of the route), preventing any trains entering platform 1. Tried the usual tricks of deleting the service and readding it but no use. Looks like this might be another issue I get stuck on for quite some time. The service locking up the route had previously split in Stockheim, so possibly it's related to that?

Work calls for now, so I'll give it another go tomorrow.

 

All the player services are now in the timetable and simulated. The 628 struggles keeping to the 642 timings so there is a small ripple delay throughout each service as they progress but only by a couple of minutes. Hopefully, once the 642 is out they manage to keep to the timings a bit better but it might just be the case that real life timings are very tight with it being a busy branch. Work has now started on the AI at Bad Vilbel.

 

I'm afraid it's probably not just the 628... The top speed on the route was raised to 80 km/h somewhere between the time that TSW Niddertalbahn is set in and today.

 

That's something I wasn't aware of. Thankfully, the delays don't tend to be more than around 2-5 minutes (fairly good for DB standards) and most of the time they'll recover this with the longer stops at crossover locations.

 

A bit of an update on timetable progress. All the S-bahn services are now in at Bad Vilbel, intially I made up majority 8-car sets and then added some 12-cars in for the peaks as they do in real life (I believe the 8-cars gain an extra unit at Friedberg). Annoyingly, I ended up having more portal issues where the trains were reporting as being off path and locking up the whole timetable. This issue only affected the 12-car sets, so for now I've had to make them all 8-car and maybe in the future I'll see if there's anyway to fix the issue.
I've now started putting the RB40/RB41 services into the timetable using a mixure of 7&8 car Talents (two units in multi) but again I've been hit by the portal issue whereby any 7 or 8 car Talent won't enter the portal but 3 or 4 car Talents will. Once I get the timetable to a state whereby the Bad Vilbel services are all in, I'll get a timelapse video put together to share.

 

I've managed to fix the portal issue, which means the S-Bahn now has 12-car services again and I've had no issues getting all the other AI services in too. The passenger AI at Bad Vilbel is now complete and simulated (with the exception of the HLB RE98/99 and IC2 services, due to lack of stock). Freight is something I intend to add in last, as I'll need to get some research done on what freight passes through Bad Vilbel and Nidderau. I've linked a video showing around 90 mins of AI traffic at Bad Vilbel, sped up at 5x speed within the editor. You'll no doubt notice some issues within the video, if there is any you spot which aren't listed below then, please, let me know!


Bad Vilbel AI issues:

• Platform 1 stopping locations
• Formation driving directions (some 146 services are being driven from the back)
• Minor time adjustments to overtaking services required

Also shown are three screenshots of the various layers. You'll see just how many S-Bahn services there are throughout the day and how straightforward the ICE services were to add.

 

Amazing!!

There are some nice community-made repaints of Dostos and the 146.5 for IC2 services, maybe it's possible to use those somehow?

 

I believe it's not currently possible to use creators club liveries in the editor. In the future if a livery becomes available as a .pak and the editor is able to use these (which it can't currently) then I'll more than happily add them in. Same applies if the SBB flirt is reskinned into HLB livery.

 

Spent the afternoon tidying up the AI at Bad Vilbel, a few places had the incorrect timings. Also added in a weedkiller player train with the 204, which I've set to run in May. I've based it off an image I found of a similar train on the line, I've had to make a couple of changes to the rolling stock used but hopefully it still looks good!
https://www.bahnbilder.de/bild/deut...5419/db-fahrwegdienste-212-093-9-und-212.html

 

That's a cool idea! German routes are pretty much missing the more unusual services that British routes tend to get, so I love to see this. Can we get a mint 628 railtour too?

 

That's a good idea, I'll look into getting one added!

 

Can't you just use the 101 and IC1 coaches for the IC2 services for now?

 

I likely will do. I haven't built that layer yet, I intend to build all the layers so as stock becomes available I can easily add it in. I was hoping that by the time it comes to publishing the timetable there might be a way to put a IC2 reskinned 146+Dosto in.
For the HLB services through Nidderau, which are normally 1440 operated, I'll just use a Talent 2 instead. I could also do the same for RE98/99 services?

 

If you backdate the whole thing by just one year, DB Talent II Sets are actually completely prototypical for RB49.

 

I think I'm gonna release it as a modern timetable rather than a set 2023 timetable. Once a 218 gets released, I'll use them for the 245 operated Dosto services. Gives me a bit more creative license!

 

Question. How do you increase the speed the editor runs at?

 

In the console, use 'slowmo' then enter a number after it. Matt mentioned going above 5 starts being unreliable.

 

Not a whole lot to update on with the timetable as I've been busy moving house and only just got my PC set up. 642s have been added into the timetable now and simulated with only 1 error I need to get fixed. Once that's fixed I'll get the AI at Stockheim added in along with a 628 seasonal railtour!

 

Ic2 Train set as pak if you need it

https://rail-sim.de/forum/filebase/entry-download/6002-doppelstockwagen-ic-für-msb-fiktiv/

 

will u make the max speed higher? because u are not able to hold the timetables with the current high speed on that route

 

No, there are no changes to the route or line speed. Despite the lower line speed, trains only lose about 2-3 overall which I'm not concerned about.

 

I mean you could just pretend that you aren't speeding, when the limit is 60 imagine that the actual speed limit is 80, I think you can even increase the speed of AI to compensate *I'm not an expert*

 

Based on the simulation, I'm not really concerned about the difference in line speed as everything is effected. With the dwell times at some of the passing points, most of the time gets recovered anyway.

 

How far off are you from releasing the timetable now .?

 

I've put no work into it for about a month now, due to real life being busy. It's unlikely I'll release it until the editor is updated with the cooking fix (I'm aware there's a work around, which I may consider looking into). In terms of what is left to do:

• IC2 services - I'll see if I can get them working with the reskin above, if not I'll use the 101.
• Stockheim AI - Should be pretty straightforward.
• Freight AI
• 628 railtour

 

Small progress update

• Stockheim AI is now in and simulated, I've used DB 642s for this as a replacement for the HLB 648s.
• Nidderau passenger AI is now all in, I didn't realise I hadn't finished doing it (whoops).

Planned next:

• IC2 services using 101
• 628 railtour
• Freight AI

If anyone has any useful references or information about the frequency and types of freight at Bad Vilbel and Nidderau, it would be very helpful as I'm yet to research it.

 

Small update on progress:

• IC2 services are in using the 101.
• 628 railtour has been added for the month of July, I could change it so it runs throughout summer.

All that's left to do is add in the AI freight services at Bad Vilbel and Nidderau. I'll probably also add in the HLB Flirt Services in a layer so any future rolling stock can be placed in pretty quickly.

 

Only freight left to put into the timetable now, I plan on making Nidderau very busy with freight traffic. Despite having worked on this project for many months now, I've never actually done a full run of the route with the timetable until today. Some screenshots from the run below, no idea why some of the terrain hasn't loaded in correctly in some of them.

 

still the bad 628.2 there. thats not modern.

 

It's the railtour service. The 628 is also used for the 245 operated services to provide more variety.

 

i hope TSG to release the 218 in 2024 quartal 4 . so we dont need to drive the 628 to long.

 

I've started to attempt to put freight into the timetable but naturally I've hit a problem. The editor won't allow me to route southbound freight trains through platform 1 at Nidderau (Heldenbergen-Windecken), it comes up with an electrification error despite already having various electric trains routed the exact same way. I instructions were even copied from one of the working services. Any ideas on the cause it welcome, I've tried using both 185 and Vectron formations.

EDIT - It seems loco hauled electric trains, all have the same issue but EMUs are fine. Are they set up differently somehow?

 

A further addition to this, what I said in my edit isn't true as I've remembered that I've got local hauled regional trains running. It appears to be an issue with train length. Still trying to figure out a work around for it, which doesn't involve routing everything through platform 2.

So, the issue appears to be that any locos where the RVD has electrification requirements set up, doesn't work.

 

The good news is that the timetable is in a position where I'm happy to release it. The bad news is that despite spending many hours trying to use the cooking work around, I cannot get it to cook. So until DTG sorts out the cooking issue, you'll just have to make do with a couple of screenshots.

 

Why not join TSC discord where people are always ready to help will give you a way to sort out your problem

 

https://discord.com/invite/G6MZ5SR4TR

 

I'm already on there and occasionally ask for help. If I make no progress and ask for some more.

 

Good news!
The timetable is now available to download and play. I'm very happy with what I've managed to achieve and the stop start nature of the route makes the 642 a nice addition to it. I'd like to thank everyone on this forum and TSC Discord who have given me advice throughout this project. If anyone has any further suggestions, or help with fixing some of the known issues, you're more than welcome to say.
https://www.trainsimcommunity.com/m...reations/i4165-niddertalbahn-modern-timetable

 

Just played my first modern service and loved it, thank you!
Do you have a recommended 642 livery to go with your modern timetable?

 

Someone on the TSC Discord (Hannah) is kindly working on a RMV Pack which will add the correct logos onto the 642 and 423.
I intend to update the timetable at some point next week to fix the issues with PIS all showing S6 and the arrival times not working correctly.

 

Hello,
thanks for your work and this additional stuff!
But everytime i start a service (modern Niddertalbahn), the game crashes. Game is running on Steam. Both DLCs are installed and everything else is working...
Some ideas, what i'm doing wrong?

 

It's possible I might have missed out a layer tag somewhere, is there any German DLC you don't own? The layers use KWG, HBK, KAH, MAG, 101, and Vectron. I'll be removing the MAG requirement in the next update.

 

Thx for your reply. Yep i am missing KWG and HBK. So i have to buy them.