it is, and I have even created a separate thread dedicated to driving techniques (and some testing of them, tho I havent tried again after recent batch of updates) of such locos... they are incredibly fun to drive, as long as the brakes work as they should, especially when trying to stop
Don't feel bad, I started attempting German trains, I am in the US, when TSW 2020 came out and I am just now really feeling comfortable in driving them.
I do have a possible criticism of the FSB 143, although I might be doing something wrong; however, I haven't noticed this with the older 143/112/114: the "Nur Bremsen" program doesn't seem to work. When I'm negotiating a platform stop, if I release the brakes the thing starts accelerating again even though NB is nominally running.
I think someone in that Driving techniques thread mentioned that the programs arent properly implemented (as well as using Aux whatever on 112 can brick the loco for the run, I think?)... I dont use em, for speed adjustment I use Force selector and for stopping at stations I turn off Speed selector and use Train brake (and hope the e-brake portion engages correctly )
It seems that if you pull the speed selector back to "on" you get e-brakes, but if you turn it "off" it takes the traction motors completely out of the loop. Weirdly, the driving programs worked fine on the old DRA 143.
I have learned both German and Austrian PZB fairly well by now, but in general I use this rule - I see a speed reduction of 8 or less, I acknowledge and brake... or, if the signal has any yellow in it, I acknowledge and brake
even with Speed selector off, e-brake should still engage when using Train brake - current 143 does this, 114 takes its time and havent tested 112 recently, so dont know Speed selector On is like setting it on zero, so it engages e-brake depending on Force selector
Honestly I think DTG erred with the control mapping for the 143 family. It would be both more true to RL, and more intuitive for TSW players, if they had reversed them: mapped the speed selector to the AFB controls, and the force selector to the throttle controls.
As the BR143 is the topic right now: I just found out that the Hilfssteuerung on the Frankfurt one is not working. On the DRA and even on the old RSN one it works. I kinda like accelarting from standstill to slower/moderate speeds with the Hilfssteuerung as it gives me more control over the Fahrstufen and then switch to the speed selector...
Installed it but there's a problem- maybe a conflict? The departure boards are great, but all the platform PIS screens are blanked out now!
when you put Speed selector to Off, it doesnt take traction motors out of the action - once you put on Train brake, it just has a slight delay on e-brake... usually on notch 1 it barely engages, usually it takes notch 2 or higher to add e-braking to air braking ... this latest 143 works nicely... on 114 it works, tho differently than on 112... and 112 I havent tested yet (busy with Elden Ring atm lol)
I get a lot of off map paths in free room on both ways into Frankfurt. I have to manually set Go-Via waypoints for the route on map
With the 143, when going at speed, then approaching a station stop, if I turn the speed selector to " 0 ", the train rapidly deccelerates without using the train brake. Sometimes, I have to select some speed to avoid stopping too soon. I only use the train brake to hold the train at the station. Is there a way to " cruise " that I'm not aware of?
well, the amount of electric braking force is controlled by the force selector lever- pull it back to, say, 20% and you'll get a nice gradual deceleration
I have that PIS mod installed as well, but I have no issues with the platform PIS screens they all work. I have read that some TOD3 -> TOD4 mod is making problems and makes PIS screens go black.. Do you have such a mod installed by any chance ?
I do. And, to support that theory, platform PIS seems to be fine on newer (TOD4) routes like Vorarlberg.
Trying this suggestion from the awesome runs thread, i get a deadlock at the start. After half hour the red signal still wasn't cleared, probably deadlock with RB22 that has to go to my platform. this is on epic with the full timetable
iriv#7314,I first ran this service, RE2 (4252) and, once stopped short of red, Hp0, signal 01A521, I went into the 2D map and just watched. That RB22 (15249} was stopped short of signal ZU559 which was Hp0. So, I watched for 20 minutes and trains came and went but neither my train or that RB22 service moved. I finally deleted it and got my green. Second time, I deleted that RB22 service immediately. Still had to wait at signal 01A521 for about 4 minutes until I finally got a yellow Vr0. Moved from this to another Vr0, then finally got a Hp1, green, and was on my way. Now, I did not complete the service but will go back later and run it fully.
I think the RB 22 is bound for the exact platform that you are leaving from. I had that situation as well, could see the platform arrival on the minimap within a few minutes. Actually reported it in this thread before i think
That is what I saw. It is a flaw with the AI dispatcher I am thinking. It should have let the player train depart while holding this RB22 service. What I saw while watching the map was this AI service not even getting onto the player path until after the player's departure time.
I have updated my original suggestion in the awesome services thread. I'm not sure what the difference was the first time I ran that service, but now every time I try running it, I get the same deadlock aswell. I have encountered a similar one earlier that I forgot to document, the difference was that I got held up indefinitely going into instead of out of Frankfurt Hbf. There was also this one, not sure if it was reported before iriv#7314 with S8 (35860) Hanau Hbf to Wiesbaden Hbf at 18:46
Ran an S1 yesterday and got a bogus Vr0 associated with an Hp1. Fortunately there was enough sightline that I hadn't slowed down too much.
anyway, not fully related but still - 143 works here nicely, so I was curious if they fixed 112... so I ran a service on Hamburg Lubeck, and for a bit it looked like yeah, the e-brake actually reacted during first major stop, also for the second, but on next one no show and I overshot the marker by almost full length of my consist... so... yeah... will check 114, as far as I remember, that one had slightly worse braking than 112 when it still worked
Was playing this route for the morning on xbox x and it feels dead and lifeless. I think because we on a reduced schedule. Got bored quick its shame because it could be really busy.
Well, it has become my favorite route now, surpassing BML. I am on pc so different experience to console players.
I fully agree. I haven't done a general feedback yet of this route because my pc is quite crappy and there is a lot of stuttering. But damn.. The first network route that gives you some speed and length.. I liked Cathcart and Cardiff too but they are so slow and short. Using the german safety systems. the 430 is so nice to drive, sounds are very good too The addition off the FernFlughafen (or so) with the ICE services through it opened a whole new world for me, in particular trying to combine them with Frankfurt-fulda and even further to Kasssel. Even to Koblenz if you distract a few years . Getting the ICE's through this part of the network is just fun. I generally like routes with a lot of switching so this is my walhalla now. I quite forgive the dispatcher lockups and stuttering for all of the above.
iriv#7314, the issues with AI trains blocking your path is something that is in the main game. I have seen it many times in routes with very busy timetables, the AI dispatcher just gets overwhelmed.
The counting Mastery is a disaster. Sometimes it shows that Tier 2 is completed, sometimes it doesn't. In the Frankfurt S-Bahn, the checkmarks are missing in Tier 2. However, I have completed 5 scenarios. You need to revise the system here.
One thing I do like is the new “whoosh” sound as AI Class 430’s pass your train. We could do with that backdating to some of the older stock. Now all we need is the 420…
Just had my first UE crash that I could not related to something specific. I was running a BR 425 on a RB10 (25004) service from Frankfurt and was about 8 km from my first stop at Mainz Kastel when it happened. On straight track, in the countryside with no other trains in sight.
When playing the scenario "Hear that train a comin'", where you pick up a singer at the airport and bring him to the stadium, on the way back to the depot there is a signal that remains Hp0 (Halt) instead of showing two extra white lights to let me pass. The HUD says the signal is green but if I play with PZB on, I need to press "Befehl 40" when passing it to avoid a Emergency braking. I've explained the situation a little bit more detailed four posts down.
So it's been almost a month since the release of this DLC and if I'm not missing something, there hasn't been any progress from DTG regarding consoles? I mean, is the reduced timetable still the same as at the time of release?
Krober, I got the same thing and it caught me since I didn't react and press the PZB override. But no harm, going so slow that could recover quickly and get the scenario done.
At the start of Scenario 4 "Hear that train a comin'", when shunting out of the depot, you must pass the signal "04 N4", which issues a PZB emergency brake (if the PZB is activated), for not pressing the vigilance button at the signal. The signal does not show a signal aspect that requires the PZB watch button to be pressed. Additionally, the signal aspect should be changed, as operationally, shunting ends and train movement begins at this signal. This means that from the start of the scenario to this signal, a maximum speed of 25 km/h is permitted, and when passing the signal that converts shunting into train movement, the speed is then the line/signal speed. The signal "04 N4" should therefore show a travel aspect, for example Ks1 or Ks2 with any necessary additional signals. The same applies to signal "ZU4", near the end of the scneario, which I already reported above. This is where the train's operational movement ends and a shunting movement to the destination begins. Therefore, the signal must show Hp0 and additionally authorize the shunting movement with the signal Sh1 (DS301) or Ra12 (DV301). A small side note for DTG: I'm a train driver in Germany and therefore very familiar with the signals. I'm happy to report any further errors or help with any questions!
At the start of Scenario 5 "Dreierbesetzung", when shunting out of the depot, you must pass the signal "04 N4", which issues a PZB emergency brake (if the PZB is activated), for not pressing the vigilance button at the signal. The signal does not show a signal aspect that requires the button to be pressed. Additionally, the signal aspect should be changed, as operationally, shunting ends and train movement begins at this signal. This means that from the start of the scenario to this signal, a maximum speed of 25 km/h is permitted, and when passing the signal that converts shunting into train movement, the speed is then the line/signal speed. The signal "04 N4" should therefore show a travel aspect, for example Ks1 or Ks2 with any necessary additional signals. Further errors in scenario 5: Due to the malfunctioning signal "04 N4" at Frankfurt Central Station, the 60 km/h speed of signal "63 243" is not announced, but instead suddenly appears on the distant signal repeater shortly before the main signal. Additionally, signal "63 243" is missing the 60 km/h announcement for the following signal "63 C233," which should be an entry signal for Frankfurt-Griesheim station.
As say tspchris#1708 there are missing speed signs after leaving Frankfurt Hbf. Another missing sign is between Frankfurt Stadion and Flughafen (I don't know what is the track speed limit after the 80 km/h limit ends). Weak headlights in BR430 (night). S8 (35912) service - I'm stuck in between Kelsterbach and Raunheim. Despite the empty road, the 31 104 semaphore shows stop. At the same time, the S8 in the opposite direction was stuck in front of semaphore 31 103. Missing magnet in front of semaphore 31 104. There are definitely too few passengers on the platforms.
I agree with 2 and 5. I haven't experienced the other problems. The weak headlights are a problem due to the lighting. I like the new version where it is dark at night but all headlights (every loco) need to be reworked so at least the high beams work nicely. I think the passenger capacity is a thing that would influence your performance. Would be nice if we could choose ourselfs if we want more or less passengers.
Another error that I have noticed in both timetable mode and scenarios is that the level crossings on the S1 line between Eddersheim and Hattersheim at kilometer 17.6 and on the S8/S9 line between Kelsterbach and Frankfurt-Stadium at kilometer 26,8 start to close much too late and when I drive at the permitted 140 km/h I always pass the level crossings while the barriers are just starting to close.
The track crossing just before the Rüsselsheim platform is not implemented correctly. The tracks are intertwined even though they collide with each other.
I post a few posts back that while running an RB10 service I got a UE crash in open country, well reran the service and this time no crash at that location. So, who knows what caused it.
Just finished driving a RE 13 service (29205) using the BR642 DB and it was fun. I have turned off the PZB helper screen on the HuD and so far am having no problems. Now, a question for those knowledgeable with the cab displays for PZB, when I first pass a 1000 hz magnet and acknowledge, the 85 light starts blinking, but later I notice that the 85 and 70 lights are now alternating. So what is the meaning of these lights. I have noticed the same behavior in other German cabs. Just wanted to point out that the country code on the GSM-R is A not DB
It indicates that you are in restricted mode, limiting you to 45kph, as long as you are in a 1000Hz influence. Restrictive mode also happens in a 500Hz influence, in this case you are limited to 25kph. Restrictive mode is initiated when you drive below a certain speed for a certain time (usually 10kph and 15 seconds) or stop, while in an active PZB influence. EDIT: In more modern locos, like the Vectron, the restrictive mode indication is different. It will tell you in the yellow bar below the blinking "85" what speed PZB currently limits you to. Here you will not see an alternating 70/85 indication. In addition, all ICEs with MFDs share the same bug in TSW, that they do not show restrictive mode at all. You will not see any yellow bar or alternative blinking. Unfortunately this has been ported through all iterations of the ICEs and does not seem to be taken on by DTG, whatsoever.
When only the 85 light blinks you have to reduce your speed to at least 84 km/h. Once you stop the train whilst the 85 was blinking it reduces the allowed speed to 44 km/h, indicated by the 70/85 alternating. For example: 85 + 1000Hz = reduce to 85 km/h (in real life train drivers have to drive 5 under so 80 in this case) 85 without 1000Hz = 85 km/h but you can press "PZB Frei" to free yourself 85 + 500Hz = reduce to 45 km/h (in real life 40 km/h) 85 + 70 + 1000Hz = speed limit 45 (in real life 40) 85 + 70 without 1000Hz = 45 but you may press "PZB Frei" 85 + 70 + 500Hz = speed limit 25 (in real life 20) 85 + 70 without 500Hz = 25 but you may press "PZB Frei" These speed limits are ONLY for PZB O with a maximum allowed speed of 160 km/h. PZB M (max 120 km/h) and PZB U (max 100 km/h) have different speed settings! Hope this helps
In some trains, the blinking for 85 and 45 is the same. There you have to keep track of what you did yourself. This is also where i still fail the most. So, if you stopped with the 1000hz on, 45 is the max if you drove 15 seconds under 10kph, 45 is max otherwise 85 although i am not completely convinced the game works like this (no proof through stupidity)
