Hi guys, is there any recommendations on how to play the Rapit Transit Journey with LZB/PZB? For me it is not doable, because the journey is based of the old timetable and somehow the signals act odd to it. Every stop will have a red signal after it and will turn green once the doors are closed again. That is even in case no train is in front of me. The issue is, that every station approach will come with 1000Hz and 500Hz PZB, in which case I lose so much time that I can't hold the timetable and end up on silver.
RT is the most flawed and broken route in TSW. Don’t look for much if anything in the way of fixes from DTG as it has long since dropped off their radar. IMHO they shouldn’t even be selling it, let alone at full price £25. Only advice is to play with the safety systems off.
On all TSW german routes the PZB system is wrong I think, for example a speed limit should be active after a Hp signal, not after the Hp signal at a start of the switch for example, what's the case on all Tsw routes. In Trainsimclassic this is correctly implemented I think.
Thanks for your comments. At least know that others know. Well, I guess the easiest fix for DTG would be to redo the journey mode based on the new timetable. The issue with the always red signal after a station/stop seems fixed there. Could that have something to do with the updated signal-dispatcher? If I remember correctly the new timetable and a dispatcher fix was about the same time when it released.
Well, the PZB is mostly correct, what you are meaning is the HUD doesn't display the speed limits after passing a signal. (PZB will only check you slow down after an active 1000 Hz magnet, it won't check your speed afterwards. PZB doesn't know about speed limits - it's just activating simple braking curves). This happens on many routes - you get a Vr2 for example with a Zsv3 displaying "5" - which means at the next signal the speed limit of 50 applies. Often it doesn't, eventually only when you reach a junction. PZB is correct in this case - the game HUD and score supervision is not, and the HUD often displays incorrect speed limits so I just ignore it - the HUD is no authority for me So if you're driving HUDless you can ignore the game's wrong speed limits and drive following signal speeds.
Rapid Transit, despite being one of my favorite routes just due to the fact it doesn't really stick out much, is a TSW2020 map... meaning it's smashed to bits as we kept switching games. Are they going to fix it? Absolutely not. At this point, they probably forgot about it completely. Unless the issue makes it literally impossible to complete the game.. which would justify a refund, they will probably look the other way.
Which is why it should either be taken off sale, or discounted to something like £3 with clear warnings that it's not up to the standard (ha!) of more recent releases.
Actually, it was fixed then by the preservation team (adding the dispatch beyond), with TSW 4, it was reverted back to the original state...so, it was playable for somewhat like 1 year and a half.
Honestly, the only reason I ever bought it (on sale) was to be able to buy the 182. I'm not sure I've ever played it.
You really can't get off your rose tinted DTG adoration, can you. Same could be said about those games as well which is why I only tend to buy stuff that is established, has good unbiased reviews etc. But Rapid Transit is quite frankly the pits of TSW DLC and it's laughable you even think about defending it still being on sale for £25.
Just called him a fanboy so expect I'll get a weeks holiday from the forum now. But his constant unwavering defence of anything and everything DTG do no matter how outrageous or thinking he is some sort of unofficial spokesman starts to get a bit bothersome.
This is the map that deserves to be adapted to TSW4. Strange errors need to be fixed, the functioning of Talent 2 vehicles needs to be unified with those in Dresden, and the strange-looking light needs to be corrected, especially at stops in the tunnel.
I am surprised they dont do what they do with TSC routes that are older and have like a classic edition
I'm guessing this is one of the routes that would probably have been sorted by the Preservation Crew, if they hadn't been sent down the road.
Yes, and that is a strong indicator, that DTGs data management in the engine is bad. For example, all Talent 2 trains should have ONE data base and child versions within the DLCs. With that bugs, which get fixed on the main base dataset get fixed in all child-versions, too. That is basic Unreal Engine management stuff... Same goes for all other locos BR 185, all HSTs... Which basically would safe time reworking trains for new DLCs and then still have old versions in old DLCs.
That might be a good topic for a survey, either the official one or maybe a DTG-created poll thread. "If you could choose one extant DLC for us go back and polish up, which would it be?"
I agree with this actually, it's an ancient route atp. I wouldn't say they would be necessarily losing anything since they've got plenty of newer more functional routes for purchase.
I quite like playing it. Just done the scenarios, so may not have hit the issues others have mentioned. I'll see what happens when I hot Journey mode. Brought it in the sale, and aware of its age, so not overly bothered that it has some minor issues
btw guys didnt 182 have some sort of AFB standing brake, y know, once you got AFB active, it usually activates loco brakes when stationary and releases em when you apply power... havent played Rapid Transit for a while, got a taste for it today and I'm like... did 182 have this or not, I cant remember for the life of me ... also, didnt it get more broken? I remember playing it mostly fine... now, eeeh edit: also, for some reason the PZB is like overprotective in the city tunnel, but outside it is fine... like, I was barely going 40, 250m in, and I got Zwangsbremsung, although I had room to spare for braking (this happened to me twice in a row lol, never got so many Zw. in such a short time), and during similar situation outside I didnt get one
ehm, I have just noticed sth, probably since I am doing back to back runs on this route - done a service from 2017 timetable, and thats as I described, red at almost every stop and resulting 500Hz thingies and occasional Zwangsbremsung, plus the same but less annoying with LZB, tho I managed to cut the delay and eventually come ahead of time to the final stop and scored gold and just doing the 2021 timetable, and this one seems to be set up much better for some reason?
ok, have run multiple runs on each timetable, and the 2017 is like, broken AF... red after almost every station, constant juggling between red and yellow, sometimes getting pretty weird Zwangsbremsung, and before you know it, you get to around almost 3mins delay, and only towards the end of the run you get some leeway and cut it down to nothing if you time your throttle and such right 2021 has shorter runs, which is a shame (I quite like the longer section before you get to Leipzig from Markkleeberg), but then, you get some nice green a couple signals ahead of you, thanks to which you actually get to run like a RAPID TRANSIT at the tunnel section, without constantly getting 500 Hz and sudden Zwangsbremsung (like going 40 with plenty of room, but then PZB decides that you should have gone 20 already and bam) and so, I recommend playing the 2021 timetable mostly, you actually get to enjoy the nice route and the powerful (somewhat OP here) loco... the 2017 you can roleplay like the signalling is going crazy
Matt has answered this, more than once. The problem with that model is that, whenever you make a change to a loco, now you have to test it on every single route where a variant of that engine runs- and in the case of modern German locos, that means ALL of them.
The game simply shouldn't have to be set up in a way where that would be needed, then. Why in the hell would I need to test if a PZB behaviour correction, or presence of a function, or blower sound on say, the latest 2025-released XYZ loco works on a route from 2021? The question has to be why would (could, even) the older route possibly even generate problems from this...
