I see no hope for this game on xbox... Revamped timetable of this route revealed how thin on performance this whole infrastructure is, stuttery and blurry texture in the oldest pre-tod tsw route... That is very very bad...
I'm glad to hear from the manufacturer's staff. There are some things I can't clear in the S12 service of the Aachen free update. I feel like I'm missing something.
Hope they do a better job of optimizing this route for Playstation than they did for Xbox. Since getting the new timetable I've tried to run the first Flixtrain Koln - Aachen service and the four times I've ran it it crashes to dashboard at the 48km from Aachen mark. I've cleared the cache and done a full clean reinstall of the whole game and still that service crashes back to dashboard! Also what happened to the 101? It's not showing in my loco roster on Series S but I have the 699 services that Series X players have
The 101 did show up for me on Series S. In fact, I completed IC 2404 with it. The only layers I don't have installed are BRO, LGV, and SRM. Although with a timetable this big it is impossible to know for sure, it does appear to me that Series S got the full fat timetable, which is commendable.
Crazy that this has somehow been released in error on PS4, and then later on Xbox. Really confusing release, but hopefully once it's available to play (I'm PS5) it'll be worth it!
Series S running the 101 (It turned up after I reinstalled the entire game) on IC1927 service from Koln to Aachen calling at Duren. 916m from stopping at Duren, passing a rake of cement tankers in a siding and got an out of memory error.
Because the Expert 101 loco substitutes in for the normal 101 loco and those consists don't have the cab car. It is currently not possible for the game to substitute the entire consist for a different one.
I'm a bit disappointed with this new timetable, having been to cologne in real life, doesn't feel anywhere near busy. Also to mention, the 187 doesn't run on the route in reality, it is mainly the vectrons Edit: Usually on cologne Bridge, usually 2 or 3 trains come and leave cologne hbf at the same time which sadly hasn't been implemented on the route
In terms of performance, I have noticed that with the likes of the vectron and the ICE 1, they tend to use up a lot of memory whereas the TOD2 ones don't. This is the problem when I find tod 4 trains on tod2 routes
Unfortunately, I'm also having a lot of problems. Besides the blurry textures, the game keeps crashing! I haven't been able to complete a single run yet. (Xbox Series S)
The 187 is just a multi-purpose freight loco. It can show up at any random German freight train. It's not at all unrealistic to have it here.
So when driving the BR406 when using the safety systems when you get to a lzb section it cancels out pzb correct but because it does that you lose ap points i lost over 2000 ponits because it thinks you dont have safety systems on because lzb cancels out pzb. Can only assume this will happen with all locos that have lzb. DTG Alex
Taking full advantage of the unintentional release on Series S, I can say this timetable is an absolute winner. So far I have driven the 101, 193, 406 and 423 with no crashes. Besides the nice variety of driveable services, the AI and static stock is noteable, especially the 642 which leaves the map everywhere. I stood on the platform at Köln and watched three trains depart at the same time. Blurry textures were present, but this is a TSW problem. It seems not as bad as other routes such as Mildmay, which I don't own but gets constant complaints. I didn't notice blurry textures at all when I drove the 423. As others have mentioned, the scoring system is broken if you enable LZB and it gets activated, but you can still get gold medals. I would say Joe has taken the timetable for SKA as far as it can go, and that's a good thing. Caveats: I do not currently have BRO, LGV, or SRM installed. I also only have a minimal amount of downloaded liveries. All my driving so far has not been in rain. Increased layers and liveries, along with bad weather, will certainly impact your experience, just like every other route on Series S. Good luck!
well, since I like 101 so much and me seeing a whole lot of 4 new services to run, I jumped right at this, an opportunity to run IC train at 200 during the day, yaaay... or not... the scoring bug is present here, which isnt really that big of a deal for me, since I want to drive this loco no matter what, but what bugs me is that I get constantly held up by another train in front of me, if I looked right it is a RE1... which means constant AFB/LZB braking, rarely getting above 140 or 160 kph, getting close to 200 like once... and then you get to Duren, which means the real highspeed section is over and you are relegated again to 160 and less I am aware that even IRL services get held up and not always reach full speeds, but daaaaaaaaaaaaaaaamn... I want to enjoy my 200 kph at least for a big, dammit ... what is even the point of an Intercity Train if it is held up by a freakin REX train that supposed to be kinda lower in hierarchy? "thanks" to this I get to Duren like almost 2mins late cos I get constantly slowed down and even stopped like 2-3x... and I was soooo looking forward to this, already one service is so not enjoyable that I didnt even finish it
Has anyone done job NJ 424 innsbruck to bruxelles. you start nowhere near station tells you open doors but they dont open.
I have tried the 06:41 NJ 424 service and have the same issue, it doesn't start in a station and it tells you to open the doors but you can't. It looks like it should be a wait instruction, after a minute or two it clears and then gives you the stop at Aachen instruction. Interestingly the 07:27 NJ 424 service starts at Koln Hbf.
The now 3 Timetables all contain some of the Layers, meant for Timetable Update, but the updated Timetable doesn't contain all of them, as shown in the Screenshots attached.
As another update I would encourage all who can to try FLX 1230 leaving Kôln at 1347. You will see LZB get a workout as you follow and eventually overtake an RE service, while passing tons of AI. The manifest freights are something to behold with all the different wagons that are represented. At the end there is even a stabling manoeuvre. I thought my Series S was going to CTD when I passed a 112 with a downloaded livery; the screen froze and I thought this is the one, but at the last moment my little console everyone loves to hate powered through. Take that reduced timetables! Once again thanks to Joethefish for all the amazing work and a job well done. He and others such as Liam are taking the old favorites of TSW and really giving them new life. Will post this also in the recommended services thread.
That br442 is so quite you cant hear anything and cant even open the windows. I thought could open them when it 1st come out.
No you do not. The ICE trains yield 65 points in non-LZB areas but only 35 points when LZB is active. Actually, I have only driven the 406 so far, so can't speak for the 401.
Weirdly enough, that seems to still happen, but only with the 406 now, ICE1 and Vectron just ran and got full 65 points? To summarize all else I've found still standing as of now: PIS at Langerwehe platform 1 does not work now. Fully blank. Plus Langerwehe platform numbers in the F9 map AND the PIS destinations shown there are opposites of what they should be. And 423 services from Deutzerfeld start outside the map. And one of the platforms at Ehrenfeld is mislabeled as Hansaring 4. Also a....very very weird issue...I have randomly inaccessible areas that seem to be invisible-walled triangular areas that come and go. One is roughly at the southeastern stairwell of platform 8/9, the other inbetween Hansaring station and the tower at the Koln depot entrance. I have zero clue what causes them to appear, and then sometimes go away seconds later. Perhaps the presence of a (specific model??) train at a S-bahn platform nearby? I'll have to check later. Sorry if it makes me sound insane lol EDIT: I have no idea what causes it. It does not seem to be train related. There is also a similar invisible wall appearing and disappearing just at the ends of platforms 8-9-10-11 towards the bridge. And if you happen to be within those areas on foot when it magically appears, you're stuck until it decides to go away. Perhaps it could be related to switches being set a certain way? That's the only constantly changing thing I can think of in the areas? Not sure how they'd be linked to invisible wall portions though...
dead BR 425 on my own creator scenario Durren to Koln with stops offered in scenario creator only for Horrem and Koln Ehrenfeld. The whole route seemed to be under LZB max 200 and 250 dropping to 140, 100, 70, but that ends shortly after Ehrenfeld at which point a sudden emerg braking occurs with a traction lock that even lok reset fails to clear. Nasty. Had a nice ride at 160 kph avg ( 158 actual max ) up to that point. First problem proved fatal. There was no chance to ack anything even tho doing under 60 kph at point of failure. Very vexing Xbox FAIL. Stop at Ehrenfeld had no issues.
I've been asking for this kind of shunting update for YEARS!!! Thank you!!!! Before trying any of these new activities, I reviewed all three of the available tutorials for the BR 363 Shunter. Despite this learning exercise, however, I've encountered one serious problem with this engine. Obviously, shunting requires multiple couplings and uncouplings, separated by yard movements. Two difficulties occur: 1. stopping the shunter accurately, and 2. starting to move again after picking up or dropping off a cut of wagons. I've found that this requires increasing the throttle to full, watching the shunter's wheels either not move at all or begin to move while hampered by wheel spin, decreasing the throttle to 0, repeating this seesaw process until the train actually begins to accelerate, and then reducing the throttle again as the train approaches the cut of cars to be coupled. In some cases, I found that I could press 3 to look at the last wagon in the cut of wagons already coupled to the engine, and then watching carefully to avoid slamming into the cut to be coupled -- this has typically required several attempts. So far, I've only been able to complete one run: 12:57 Stollberg GBF Shunrting in the Nahverkehr Dresden yards. Any suggestions will be gratefully appreciated. Thanks in advance and thanks again to the creators of these shunting activities!!!
After trying all the freight trains, I found that about five of them were sent to completely unrelated stations or bases.
PS4 version: I do not want to sound negative here and I know the route was released "by accident" on PS4, but there really are not many trains on it. In fact, if I run anything I hardly encounter any other services. Maybe a 442 somewhere. This is despite the fact that I had specifically installed all the German and French DLCs that were listed in the Dovetail Live article. Apparently, I am not the only one, as I have come across this playlist on YouTube by the content creator "saints rail 2.0" (kudos to him if he is on the forums). It shows a series of runs on the new Köln-Aachen timetable on PS4 and there is also not much going on. https://www.youtube.com/playlist?list=PLinhMg8tN8LtisaG2CqlEfGP6BEQP8mvj Again, I know this was an "accident" but it appears to have also taken away S-Bahn services on the old timetables. So a fix would be very nice. Thanks. Edit: just did a search and found that d.heal is the creator of the videos. Again, thank you for sharing your experience!
Is it prototypical for the br401 to have a max permitted speed of 200 km/h in the lzb zone ? Despite the line being perfectly capable of 250 km/h ?
I can't address how prototypical it would be, but this lower limit can be based on either the 401 having this limit or the cars it is pulling/pushing having this limit.
When coupling: stop 1-2 meters in front of the consist you want to couple to, apply the locomotive brake (direct brake) to about 1 bar (max) and apply power until the friction is barely overcome. Crawl up against the other consist (at less than 0,5kph) and as soon as the buffers (are about to) touch, idle the throttle. That way you won't bounce back and you'll stop exactly as intended to be able to couple. This procedure is done the same IRL.
PC Steam No mods installed I installed the BR423 add-on pack, but the timetable kept crashing so I uninstalled it to avoid that. So I'm sad
I was playing Köln - Aachen Revamp Vehicle: ICE1 (BR401 DB) Service: KWB DB ICE1 11 Car [Official] Schnellfahrstrecke: Kassel - Würzburg ICE545 Aachen Hbf to Berlin Ostbahnhof (start at 7:38, 38min drive) I'm not going to claim I'm very knowledgable about trains or the ICE1, i've run services with it before on other maps before and finished them successfully. The issues I ran into - At the first stop: I noticed the red G started burning, so I started braking. Even when I was slamming the brakes once it felt like there is no way I was going to make it the red G wasn't blinking whatsoever on any point that it would be achievable. It ended up going straight into emergency cos I wasn't going to make it before the red light - After the first stop: I'm not aware if I was late and ended up behind the cargo train because of that, but there was no way I was making the next stop on time. But along the way behind the train it happened multiple times that I had multiple green signals one after the other and then suddenly the next signal was RED. The first time I slammed my emergency brakes, and after starting the run again after a few green signals the same thing happened again, the next 2 signals were both red. I ended up just ignoring it and then the first red one turned green, and the next one turned yellow. EDIT: before the first red light popped up, everything was rather normal... green lights with a yellow behind it for beeing after that train. Until some point it didnt show yellows only greens and reds. EDIT2: So the orange lights are there "physically", but they don't turn red when I enter the block and they are not shown on the UI. - At the last stop there was no way I was going to make the stop again, the G went on, started breaking, even when I slammed everything to stop the G did not start blinking whatsoever and I didn't make the stop without it kicking into full emergency If the issue is me, then please ignore this, but as far as i've experienced how PZB works on other routes and my knowledge about signals this seems like the route is not concidering the time the ICE1 with 11 cars needs to come to a halt. Kind regards, Ata
Driving that service (Sifa-PZB-LZB-AFB On) and so far, I have made to the first stop in Dueren without any major issues. At the moment of departure there's an ICE3 in front of you on the line, but you end up having to wait not only for that to leave, but also a freight train to cross the entrance to Aachen in the opposite direction, so when you finally get a green the ICE3 is long gone and you don't interact with it anymore. Driven along as normal constantly at posted speed-5kph via AFB. At the LZB entry point circa 3km away from the Dueren stop, LZB kicks in, two seconds after it notifies of the red light at the soon-to-be-stop and starts braking. AFB braking alone isn't enough (or prototypically correct procedure) but a brake level of 2 I found enough to make the thing slow down and always stay just below the Vsoll speed target. You do have to brake a little harder towards the end because LZB would guide you to brake for the red signal but you need to brake for the platform end which is a bit earlier. I stopped in Dueren at 7:59, a minute late. After the stop, I can indeed see you get routed behind the rather slow freight train coming from behind you. This particular doesn't seem right...and it will absolutely impede getting to Koeln on time. EDIT: Finished it. You do get there very late, more than 10 minutes, because of being routed behind the freight train, but aside from that, I couldn't see any of the issues you listed.
As for the "orange lights being there physically" but not in the UI and that don't turn red when you pass, are you referring to these? If so this is a distant signal (Vorsignal) of the Ks signaling type and not a main signal, non-main signals are not shown in the game UI. Their aspect also only really references the next main signal, announcing if it's red (by being yellow), or if a speed restriction, or full line speed is to be expected after their successive main signal, but they don't represent a section start in themselves and as such do not change when you pass them. It may require you to PZB acknowlege it, if you're under specifically PZB (not LZB), but it isn't a main signal per se so the UI ignores it. In case it is one of these, go read a bit more on german signaling in general, especially chapters about Ks signaling, Vorsignale and Hauptsignale in general, and the shields (Tafeln) that go along with them. In this image the type of signal is conveyed by the white shield with black X being a Ne2 (Vorsignaltafel, indicates distant signal). I'd also read up more on PZB and LZB (which is utilized on this route and service too) if I were you, because I don't really get what the procedure you're describing to stop is, ideally you should attempt never to have the red G indicator blink. EDIT: That said, there IS a bug related to them on this route, and it is encountered on this service, but it is a different one. Sometimes you will notice one of these being yellow, but the next main signal (also on the UI) is also yellow. This is wrong, because the distant signal of a yellow main signal should be green. Only the distant signal of a red main signal should be fully yellow.
Also, sorry for the triple posting but this is back to feedback/unrelated to the previous two posts: What year is the timetable supposed to be set in? Asking because for example the train displays indicate 2023, but there's simultaneously drivable services like the IC 2222 of 2016-2019, the NJ 424 of 2020 and also that of 2021 on the same day, even the ICE 545 of 2009...
@TemporaryAI Thanks for all the information. I didn't know the signals was that much different as the UK ones so thanks for clearing that out. As mentioned I'm not that experienced so I don't know if the issue was me, however I do appreciate gaining more knowledge and understand About the red G, on another map with an ICE3 it was perfectly managable to "start braking lightly" if the G was fully lit and if it started blinking to increase the brake lever. But that wasn't the case this time All I can say at this point is that I did the run with other trains or with ICE401 on different runs and didn't really have the issue of not making the stop, and the train does feel a lot more responsive when braking. Maybe i'm just more carefull now I don't know. I did search more on German Railway Signals but I didn't really find any good source in English that explains things. I might understand German but not within a context that are not that common for me. This is probably not the place to ask but do you know any good and factual resource? The actual bug you explain might also relate to why I linked it to the UK system. :p [ MAP RELATED ] KAH ICE3M/BR406 DB (don't remember which one I actually took, sorry) - (ICE 11 Bruxelles Midi to Frankfurt) when you get to the higher speed piece of the scenario (Ü) there's some noise that doesn't seem right. also the UI gives a warning, when you enter the part where Ü kicks in, that you can enable PZB/LZB etc for more points but I had everything enabled from the start. I don't know if it is because there is an actual interaction with the PZB right when that happens and if this is intentional, but this is behaviour I did not have on any other scenario I played so far. KWG DB ICE1 11 Cars ( ICE 657 Aachen HBF - Berlin Ostbahnhof) right past indicator 24 when you're about to enter Berlin, the train seems to go trough the wall slightly and the pantograph goes through the roof of the small tunnel right after that. Kind regards.
