Example of a Timetable file

[=FI=Ghost]

Hello,

I've never taken a try at learning how to make proper activities for MSTS/ORTS. I would, however, like to try with something simpler. Right now, I am interested at learning how to populate a route with static trains and/or cars. They don't have to be drivable. I just want to see some locomotives and cars while driving through railyards etc.

I've tried doing that using the default MSTS Editor, but for some unknown reason, I cannot open it. So, I guess I am stuck with ORTS Timetable editor. I've looked through the attached Manual, but I just can't seem to get it how to place static locos on the route.

That is why I am asking if anyone has a Timetable file that already contains static locos and cars on the route, and is willing to share it with me. I believe it would help me to get the hang of this.

Borislav

[rober]

Hi Borislav

Try Rob Roeterdink's Demonstration Timetable over at Elvas, it's in the General Feedback Area.
Even if not a member it can be downloaded straight off the page.
BE WARNED; it is very comprehensive.

Good Luck Bob

[scottb613]

Hello,

I've never taken a try at learning how to make proper activities for MSTS/ORTS. I would, however, like to try with something simpler. Right now, I am interested at learning how to populate a route with static trains and/or cars. They don't have to be drivable. I just want to see some locomotives and cars while driving through railyards etc.

I've tried doing that using the default MSTS Editor, but for some unknown reason, I cannot open it. So, I guess I am stuck with ORTS Timetable editor. I've looked through the attached Manual, but I just can't seem to get it how to place static locos on the route.

That is why I am asking if anyone has a Timetable file that already contains static locos and cars on the route, and is willing to share it with me. I believe it would help me to get the hang of this.

Borislav

Hi Borislav,

I could send you a simple one tonight (EDT) - the best way to do this is to use the tool in the ORTS Interface to build it... It's pretty cool - as you can make a separate timetable that has your placements of static consists all over your route - then just call it from a different timetable you use for all your AI... So if you take the time to set one up right - you could get a great deal of use from it...

Regards,
Scott

[=FI=Ghost]

That sounds great, Scott! Thank you.

Thank you, Bob, as well! I'll give it a look.

[scottb613]

That sounds great, Scott! Thank you.

Thank you, Bob, as well! I'll give it a look.

Hi Borislav,

Very simple timetable - "test" has AI Traffic which calls "static" and "static" is all static consists...

Both in attached zip...

Hope this helps...

Regards,
Scott

SCO_TT_Static.zip

[=FI=Ghost]

Thank you very much! I will try it out tomorrow.

[gremlin1812]

G'day Scott, I have been watching this and thought I might give it a go but I find that I am missing two consists, they are
"SCO_BM_482_x35mix and SCO_LC_HopperX5_MT". Any help to fix this would be appreciated.
Regards
Barrie

[scottb613]

G'day Scott, I have been watching this and thought I might give it a go but I find that I am missing two consists, they are
"SCO_BM_482_x35mix and SCO_LC_HopperX5_MT". Any help to fix this would be appreciated.
Regards
Barrie

Hi Barrie,

Oh - sorry - this wasn't intended to actually work for anyone - it was just a simple example of how to make both an "AI Timetable" and a "Static Consist Timetable" (how the fields are structured in the spreadsheet) - - - you would need the same route - same paths - and same consists defined on your system - for this to work as is... While this does work on my machine - because all those are defined - this was just a test setup by me to test out some of the features of Timetables - this is nothing really useful...

To start a simple Timetable - pick a route - create (2) paths - have (2) consists - then open the Timetable tool from the ORTS menu - I can help you from that point forward... I only know some of the very basic functions of this feature - I haven't gotten into the more advanced stuff yet...

Regards,
Scott

[=FI=Ghost]

Hello, Scott!

I've taken a look at the Timetables that you sent me. I think I understand the whole system a little better now, but I have a few questions.

Screenshot 1:

1. If I understood correctly, each column in the spreadsheet represents one consist, static or AI. Is that correct? So, if I want to place 20 different static consists on a single route, I would have to have 20 columns?

2. What does the comment column represent?

3. Why are those station names present on the spreadsheet?

Screenshot 2:

1. What exactly is the "Path"? A physical location of a given consist on the route, or something else?

2. Do I have to check the option "Show Static Trains" if I want them to be visible on the route?

Untitled-1.jpg
Untitled-2.jpg

[scottb613]

Hello, Scott!

I've taken a look at the Timetables that you sent me. I think I understand the whole system a little better now, but I have a few questions.

Screenshot 1:

1. If I understood correctly, each column in the spreadsheet represents one consist, static or AI. Is that correct? So, if I want to place 20 different static consists on a single route, I would have to have 20 columns?

2. What does the comment column represent?

3. Why are those station names present on the spreadsheet?

Screenshot 2:

1. What exactly is the "Path"? A physical location of a given consist on the route, or something else?

2. Do I have to check the option "Show Static Trains" if I want them to be visible on the route?

