Creation Sharing 2024 München Augsburg Timetable [beta V0.8.4]

No Speed limit override. Both service nodes have identical information, aside from name and timings. From testing in the PIE, I determined that ICE 699, with the dependency setup for the Munchen-Pasing stop instruction, experiences the 200km/h LZB limit, but ICE 987 does not suffer this issue (same instructions, without call on dependency). I guess I'll keep troubleshooting.

 

Okay, the 200 km/h issue has been resolved by moving the last go-via before the stop instruction outside of the LZB 200 km/h detection range. I have no clue why it does this, I have some guesses but no concrete answer. This solution unfortunately has its restrictions: Due to the last go-via being 13 km upstream from the regio/fernvehrkehr merging point, a train on the highspeed line may be held at a signal far out (13 km) due to the regional service ahead in sequence not having reached the dependency instruction yet. I haven't encountered this yet as I haven't rerun the full timetable, but if this becomes an issue, I'm not sure what else I can try. This also doesn't properly simulate real LZB functionality but again, I'm not sure what else to do. This is also only an issue for a handful of services that require dependency, so it may not be that critical.

On another note, I now start on my most dreaded task: shunting movements for ICE services. Based on satellite imagery, I've determined that there are four common siding areas for ICE formations to sit while they await the next service:

1. Laim Sidings [North]
   Mostly ICE trainsets. This is likely for longer rest periods given the distance from the Hbf. Accessible from all platforms.
2. Hirschgarten Sidings [North]
   It seems like a mix between different vehicle types, so maybe I reserve only the bottom half for ICE consists
   Accessible for trains from platforms 14 and up.
3. Donnersbergerbrucke Sidings [Central]
   Mostly ICE trainsets, with some occasional diversity. Used for short turnaround times? Accessible from platforms 14-26.
4. Donnersbergerbrucke Sidings [South]
   Another mix of formations. Used for short turnaround times? Accessible for platforms 5-21.

Before I get started on this guessing game, does anyone have any resources/tips/knowledge on typical movement patterns, typical sidings, which services are paired with the same trainset, etc.? Cheers.

 

I can't give you anything on the train movements sadly.

To clear stuff a bit

1. Laim: The tracks in question are 801 - 810 and are used as storage for ICEs (München-Laim Rbf, Bft ICE Wende- und Abstellanlagen)
2. That's München Hbf Vorstellgruppe Nord (Track VN501 - VN514) and is used by all different EVUs to store and prepare trains, ICEs from the storage towards Hbf have to pass through
3. 1HW - 4HW I assume short term storage, used by mostly FV and GaBy afaik.
4. Vorstellgruppe Süd, again used by different EVUs.

Missing: 1PV - 4 PV which are at the end of the tunnel from Vorstellgruppe Nord, they are used to store trains for a short time or to line them up, as well as by Länderbahn and DB Regio for Loco Change and/or shunting of their locos and formations for RE2; RE23 and RE25

You can use https://trassenfinder.de/ to get track plans of the stations, maybe that helps.

 

I don't think there's a simple overview or anything, but what you can do is open München Hbf on bahn.expert/. Turn on "UIC Number" and turn up the lookahead/lookbehind times in settings, filter down to just long distance trains, and then it'll give you the actual vehicle number for any train arriving or departing München up to eight hours before and after the time that you're looking at. Make a list of all the trains you have, write down the vehicle numbers and you'll be able to pair them up accurately.

 

https://www.fernbahn.de/datenbank/suche/ would be another option, search for Zuggattung ICE and filter for each Train type, ICE 1, etc., go through the list and try to figure out which combination works, as it gives you previous and follow up service(s). Not sure how accurate it is.

 

Since it has been a week, I will provide a short update on progress. Busy with life, but managed to extend the S1, S2, and S6 to represent their entire 24 hour timetable. This is what the S2 timetable looks like now:

After looking through the resources that were provided by gesingus and mkraehe, I have put the ICE shunting task aside. I want to get the shunting done all at once, not having to stop halfway through, so I will continue to build the full 24 hour timetable for all services before developing the shunting movements. Here's a final screengrab to wrap up this post:

 

