Hello everyone, it's been more than 3 months since I last posted. I had a big real life change with the birth of my first child so development did stop for a few weeks, but I have been happily developing the timetable further since November. I have done quite a lot of work: Reconfigured the timetable so it starts/ends at midnight (previously it started at 2am). This resulted in only one passenger service needing to be split in two parts, but provides the best guarantee that some nasty 'over midnight' bugs don't appear. The timetable is also completely "loop" proof: every service ends exactly at the same location it starts, so in principle one should be able to keep the timetable running for multiple days (has anyone actually tried this ever? ). Added the DB BR 101 Expert (and cab car) for some diverted/extra IC services (fictional, layer can be disabled). This required some extra attention as more modern traction like BR 101, 401, Flix 193, is not compatible with the MSB-route because there is a small section of track just outside Aschaffenburg Hbf that has bugged electrification (that doesn't give any issues while actually driving a service over it). Added Flixtrain services for a (fictional) Köln/Frankfurt-München/Innsbruck service, split in three layers that only run partially during a some months (I won't spoil too much here). Splits up the ICE services in 6 (or so) layers, enabling the BR 401, BR 403, BR 406 and BR 411. This provides quite a few opportunities to operate ICE services on the MSB, with a fictional stop at Lohr Bf. I have finally been able to let some services use the curve between Langenprozelten and Rieneck. Using this stretch of track previously resulted in a CTD, both in editor and in game. This came out handy for a few diverted passenger/freight services that were rerouted over the Fulda-Main-Bahn and MSB because of works on the Kinsigtalbahn (well known from FTF). I have finished the full 24 hours of banking services for the first banking layer, that will require DRA and RSN to be enabled. A second banking layer (with its own banking locomotive) will be added later, I am still considering what dependencies this layer will use. I have ditched my original freight layer (over 1000 services - including portal services) and redone everything properly with multiple layers. This means I have taken a step back, but the end result will be A LOT better. I have added all (virtual) destinations to the timetable, making all PIS-screens show the correct destinations and stops, both on platforms and trains. Because of this I have replaced the HRR BR 425 with the BRO BR 425. I have also replaced the MSB BR 146/Dostos with the FTF BR 146/Dostos, to get functional PIS screens. I think this version of the Dostos most closely resembles the Twindexx Vario trains that are used for these services IRL. I have checked and fixed all driving directions (I was a bit sloppy with this back when I started developing this timetable over a year ago), so every train runs with the correct light setup. I am currently fully redoing the RB88/RE87 (Maintalbahn) services because of the work on PIS and driving directions. Alas this has re-introduced the load/unload and couple instruction bugs that I encountered earlier. I have now been debugging this layer for the last two weeks, quite a frustrating task as an identical instruction sometimes works and sometimes doesn't. I have currently managed to get all services up to about 15:30 functional again, but there is 1 services that has been taking all my attention for the last week or so. I hope to release a first bèta version of this timetable in the near future. The BR 642 bug will define when I will be able to do so.
can´´t Wait for IT. MSB was one of my first TSW routes and I´m really a fun of these Modern Timetables.
Can't wait for this amazing timetable mod. When do you expect to release the beta version of it? Keep up btw!
I won't set a release date yet as I don't know how easy it will be to cook and pack the content for use in game. I'll keep you posted here. On a positive side: I have now been able to get the BR 642 services bug free again and have moved on to the last layer (2 available) of banking operations. Yesterday I've spent a lot of time adding the G6 shunter into this layer, for Hafenbahnhof operations that finish with a heavy train needing banking operations when it finally runs from Aschaffenburg Hbf towards Langenprozelten (where it joins the Fulda-Main-Bahn for its destination Leipzig). This should allow you to perform one continuous series of shunting operations at both Aschaffenburg Hbf and Aschaffenburg Hafen (and runs between them) between about 4am and 3:30pm, with only one hour where the shunter sits idle in a siding (ideal to have some food and stretch your legs if you take on the challenge of performing the full series without leaving the game). It was quite a challenge to weave this in all the other traffic that is already running up and down between Aschaffenburg Hbf and Hafen. In the end you'll be able to finish off the day by performing the mainline freight run where all the stock you've been moving around has to be moved towards the east by two (on the Spessartrampe three) Railpool BR 185.2's. Good to know: this layer will require MSB, FTF, DCZ, LFR and the Vossloh G6 shunter to function. If you don't have one of these addons, do look into them, they are fun! When this layer is complete (still a lot of other banking ops services to add), I only have to add the nightjet services (last passenger layer) and a lot of layers with freight services from different addons. I might release a first beta version before all freight services have been added.
Hi everyone, The timetable is getting pumped with freight at the moment. When my current layer is finished (mostly a combination of KWG/DRA/LFR stock manifest services with the RP Vectron and Dispolok 182), I plan on getting it cooked and packed for the first time. I do however have an important question: there are a lot of shunting services that require specific moves, coupling, uncoupling etc. I am experiencing more and more issues when simulating with PIE when I happen to start the simulation at a time where such a service is in the middle of an instruction to (un)couple or move to a specific shunt signal. It seems the simulation is started from that point and routes will be dispatched at that moment instead of having an overview of which signals are in what state, based on the datatrack. This results in services getting stuck in front of a closed shunt signal because the dispatcher is unable to clear a route from the specific location the service is. (e.g. the dispatcher CAN dispatch a certain route from a main signal, but is unable to do so if the train has already passed that signal and is in front of a shunt signal). I'm getting more and more anxious that this will result in a crooked timetable when playing in game, because there are so many shunt services that might break the timetable because it starts at an inconvenient time. Do I have to worry about this? How do others deal with this? The only solution I see is dispatching every shunt service from shunt signal to shunt signal with a lot of 'stop at's' and 'go via's'. But I have even seen it happen on regular services getting stuck in front of a shunt signal after leaving a portal... With PIE I can sometimes get the timetable running again by using the option to toggle signals via the map (there's a console command to enable that), but sometimes that leads to simulator crashes and is not available in game so it's not really a solution. I have a feeling that the MSB route is also not very optimised network wise, as I am unable to choose certain routes that should be available because there are tracks available. It's just that the route was not set up properly. Any insights on this issue?
For me it has always done that and thus I never was able to PIE test services apart from if they are on map or when I start the time 5 minutes or so before their spawn time. all services before PIE start on map don't start and those from portals I think all pour out at the same time or also don't. wasn't aware there was a way to have it work. For shunting around Salzburg I am yet to run into any breaking problem though just that the signals to split platforms do not work properly and the electrified turntable has a spot of no electricity. pathing issues are usually due to me setting the coordinates a bit off or not using the exact stop function
When you have modified stuff on the timetable after simulating, you have to enable 'ForceTimetableStartWithIncompleteData 1', when testing in PIE, then the services should run when they have valid datatracks, even if they start before your PIE start time. To be clear: my issue isn't that the timetable doesn't simulate in PIE or that some paths are not working. It is that functioning paths break when starting the game/simulation when they are in the middle of certain shunting moves.
