[Weter]

Hello.
Just a preamble:

Spoiler

I interested in learning timetable definition.
During last three years I have started some TT projects, so I already know something.
For improving my skills, I have translated the 11-th chapter of Manual, dedicated to timetables.
But I'm sure, that the best knowledge is based on collective experience: this means the discussion.
So I'm offering to follow the way of timetable design together. I'll tell, what I know, and maybe someone would share his opinion, or offer some solution.
Hence, I'm expecting, many of us would gain. So, let's get started.

The matrix:

Spoiler

Just some days ago, I have downloaded the route, that interested me; installed that and have performed some explore rides.

That route was built with some ambitions to reproduce real-life railroad; it looks good, being well-decorated with authentic object models, has interesting and quite complex trackwork. And, what is essential-it reproduces the railroad system's piece, used for busy commuter traffic from the Capital center to nearest suburb town. But it combines intensive long-range intercity, mainline and local freight operations and technical traffic of passenger consists/commuter EMUs as well.
Furthermore, since this is real-based line, the prototypical timetables are available, either modern or historical. And numerous of RR-simmers maybe familiar with that specific, for instance, due to living there. All this is giving to me a good amount of hope on some interest and feedback.

The task:

Spoiler

We will start new timetable for the route, which I didn't know before, and go through each of stages from the very beginning.
I'll try and use the pole function for taking in account and display the average opinion about key questions, so everyone will have an opportunity to influence the development process. We would try to find the best ways of dealing with questions and issues of the process. Now, what if we try?

[Weter]

So, I have attempted first steps.
Before starting timetable defining itself, some route's bugs shall be fixed.

As not every platform was defined the right way, I at first, made revision of the route with TSRE and entered missing names for platform markers.
Also, I've corrected some lengths of markers for matching given platform models.

[Aldarion]

Yes. That kind of fixes are necessary for making a timetable work. I'm making a list of fixes I have to do with my older portuguese routes to be able to make a working timetable for those routes.

[Weter]

There is misaligned track there too. I'll need to fix it with TSRE next time: then freight operations will became possible.

[Aldarion]

will you be sharing it for download?

[Weter]

Hi, Rui.
Sharing what?

[Aldarion]

the timetable.

[Weter]

Of cource.
See post one.
It is being planned as a conference for experience-exchange, so material exchange is the part of that plan.

[Aldarion]

right. cool

I hope to be of some assistance since I got a pretty good experience with timetables. I still ahve some things to discover myself. For example, I am not always sucsessfull in sending trains to pools...

[Weter]

Yes, that is need-to-investigate...
But this route have only few tracks for making pools... But 120a gives to me wide opportunity for practicing that.
So, after basic/simple things, we can focuse on pool operations.

[HookitandBookit]

I've read somewhere that even just touching a track piece with TSRE destroys the track.db of that route. Because of that i have been very afraid of trying to fix errors on some routes.

[Weter]

Hello.
First, thank You for warning: it's really a serious risk.
And for using MSTS RE as well, by the way. Other risk is saving route after deletion of something: last action always MUST be adding.
Well, most precise to say: if that track piece is tied with some track object – than yes: there will be problems, but if there are no signals, crossings, etc. than it can be tried.
I've done those fixes several times without any issues.
Furthermore, TSRE offers to us CONTROLLED process of TDB modifying, while MSTS RE did it only automatically and hence - unpredictable.
In other words, signals, mileposts, crossings are tied with nearby track section, so if you would edit the latter: these tied items will be lost!
So far, there is a law: never place track objects like that, before your track work for that place will be completely finished.
But, of course, you can lay new track, extending the line.

[Laci1959]

Hello.

I’ve only been using TSRE for a year to build a track with no problems.

What I pay attention to is that when deleting items that affect the tdb, I save it before leaving the Tile. I used to do this at the MSTS level editor and have been using it ever since.

Indeed, TSRE also fails if we do not follow the above rule. I saw a log file with signaling errors. The track builder only uses TSRE. I think the maker didn’t save Tile before switching.
Replacing a Siding with a Platform or creating a new one is no problem if you pay attention to the backup.

Laci1959

[Laci1959]

[quote]So far, there is a law: never place track objects like that, before your track work for that place will be completely finished.

This can also be tricked. I go from station to station in track construction. When the track is ready, backup, then signaling, milepost, track sounds. Then backup again, and then you can come up with the next station spacing.
When making changes, make sure that the elements placed on the track are removed while the track is active. If you do the opposite, it will freeze when the Signal is selected.

Hello Weter. I welcome you too.

[Weter]

To our case: since there are no signals near misaligned track, I will try to fix that.
What is "active track"? Selected?
Yes: I've heared too: if track work have to be modified anyway, first it's needed to remove all related objects, then reconstruct tracks, and finally add new track objects to proper places.
WRT save before leaving this tile-thanks, it sounds reasonable.