Page 1 of 1
| Doncaster (South) May - December 2014 19/01/2025 at 01:00 #159974 | |
Civolics
10 posts |
Hey everyone! Throughout the past few months, I have been pondering about trying my hand at creating my first-ever timetable for this game. Eventually, I've decided to go forward with my anticipations. A few days ago, I started working on a Doncaster (South) May 19th to December 12th, 2014 weekday timetable with just over 40 trains currently. While I am an amateur at writing timetables, I intend to make this timetable as accurate as possible. I have acquired the necessary tools to achieve this. However, I will need some help with a few things such as Freight train consists and lengths as well as UIDs that were used on Passenger and Freight routes at the time. Considering that I am from the US, I'm hopeful that I can be pointed in the right direction and attain some knowledge to achieve accuracy. Any feedback or tips is much appreciated. 
Last edited: 19/01/2025 at 01:05 by Civolics Reason: None given Log in to reply |
| Doncaster (South) May - December 2014 19/01/2025 at 12:27 #159975 | |
|
bill_gensheet
1446 posts |
Welcpme to the Timtablers Union :-) Obtaining UID that far back looks tricky, the usual databases don't go that far back and UID's aren't in the WTT either. However I would not get overly hung up on UID's, especially for a sim such as Doncaster South. You are unlikely to get a clash of ID's on most trains, maybe just light engines and there you can make up your own to ensure reliable use of rules and decisions. Keeping it logical will help a lot on debugging. For train 6A01 the light engine to work it would usually be 0A01 (likely unique too), the light engine from it either the next working (say 0B02) or a 0Z00 to depot which I'd give UID $LE6A01. You could also see what UID's are used now and produce logical but 'likely' equivalents. So as EC services are all C7xxxx, nothing too wrong in having C71001, C71002, ... for the up and C72001, C72002 for the down trains or whatever. It means a sort by UID on timetable editor will group the similar services for you. That contrasts with my current TT where every Euston - Watford was 2B55. I either have to make up UID's or to assign my own logical ID's, and chose the latter. I also tend to use UID to track trip workings through the day. So trip 20 progresses through $T2001, $T2002 etc while each leg is 0T20, 6T20, 8T20 etc several times over. The rules are then simple logical '$T2004 after $T2003' etc Doncaster area at that age will be well photographed, so a trawl through the likes of Flickr searching by ID will usually turn up a few examples of each train. Apart from making sure they fit the loops, and anything excessive is likely noted in the WTT, fairly generic trains will work quite well. 'Loaded coal', 'Empty coal' etc. Bill Log in to reply The following user said thank you: Civolics |
| Doncaster (South) May - December 2014 20/01/2025 at 01:13 #159980 | |
|
Civolics
10 posts |
Great! Thank you so much for the insight!
Log in to reply |