Radio silence for the last two weeks, but fret not, there has still been some background progress. I finally finished condensing the full Munich Hbf timetable into an excel spreadsheet to identify which inbound/outbound services can be paired together, and which ones will require shunting to the yard. Here's what a full typical weekday looks like (Green means it has been implemented in the timetable, yellow is missing shunting movement/connected service pair):

Unfortunately, due to the restriction at Donnersberger Brucke established a while back in this thread, there will be no services at platforms 33-36. I contemplate adding static vehicles at these platforms that remain parked 24/7 to give the feeling of a busier station.

Now that this spreadsheet is complete, I can proceed with creating the full 24-hour timetable for regional and intercity services. I also have a quick video in the works, to showcase the busy S-Bahn trunk line.

 

If we don't have all the DLC will we still be able to play but just without these services, or is every train a requirement. I would love to use this new timetable but I don't have the 612 and possibly other DLC's.

 

Each DLC will be added as a layer, just like existing timetables by DTG (i.e., if you don't have any DLCs other than Munich-Augsburg, you can still play/see S-Bahn services and ICE3 services, but no other services would appear. If you owned all DLCs except the 612, you'd have access to all services except those with the 612).

 

Thank you very much for this clarification.

 

Cheers mate, you've been doing an amazing job! I'm from Munich, and I'd love to see a more realistic timetable in the game. You've made incredible progress, but if you need any assistance, I'd be happy to help

 

Here is my obligatory weekly/biweekly update (in the form of an image to save space):


Green is what I've worked on since my last update. Orange is work in progress. The last two weeks have been 60-hour workweeks, so I'm taking time to rest. Should see more progress in the coming weeks. Aiming to finish S-Bahn services next, followed by regional services.

ChrissNIET A list of all ICE services and associated formations/train types would be great, there are a couple of resources further up in this thread. It's still something that needs to be done before I can properly code all 24 hours of ICE services as it'll allow me to determine service pairs for outbound-inbound-(shunting)-outbound trains. Send me a PM if you're interested.

 

Progress:

All S-Bahn services are now complete, there remains to be some fine-tuning after testing, but the tedious data entry for those services is complete. Also, thanks to ChrissNIET, significant progress on ICE services has been achieved. You may notice that RE4/40 services remained as WIP. This is due to the uncertainty behind shunting movements, something I'll get to after finishing ICE services.

I wonder if DTG would ever consider adding destinations to the station directory (and other issues mentioned in this thread while were at it)... the majority of station PIS signs display inaccurate destinations, which is especially awkward with S-bahn services (S3, S4 excepted) "destined for Hackerbrucke". Here's hoping

 

That's some good news.

For München it would be RE4 and RB40, RE40 is Nürnberg-Regensburg
Is there any specific issue with the shunt moves?

 

Seems to be put in onto the map. I put a 648 in free roam on Salzburg-Rosenheim and had Budapest keleti and Verona or Roma termini. the destinations for RJ and existing EC trains on the route. I'd say if they had a general database for destinations for locations like Fern, Nach and Sbahn verkehr trains that works on every route and train

 

A Lint?

 

I keep messing those numbers up. I meant a 642 desiro classic

 

