Yes i know, if you key out and key in again after the service starts, the GSMR should display the correct headcode again
I found a way to get a lot more out of 07:45 RE50 Leipzig -- Dresden than just the "PZB action at the end" that it's listed for in the spreadsheet. For a challenge: Run this service in the 143 instead of the 146. It's very rare for this to occur in real life, but it has been done. Start the service in some kind of wet weather. PZB on, next signal HUD off. Try to be on time. Spoiler I actually managed to be on time pretty well, but I was slightly late at Coswig and an S-Bahn from the Meißen branch got priority over me. From there on, it was PZB hell all the way to Radebeul Ost, followed by a long wait to be let back on the main line. I was 20 minutes late at the end. Almost felt like a chaos run, but I didn't have to force any of the chaos - it all just happened organically because I was very slightly late!
Really interesting run, thank you. I questioned in my mind whether NTP’s wobbly signalling would be able to handle this, but all of the signal sequences I got were correct.
SEHS Desiro City Delays Scenario with the 700/0 This is a well designed engaging scenario with plenty of AI. The premise is that increased freight traffic had led to delays and, as advertised, you will not be on time. You actually wind up following 3 different services - a very engaging 75 minutes. Have the 700 manual handy to look up how to recover from a TPWS stop.
RRO - RE4 Wuppertal > Hagen - 07:00 Dosto-compatible locs layer into the timetable, so if you own just about any other German DLC you get RE4 services on the route. This one in particular piqued my interest as it's significantly longer than the other services of the day (33 min vs. 24-27) I was looking for some PZB action and was not disappointed. Ran it with the BR110 (112, 143 and 146 are on the menu as well, so pick your poison). Hardly any clear signal the whole way. You run into a red right out of Wuppertal Hbf and after a short wait immediatly catch up to an RE7, itself held behind the 6:29 freight out of Steinbeck. You follow both of them into Hagen. Spoiler The whole thing is likely a minor signalling/timetable bug. Looks like the 7:05 Oberbarmen-Wuppertal Hbf service has its route set too early by the game, leading to backed up traffic out of Wuppertal Hbf as it intersects the track to Hagen. A nice run nonetheless.
Just a note for this (incredibly amazing) list & resource: I've run London Commuter 1M71 13:46 Brighton-Victoria twice now, and I think it's listed on the spreadsheet by mistake or has been misidentified as a different service (or possibly the timetable has changed between TSW2 and 3). It's Greens all the way except for a couple of double yellows coming through Clapham Junction, and that was even with being 9 minutes ahead of schedule! (And I should say that I have LC, East Coastway, the Class 313, and GWE - which should result in maximum available AI I believe?)
Thanks. It has been a great community effort to find these runs. Pointing out one that doesn't work the same as when it was discovered is very important and I really appreciate your posting this. I have been wondering how to handle those runs that change with updates and fixes to the game. The layers are something I can't keep up with for these runs so that may also be an explanation about why it doesn't seem to behave as originally discovered. However, runs do change with updates and I do need some way of addressing this. For now, I will keep the run on the sheet and put a line through it to indicate that it seems to have changed with an update to the game. If anyone has a different idea on how to handle this, please let us know. Thanks again!
The complication, of course, is that the signal checks on timetabled runs do vary depending on how you drive them. The obvious one, of course, is that a person who just drives as fast as they can regardless of timetable will get signal checks not seen by someone who aims to conserve (virtual) fuel/electricity and keep the train in its path. However, it can also work the other way around - a run identified as having signal checks by someone who keeps the train in its path, may not have signal checks for someone who runs very early - because hitting a particular junction early enough might result in getting ahead of the train which is supposed to be in front of you, providing the signal checks. This does make it difficult to identify whether a run has truly changed, or is just being driven differently. However, I agree that if you leave it in the spreadsheet with a line through it, others can try the run, driving it their own way, and report back - which sounds quite interesting in itself! (or maybe I’m just weird…)
It's interesting that you say this: I've wondered about this too. Running ahead of the schedule and encountering signal checks is an obvious case, but I'd be interested to know: is the signalling in TSW actually 'clever' enough to allow the opposite situation you're suggesting here? My impression is that the game works with a fairly basic level of sequencing, which is why things get stuffed up if for whatever reason a train doesn't move (e.g. through a save and re-load). So I think that the game gives you, the player, the longest cleared path it can at all times taking into account any scheduled movements (assuming your train is actually 'on', i.e. key in and reverser on), but once a path is cleared/has gone green, it will never step down until you've passed through it. So let's say I'm scheduled to pass over a junction at 10:00, and there's a conflicting movement to pass over the junction at 9:57. I don't *think* that the game will give me movement authority across the junction until 9:57, then deny it for a few minutes, then give it back. It will just hold the signal at danger until after 9:57 (as it should, to be fair, or you allow the possibility of the signal suddenly going to danger as you're approaching it). But conversely, if I'm late (and the path has already been allocated), and there's another movement to cross that junction at 10:05, I will keep priority and the other service will wait. I could however be completely wrong, but that's my impression of the way the game handles you. (Wouldn't dynamic delays be fun!!). I suppose a partial fix to this issue would be that when we discover a route, to specify whether we were driving to timetable, or ahead of it?
As I understand it, the game doesn’t signal a train for its entire route as soon as it leaves its point of origin. It sets up the route as the train goes along (like in real life to that degree) and which train takes priority at a junction is not pre-determined - it is influenced by the actual movement of the trains. So if you’re running early or late, it can indeed change the sequence in which trains are signalled through a junction. The only problem is that the game is not hugely sophisticated in how it decides which train to signal first in any given situation, so it does create some oddities, like fast trains being held to put slow trains in front. I actually don’t think it’s entirely a bad thing that selecting a train from this thread doesn’t guarantee signal checks. Drivers in real life aren’t guaranteed signal checks either. It’s just they’re far more likely to get them than we are by choosing a random timetabled run on TSW. I like the fact that choosing trains from this thread means it’s much more likely I’ll get signal checks, but an entirely green light run is still possible - just like in real life
Matt described it briefly in this thread once. https://forums.dovetailgames.com/threads/did-the-signaller-get-dynamic.70846/
Thanks all - interesting stuff about the signalling. That's a really good point - thanks. I have my own suggestion for London Commuter: 1Y40, Victoria - Caterham & Tattenham Corner, 17:00. Class 377/4. A busy departure from Victoria, crossover from the fast to the slow line at Selhurst, and lots of adverse signals. Run in winter for darkness & added difficulty.
Southeastern High Speed Extended + ROG Class 37 5Q23 Yard Prep (11:32) 5Q23 Gillingham Depot to Wembley Reception Sidings (11:59) Two back-to-back services with Class 37 involving shunting in Gillingham and then a short run to Rochester. Plenty of AI traffic that gets in your way as you cross the mainline to the siding on the other side. The second part is short, but you follow a stopping service so there is plenty of yellow signals with some red. Do not bother with metals on these two as the scoring is way off.
89417 HLB DB BR 187 This freight service takes place at night at 21:50 from Rothenburgsort-Lübeck Hbf. I chose the 187 for this run because of the headlights and not long into the run, you catch up to a Regional service to Lübeck. So, expect adverse signals and run under PZB mode U. You also encounter the ICE 3M coming down from Lübeck as you pass Bad Oldesloe.
I have another BML service worth adding, not because of any notable signalling or AI traffic, but because of the variety of activities involved. It's 5U83, a class 387/2 service departing Lover's Walk Depot at 14:55. You do a depot move to the north end of the yard, switch ends, then you head to Brighton, where your 4-car formation couples to a 8-car formation already waiting at the platform. You then drive the 12-car 1M83 to London Victoria. After that, you can continue back to Gatwick as 1D02 after a 16 minute layover.
Another SEHS service. Nothing particularly noticeable but I quite enjoyed it. 5U05 Gillingham Depot to Gillingham (both parts) @0527 and @0535 A simple run starting at the shed in Gillingham Depot, ending at Gillingham Station. Requires switching ends for Part 2. A variety of traffic. Once you start Part 2 you go to the reception siding and wait alongside a 375 (4 cars). You also see an 8 ar 375 connect to the 4 car which then leaves before you towards Chatham. Once you depart the siding, you end up at Gillingham Station, where you can then also do 2U05 Gillingham to Dover Priory @ 0548 (also requires switching ends). Some nice AI traffic passing in the form of Thameslink and Southeastern. I ran these on a clear January morning in a 465, although it can also be done with a 375.
1N14 Charing X to Strood. Running all stops to Strood, you are behind a 700 and 395. As you are between Swanscombe and Northfleet the 395 leaves Ebbsfleet to Strood (don't know where it goes after that). You get held up near Strood because of the Javelin. Nice variety of AI, including 2 Javelins heading towards Ebbsfleet in close succession as you're near Gravesend.
A great service, made even better with the 700 layer. The second Javelin headed towards Ebbsfleet is also awesome. It is 5F55 which is an ECS Javelin run that is a Greatest of All Time nominee for me. Run it in fall to see the RHTT. You deal with adverse signals on two different safety systems and have a nice coupling move at the end. Here is the latest update: Google Published Documents: TSW3 Recommended Service Runs: https://docs.google.com/spreadsheet...4lUuBrw-k2_y7FxuzH6mZ1m3Qu4YTfLViTfxQ/pubhtml TSW Compatible Recommended Service Runs: https://docs.google.com/spreadsheet..._wzt7qTCooxSTBW8pGAwYLs_ohsdDOcQOuZ4A/pubhtml Chaos Runs: https://docs.google.com/spreadsheet...yCTbHVZrwBSBUUkPiiJGlTWfRXexfPn7kBVDw/pubhtml Excel Spreadsheets: TSW3 Recommended Service Runs https://docs.google.com/spreadsheet...ouid=108028767534258522758&rtpof=true&sd=true TSW Compatible Recommended Service Runs https://drive.google.com/file/d/14YgilvnKZFc7TJXyqftRJ0I5yTMlMf81/view?usp=sharing Chaos Runs https://drive.google.com/file/d/1cMKrwNA2OmZz8tVEQo1_FZnRZXpNT463/view?usp=sharing Let me know of any errors, omissions, or runs that may have changed with an update.
Got another one on Linke Rheinstrecke: Mainz - Koblenz with Br 103: IR (2310) Karlsruhe to Emden at 8:53. Just a relaxed early morning run. Or so you’d think… Spoiler While this run isn’t too crazy, it was nice to see some traffic build up. Before you set off, you let an IC pass on your right while a freight train departs to your left (which you’ll overtake leaving Mainz). On your way to Bingen, you might catch up with the IC, so watch the signals. In Bingen, you have a short scheduled stop. The regional train to your right leaves before you and will slow you down once you depart. Not long after, the regional is pulled to the side and you can finally let the 103 run while overtaking the regional.
Probably my favourite long drive in this sim. 5 hours of fun. I even did a version of it with the locomotives shut down, not attached, and on the wrong side of the turn table.
But wait, there's more! Switch ends and run 1F56 back to Faversham. You do encounter a few adverse signals the closer you get to Faversham, but the main point is that you park on the passenger loop, uncouple the front part of the train, and then take it to the up sidings. There, you switch ends again and drive back to track 4 to park it for the night. It's a great couple of hours with a huge variety of different things to do.
How the hell do you couple at the end? I cannot figure out for the life of me how to join two 395s with working brakes and electricals.
Try this: Come to a stop with enough space between you and the other unit. Put the master key in the other unit, set the reverser to neutral, and press the "Front Couplet Preparation". Do the same on your train. Then move your unit into the other one. Press the "Couple" button. Basically, you need to make sure the nose cone has slid away on both units to expose the actual coupling gear.
Thanks, I finally worked it out. For some reason it hadn't occurred to me that there are two steps, the mechanical coupling (automatic) and the electrical coupling (dash button). And then had to remember to turn off the other cab again! -------------------------- BTW, that's a great service, with a lot more TVM action than you usually get on a HS1 run.
Really enjoyed that, followed it up by changing ends on the Medway Valley Line then preparing the unit for a Gravesend- Charing X run afterwards and you get held up somewhere along the way as well. Love driving the 465!
As promised I set out a challenge in a thread on the Harlem Line in this forum. Train 528 North White Plains to Grand Central Terminal
My Favourite Runs are the ca. 3 Hours / 4 Part Services in the Dispolok ES64 U2 at Kassel - Würzburg (LZB Fault with delay included) , single Engine Loküberführung + Coupling and hauling a Freight Train in the end: Part 1 & 2 (13:42 - ca. 1h20min): - 1: 67142 - Körle Ost to Fulda - 2: 67143 - Fulda to Würzburg Begin at Körle Ost you can take the Taurus ES64 U2 Dispolok (Single Engine) up to 230km/h under LZB down to Würzburg. You get looped a lot to let the ICEs passing. Part 3: (21:33 - ca. 30min / 50min with delay due LZB Fault, spawning on foot a couple of minutes earlier!!): -3: 67144 - Würzburg to Fulda Taking the Taurus Dispolok back to Fulda at 230kmh in the Evening on a nice night LZB Speed Run.., hah at least that was what i thought in the first place. As soon i came into the LZB restriction, the Loco got some strange signals and forced to brake the loco down to 0kmh. (I didnt know its a "tsw 3 Bug" on this loco because the Cab 2). But the Situation was you are blocking the Mainline with a loco and you have to come up with a solution. I "wasted" 5 minutes to figure out what this might be, but nothing worked. So i decided to isolate to LZB and drive the loco under PZB O with max. 160 kmh to Fulda. You will arrive around 25mins late. Now quickly couple the Freight Train and make the Brake calculations, which gives you a allowed speed of 120kmh in PZB M (empty Kijls) Part 4: (22:15 / 22:30 with delay): -4: 67144 - Fulda to Würzburg In Part 4 you take the Freight Train back to Würzburg (The LZB should work now, but i choose to let the train run in PZB to not cause any more delay.) Right before Würzburg i got into a Red Signal because there were 3 Freight Trains on the Goods Sidings. The Red Signal stayed for 12mins and you get plenty of a.i S-Bahn and Freight Trains to spot, before the signal changes to green. I arrived at 23:40 at Würzburg, its probably nothing for medal hunters but the LZB Bug is fun and can be threated as "random failure", which is highly suggested by players. The 4 Parts gives a huge mix and a long driving time, The 160kmh in PZB needs more focus on signals. Here a youtube video of a similar cab ride on the same route:
Sorry; I tried it but the Dispolok 182 is just too effed up to be worth driving. Not only the nonfunctional LZB, but also the unreadable instruments, and the fact that reloading from a save it stops irrecoverably. Worst DLC purchase I have made- even the 187 isn't as bad.
Cant agree on that, but i understand if some players are annoyed by those kind of things. LZB works well, but not in both cab directions unfortunately. You can turn down the desk light by a dimmer. This is my favourite german loco. Funny how different opinions can be. Also real trains / locos have faults. Just wish the E-brake isolation would work, in winter a too low use of the friction brake causes a freezing.
I am not at my PC at the moment, but I believe you can run this with any 182. I prefer the Rapid Transit one: the gauge lights are a touch better and the SIFA light also works. I don’t know about LZB from cab 2, though.
Yet another SEHS run. Didn't see it on the spreadsheet so will post it here. 6Y21 East Peckham Tip to Tonbridge West Yard. A nice Strood to Dartford run (empty). Nice variety of AI. You will get held up at Gravesend, a 465 pulls pulls out of Platform 0. You then have to wait for another to pull into the same platform. You then follow the first 465 all the way to Gravesend, which stops at all stations. Highly recommended to run in blizzard conditions (or any conditions making it hard to drive), as you will encounter a few yellows and the odd red. Have fun keeping to time.
Reminds me the Berlin Wittenberg route scenario with the old BR (101)? and you get crossed a lot too.Berling Wittenberg-Leipzig is amazing in TSC with the detail on the old buildings and sidings and old disused tracks....... Makes me want to try this now.
I did Midland Mainline 2K65 Matlock-Newark Castle 17:11 in timetable service mode. Class 158 Very nice. You do stop at the first station, Spondon Stadium Station? Never had that before.
Route is RRO = Rhein Ruhr Osten RE4 is the service name (Regional-Express 4), IRL it goes from Dortmund to Aachen via Hagen, Wuppertal and Mönchengladbach.
As usual, trainsimcz released patch shortly after the DLC release that allows substitution of other compatible locos. Just trying it with MRCE182, and it looks okay even in TOD4. However, I am afraid I have to call on our lord and savior OpenMinded with a question once again. Can you shunt on LZB? In this particular service (KWG 67142), you are given a very unusual sequence of signal in Fulda. First, you get LZB Ende which makes sense as you end in the sidings there, but it still pulls you through most of Fulda within the LZB effect. But at the Ev signal, you get Vr0, with entry signal showing Hp0+Sh1, while LZB still shows you 100+ km/h and then slowing you to 60 within the diverging junctions. From ingame dispatcher point of view, the Sh1 is shown because you are pulled through opposite track in Pbf that only has shunting signal at the end, and after you pass through it, you get normal train path for going to the siding. But what are you supposed to do in this situation? You can't be running 100 km/h while expecting stop at any barely visible dwarf signal, and not sure if LZB can even use dwarf signal as a target for braking curve. I just pulled emergency brake when seeing Hp0, and crawled then on-sight under shunting rules within 25 km/h. Or is this completely non-canon situation and when encountering incompatible operations the signal would just give up, turn off and leave it on in-cab signalling?
Sounds like a wild ride But no, LZB can not be used to shunt (as LZB does not even recognise shunting signals) and you would under any circumstances be released before this sh1 signal. In reality this could have been an LZB stop, where the signaller gives you the approval to manually switch off LZB (Befehl 14.9) but it should not allow you to pass. By the sound of your explanation the simulation simply “forgot” to take you out of LZB at this specific signal. When I will find the time I will try this service myself. If there is interest I could go through the specific signals that are wrong. It is a bit difficult to say from just a written explanation, seeing it makes it easier for me…
Correct and that has happened to me on Riesa-Dresden 182 Dispolok runs. In that case, turn off AFB and drive manually under LZB PZB
1P99 Faversham to Dartford @1900 I know this is on the spreadsheet already, but apart from the signal checks, what else made it interesting? Asking because I just found that if you pass the 375 at Newington before it departs, you will get priority, and therefore will not be stopped at the signal before Rainham. I only found it out while driving that 375, as I had accidentally set the reverser to off as the railtour passed me, but thought I'd share.
For Birmingham Cross City try the 14:08 RHTT Service from King's Norton to Birmingham New Street during October to November fall season. Spoiler: What makes it special The service starts with you waiting at the junction between the RHTT King's Norton Depot and the main line for 10 minutes due to a 6 car train of 323s passing you. After it has left King's Norton station you will follow it all the way to New St with an alternating yellow red and green signals
East Coastway Far Reaches scenario Spoiler: What makes it interesting If you leave 1 min and on time from Eastbourne to Falmer you are going to be stuck behind a local US terminology for UK and Australia All Stations/Stopper service from Falmer all the way to Brighton. You must use the DRA Driver's Remainder Appliance on red signals from Falmer to Brighton on the Class 313/2. On the 80-90 mph sections of the route you always follow Class 313/2 75 mph (120 kmh) Max Speed
Thanks for posting this. Can you clarify something? If you run the scenario as designed, do you get stuck behind the stopping service or do you have to wait at Eastbourne for that to happen?
