Page 1 of 1
|Key locations visibility suggestion 18/05/2019 at 20:40 #118368|
Noticed this is the shout box:
Edgemaster: Ben: It's not documented very well, but there's two types of locations, some won't validate even though adjacent. You need to keep going back (or forward) until you find the next 'Key' location in the sim. These are usually junctions or stations.
Edgemaster: It can be quite awkward to find them by hand. Usually following existing timetables as an example is useful
Edgemaster: Ben: The mandatory timing points for Edge Hill are listed in the sim manual: <<link>>
BenWright: "Entering trip must specify at least one key location"
Steamer: Roby is not a key location- keep timing points until you reach one (either Olive Mount Jn or Bootle Branch Jn will do it).
GeoffM: Have a look at the included timetables as examples of valid next locations.
Would it be possible / worthwhile for key locations to be shown in bold in the timetabler location list box or similar ?
Not sure if I see this in Windows drop down lists often enough for it to be a permitted function.
Log in to reply
|Key locations visibility suggestion 18/05/2019 at 21:11 #118370|
jc92 in post 118369 said:
agreed. I've had this issue where the key locations in a sim are different to the WTT due to era differences.Depending on how the developer writes the Path file for the sim, it's possible that every location could be a key location, but, that does not mean that you can timetable between any two locations.
I suspect rather than a list of key locations, the comments in the post are more asking towards a list of valid paths between various locations.
For example, one of my smaller in development sim, Every location would be considered a mandatory timing point, but there'd be no point listing that, as it wouldn't mean anything as every location would be noted, yet, mentioning that there is a path Location A -> B and C, and paths B -> D etc would make more sense for timetabling purposes.
Log in to reply