Just the sheer amount of moves. The RE4/RB40 have many extra peak services, so formation utilization would be pretty poor (i.e., I'm looking at possibly 8 formations for 40 services, of which 6 are expected to sit in the yard most of the day).

Since MAG is a pretty old route, the destinations are cooked with the map. Below is a list of all the destinations that can be displayed in station PIS. I have no intention of modding the map, as I want this timetable to have no dependencies on other mods.



On another note, look at all these Dostos parked away nicely.

 

Aren't the destinations cooked into every map?

 

My point still stands, station directories aren't shared between maps.

 

I wasn't arguing against your point...

 

Did you experiment with “unload all” instructions on depot moves?
I played around with this, seemed like you had to set the “by percentage” to 0 and set manual start/complete times. Which I thought would be tricky but the service wouldn’t end until the unload completed. Can’t remember what happens if you arrive late, I think it just ends when you open the doors. Otherwise I think it worked with AI after simulating.

 

I presume this is referencing the door issues I was facing with the Dostos a couple of months ago, this has been resolved since. I will keep this in mind if I encounter the same issues.

The last two weeks have been slow progress on the ICE services, the manual entry of all services has been an arduous process, but I have coded all arriving services, and I'm at 18 hours out of 24 hours of departing services.

I have a question for anyone who may have worked with the ICE in TSW4: How does the onboard PIS work? It seems I should use "BP MAG DB ICE3 ServiceDataDestination", which gives me these three variables:
Now I wonder, what do I enter for each? The service number is straightforward, but I wasn't sure what I have access to (similar to the restrictions on the SBahn). I did some snooping around and found this:

So now I'm curious, is there a way to somehow list multiple stops on the PIS? I guess final destination displays are limited to these destinations, but can I put in more than one "Initial destination" (i.e., multiple of the westbound/eastbound stops listed below)? Thanks in advance!

 

Its time to wake up this thread, I guess. I have had a busy couple of weeks (again), but I was able to get back to the timetable in the last few days.

Notable progress includes RB68, RE70, RE72, RB74, and RE96 services now have 24-hour services. IC 24h timetable is also complete, I am spending some time trying to get some BR101 shunting movements working, i.e., drive the BR101 from the yard to the Hbf, connect to the back of a BR101+7car, and then uncouple the front BR101 from the consist. Up next, Regio 1/16/2/3/33 services, and hopefully Regio 87/9 services too.

Late night intercity testing:

 

I've managed to get the coupling/uncoupling services for the BR101 working (albeit with a few quirks). Here is a video I quickly put together with two sample shunting services and a little sight-seeing in-between.

 

Nice work! Coupling movements sometimes need some quirky instructions indeed. It seems your first 'stop at' instruction still has 'overlap' selected instead of 'within'.

A hint for more realistic and smoother coupling: stop a meter or so in front of the formation, set the independent brake (locomotive brake) to 1A or B and release the train brake. Then, with the independent brake still set, apply the throttle to barely overcome the brake friction and reduce it as soon as you touch the buffers. This way you don't have to simultaneously apply the brakes and reduce the throttle and your locomotive won't bounce back. I have no real life experience myself but I came to understand it is done this way IRL too.

 

Today's update:

"Wow, is that the BRB RB 58?"
Why, yes it is!
"But Vindicity, how did you do this, I thought you said it was broken!"
I lied (Aka, ChrissNIET helped me find a loophole in the pathfinding). Long story short: I needed to end the service just past the last signal on the flyover, and then create a new service that continues into Donnersbergerbruecke. The NPC driving is a bit goofy as the train comes to a halt on the bridge between services. However, if you drive the service yourself, TSW4 will maintain whatever momentum you had between services for an almost seamless transition (aside from being forced to the end-of-service screen/overlay, just press "continue in free mode". Maybe I'll upload a video showcasing this later.
Progress:

All the RB58 services are complete, finishing up on the 55/56/57 now.

 

This is looking epic!

Long-lead item: TSG say that the BR 420 will be released for "another" route instead, but that it will come also with the München variant (refurb, LZB). Could this slot into your TT when it appears?

In general, it would be nice to have a listing of which services are covered by what rolling stock. (As a placeholder, I would consider using 1116/OBB coaches on the RJ/RJX services, until such time as DTG give us a real RJ. At least they're distictly Austrian!)

 

Thank you very much for this work. MAG is still one of my absolute favorites, and I am really looking forward to the Timetable Mod. Great work and have fun building this timetable further.

 

Looks Great, but I have a question: Why are the Austiran S-Bahn Trains in the back?

 

Those are substitutions for Alstom Coradias. I think the Stadler FLIRT would be a better option though tbh.

 

The Luzerne RAB 525 is a FLIRT

 

exactly

 

I still haven't found out how to get the destination display of the BR423 showing blank for my own timetable. I have sent you a DM, have you seen that?

 

Here's a high-level overview of all formations used for regional services, they are subject to change.


At this time, I have no interest in purchasing the 1116 or 525 as I have no intention of playing their routes and the price tag is not within my budget. If there are good upcoming sales, I may purchase them then. Perchance.

General progress update: I have split the regional 2/25/3/33 into 3 different formations, previously it was only Dostos running the route. This required a minor overhaul, but the 24-hour timetable for those services is almost complete.

 

Which of those IRL are DB and which private TOCs?

 

Good to hear there is progress going on. Wish you all the best for the remaining work.

after seeing the list, I notice there are some things, which don't fit on the 2024 timetable. Hope it is okay, if I put in a list (should have done this a lot earlier) with my observations (not 100% accurate, because I put things together with the route map and what I know) and suggestions.
As München is the only station in the game I am regularily, I am probably a bit to much into having it 'right'

 

"Private" as of not state owned only Westbahn
NE-Bahnen:
DLB -> FS
BRB -> CDC
GABY -> ÖBB

 

Alright, some more behind the scenes progress this week, including some troubleshooting on RB58 services... although check this silly video out (you can thank vircom):

Thank you for this, there may have to be some sacrifices made for performance (i.e., where using a different, similar(ish) formation would cut half the formations required, drastically improving performance. Overall, good resource though, thanks!

 

Thank you for the update.
As much as I'd like to see all the different vehicles and formations, I understand the need to sacrifice some for performance reasons.
RE3 alone has min 8 formations running around, so like 5 needed ingame to capture that in detail, just for on AI line, when in the end 2 Formations shared with RB33 would do the job.
The one thing I'd realy appreciate is stuff luke the loco run arounds, exchanges and shunting done on the RE2 Trains or the RE23 and RE25. Or adding/taking away one EMU from HVZ Formations, as that's the stuff that makes München Hbf come alive with those yards outside the station.

 

Hi, I wanted to ask if you will release a pre-release version of the timetable, or will you release it, when its finished?

 

Good question, I am considering releasing a "beta" version for those interested as a test. Given the sheer amount of services, it would not be effective to test every service myself (nor do I have the time) so the beta could help speed up the process... still unconfirmed at this stage though.

On another note, I have just returned from a 3-week vacation in Munich, so there has not been much progress since. I am hoping to pick up the pace again very shortly.

 

Sounds good! I hope you had a great time in my wonderful hometown of Munich.
Anyway, take your time and if you release a beta, let us know.

 

Update: Most of the ICE services are now coded, including ICE1 trainsets. Next, a large chunk of time will be dedicated to debugging and resolving pathing issues. See screenshot below of a busy Hbf at 7 AM.


ICE1s and ICE3s parked away at Laim:

 

Wow! That's how I like to see MH

 

Progress continues on debugging and other work... fear not, I have not abandoned the project

full length s-bahn services are now included on select peak hour routes (pic above: S8 Germering-U.).

Currently encountering issues with IC services not being able to open doors at platforms after being coupled to a new BR101... it seems that generally when I use/create new formations, load/unload instructions struggle (Weirdly enough, the AI service is able to open the doors in PIE, just not when simulating the timetable... awkward hiccup). I will continue debugging.

Munich Hbf approach is looking busy.

 

Nice work!

I've encountered this numerous times, also the other way around: timetable simulates but load/unload breaks during PIE. It's a big PITA. I have no idea how te reproduce or reliably fix it.

 

Also got this same issue with my RSN timetable, set up a template timetable and it simulated all fine. Copied it to make it a full 24 hour timetable for that layer and it immediatly breaks on one of the first services that previously simulated just fine with the "trigger door lock state" error. It would be nice to find out if DTG have some workaround or fix for this in their own timetables.

 

Something I have just discovered, having spent several hours trying to fix the door issue, is manually setting which side the doors need to open has fixed my problem. In my case I had to select both sides due to the issue with n-Wagen doors not working on RSN.

 

I have tried:

• setting the opening side to both doors, left, right, auto - nothing.
• switching platforms - nothing.
• offsetting the STA by X seconds (to avoid multiple instructions being processed simultaneously) - nothing.
• changing the prior go-to instruction to an exact stop - nothing.

When I hop in PIE and play, it looks like the service arrival markers are backward (arrow for direction of travel, dotted line for wagon markers). I feel like this may be a side effect of coupling the back of the BR101 loco to the back of the full formation... however, the service recognizes the formation in the correct direction (see second image).


For context, here are the full couple-uncouple instructions at Munich Hbf if anyone has any pointers, at least I know not to end a service with an uncouple instruction. Feedback is appreciated