[ATTACH=CONFIG]76925[/ATTACH]
[ATTACH=CONFIG]76926[/ATTACH]

Hi Borislav,

I'm by no means an expert on this topic - so please take anything I say with a grain of salt (I could be mistaken)...

1-1: Yep - sounds like you have that right - each consist is placed in its own column... Just click the add column button to add a new one...

1-2: The most right column need to be a comment and needs to contain the name of the Timetable...

1-3: I believe Timetables were originally designed for passenger traffic - so the station are represented - if you put an appropriate time in the respective field - a passenger train will stop at them - leave them blank and it's bypassed... I use this mostly for freight running AI myself - so most times I leave them blank...

2-1: A PATH goes back to the earliest days of MSTS - all trains - AI and Player have a PATH defined to run on... It provides a starting point and end point while positioning all the switches appropriately... In ORTS "Activity" mode - if you have the "Advanced Shunting" enabled - you can do all kinds of incredible things with paths such as having yard switchers making up or breaking down trains - road engines trundling out to grab their assigned train then heading off to their destination - helpers automatically attaching for a shove over the hill and automatically detaching when their job is done - locals picking up and dropping off cars along their assigned route - AI horn blows - trains doing actual work - all this - while under AI Control - WITHOUT user intervention... The best way to create a path today is to use the ORTS Track Viewer tool and create paths there...

For Static Consists - the Timetable editor will automatically create a very short path to place a loose consist on - without you having to do it manually - you have to know the siding name for placement with this tool... You can go create your own paths if preferred...

2-2: No - it's just a filter for use in the Timetable Tool window - if you use the appropriate naming convention for loose consists - it will remove the loose consists from the list to make the consist you're after easier to find...

Regards,
Scott

[=FI=Ghost]

I have managed to put some static consists on a route!!! Thank you very, very much, Scott!

I think I am going to have to learn to make a path for my own train. I tried just putting it on the route. The train does show up and it runs well, but the Track Monitor shows only zeroes.
Open Rails 2019-05-29 04-56-54.jpg

[scottb613]

I have managed to put some static consists on a route!!! Thank you very, very much, Scott!

I think I am going to have to learn to make a path for my own train. I tried just putting it on the route. The train does show up and it runs well, but the Track Monitor shows only zeroes.
[ATTACH=CONFIG]76945[/ATTACH]

Hi Borislav,

Happy to help - glad it worked out... Not sure on the all zeroes ?

Yeah - in my book - creating PATHS is an essential skill...

Just open "Track Viewer" for the desired route - add the "Meta Data" for the path - add start and end point - the SAVE - you will have your own simple path... There's a help document for Track Viewer included with ORTS that's pretty comprehensive - it's under the "Documents" button - review same - as it will provide all the specifics...

Regards,
Scott

[roeter]

Hi Borislav,

I'm by no means an expert on this topic - so please take anything I say with a grain of salt (I could be mistaken)...

1-1: Yep - sounds like you have that right - each consist is placed in its own column... Just click the add column button to add a new one...

A column in a timetable can always only contain the definition of just one train, so indeed each train (static or otherwise) requires its own column.

1-2: The most right column need to be a comment and needs to contain the name of the Timetable...

The first field (top row, leftmost column) must be empty, the first non-empty field in both row and column must be set to #comment, and the field at the crossing of this first #comment row/column must be set to the timetable name.
The reason for this fixed layout is that it allows the program to identify the fieldseparator used in the timetable file. What character is used as field separator may depend on the used tooling, the method of saving and certain user system or program settings.
OR can now determine the separator automatically, otherwise it would have been necessary to have it defined as user input.

1-3: I believe Timetables were originally designed for passenger traffic - so the station are represented - if you put an appropriate time in the respective field - a passenger train will stop at them - leave them blank and it's bypassed... I use this mostly for freight running AI myself - so most times I leave them blank...

Not quite - but here in the neck of the woods where I live everything runs to a timetable, freight trains just as well as passenger trains. The whole idea was that if in real world everything runs to a timetable, why should that not also be so in OR? The rest is history ...

2-1: A PATH goes back to the earliest days of MSTS - all trains - AI and Player have a PATH defined to run on... It provides a starting point and end point while positioning all the switches appropriately... In ORTS "Activity" mode - if you have the "Advanced Shunting" enabled - you can do all kinds of incredible things with paths such as having yard switchers making up or breaking down trains - road engines trundling out to grab their assigned train then heading off to their destination - helpers automatically attaching for a shove over the hill and automatically detaching when their job is done - locals picking up and dropping off cars along their assigned route - AI horn blows - trains doing actual work - all this - while under AI Control - WITHOUT user intervention... The best way to create a path today is to use the ORTS Track Viewer tool and create paths there...

And nowadays timetables can do all that as well - and even more. And the best thing of a timetable is : one day all that shunting may be observered as it is handled by AI trains - next day you can select it as player train, without the need to create another timetable.
The main basic rule for timetables is that all (driveable) trains can be either AI or player, depending on the player train selection. It should not matter to the flow of the timetable which train is selected as player train.
This does lead to some restrictions. For instance, it is not possible to switch the player train to Manual mode, run it into a siding and drop off or pick up some wagons by defining the action in a 'worksheet' but without setting all details in the timetable, as would be possible in an activity. The reason is that obviously AI trains cannot read the 'worksheet', so the flow of the timetable would be different if a particular train was selected as player train. All actions, including all attach/detach etc. actions, must be explicitly defined in the timetable and will take place automatically when running.

For Static Consists - the Timetable editor will automatically create a very short path to place a loose consist on - without you having to do it manually - you have to know the siding name for placement with this tool... You can go create your own paths if preferred...

Indeed, everything in a timetable needs a path. Some items need paths even without trains defined directly to use them, e.g. pools.
In general, a timetable needs more paths than an equivalent activity. The trackviewer is a great help in this, it is far more versatile than the 'old' MSTS path editor.

2-2: No - it's just a filter for use in the Timetable Tool window - if you use the appropriate naming convention for loose consists - it will remove the loose consists from the list to make the consist you're after easier to find...

Regards,
Scott

As for all zeros in the track monitor : that has nothing to do with the timetable. The trackmonitor is basically identical for timetable and activity mode. Signalling and rolling stock behaviour is also exactly the same, except that some items are not (yet) implemented in timetable mode, like opening doors and freight car loading/unloading.
There are some differences in some aspects, e.g. handling of reversal points and station stop processing (timetable does not use 'number of passengers' as defined for a platform).

Regards,
Rob Roeterdink

[scottb613]

I have managed to put some static consists on a route!!! Thank you very, very much, Scott!

I think I am going to have to learn to make a path for my own train. I tried just putting it on the route. The train does show up and it runs well, but the Track Monitor shows only zeroes.
[ATTACH=CONFIG]76945[/ATTACH]

Hi Borislav,

Well now you have it straight from the guy who designed and implemented the feature...

A column in a timetable can always only contain the definition of just one train, so indeed each train (static or otherwise) requires its own column.

The first field (top row, leftmost column) must be empty, the first non-empty field in both row and column must be set to #comment, and the field at the crossing of this first #comment row/column must be set to the timetable name.
The reason for this fixed layout is that it allows the program to identify the fieldseparator used in the timetable file. What character is used as field separator may depend on the used tooling, the method of saving and certain user system or program settings.
OR can now determine the separator automatically, otherwise it would have been necessary to have it defined as user input.

Not quite - but here in the neck of the woods where I live everything runs to a timetable, freight trains just as well as passenger trains. The whole idea was that if in real world everything runs to a timetable, why should that not also be so in OR? The rest is history ...

And nowadays timetables can do all that as well - and even more. And the best thing of a timetable is : one day all that shunting may be observered as it is handled by AI trains - next day you can select it as player train, without the need to create another timetable.
The main basic rule for timetables is that all (driveable) trains can be either AI or player, depending on the player train selection. It should not matter to the flow of the timetable which train is selected as player train.
This does lead to some restrictions. For instance, it is not possible to switch the player train to Manual mode, run it into a siding and drop off or pick up some wagons by defining the action in a 'worksheet' but without setting all details in the timetable, as would be possible in an activity. The reason is that obviously AI trains cannot read the 'worksheet', so the flow of the timetable would be different if a particular train was selected as player train. All actions, including all attach/detach etc. actions, must be explicitly defined in the timetable and will take place automatically when running.

Indeed, everything in a timetable needs a path. Some items need paths even without trains defined directly to use them, e.g. pools.
In general, a timetable needs more paths than an equivalent activity. The trackviewer is a great help in this, it is far more versatile than the 'old' MSTS path editor.


As for all zeros in the track monitor : that has nothing to do with the timetable. The trackmonitor is basically identical for timetable and activity mode. Signalling and rolling stock behaviour is also exactly the same, except that some items are not (yet) implemented in timetable mode, like opening doors and freight car loading/unloading.
There are some differences in some aspects, e.g. handling of reversal points and station stop processing (timetable does not use 'number of passengers' as defined for a platform).

Regards,
Rob Roeterdink

Hi Rob,

Thanks so much for taking the time for the detailed write up and all your development work on same... Yeah - I'll have to dig deeper into TT operation - I didn't realize you could do all the advanced shunting features in TT Mode - as in Activity mode they are all based on "wait points" and wait points seemed to have limited use in TT Mode - and I tried the simple AI Horn in TT mode and it didn't work... I know you created some advanced examples with your latest update - I just haven't had a chance to go through them yet...



Regards,
Scott

[=FI=Ghost]

Thank you all very much!

I now have a basic understanding of the Timetable concept in ORTS.