Atomic Systems

When creating a timetable for trains on a long route, it is impractical to have to fly all the way to each destination to mark it on the timetable. However, although the UI is not particularly well designed in this respect, it is possible - and fairly easy - to set up a timetable without flying to each destination manually, which makes things much simpler.

The sequence is this:

1. set up the train ready to take the instruction;

2. open the list of destinations on the route;

3. click on that destination to bring up the latitude and longitude in the navigation window, but do not click on the arrow to go there at this stage;

4. double click on the instruction icon to bring up the option of adding a destination;

5. now click on the arrow in the navigation window to go to the specified latitude and longditude;

6. click on the destination marker in the new location; and

7. use the list of destinations to jump back to the train to add the next instruction.

This is a little cumbersome, and not ideal, but definitely better than flying to the destinations; better enough, in fact, that I am going to downgrade the flying to destinations issue from "sub-critical" to "non-critical" in the list of operational deficiencies.

Thanks for this more detailed discussion of the problem.

Bill Hobbs

Yes this is a much better and faster way...if I could just get AI trains to stay on the track and not derail I might be able to enjoy the game,you must have a lot of patience James!
I must admit I have had enough of it now. The ability to create simple scenarios is the most important part of the game to me, I have had problems with every scenario I have made, the frustration out weighs any fun by far.
So I have uninstalled RS..very dissapointed.

markjudith wrote:Yes this is a much better and faster way...if I could just get AI trains to stay on the track and not derail I might be able to enjoy the game,you must have a lot of patience James!

It is frustrating - there are quite a number of problems. I have recently encountered as yet undocumented bugs with portals, which I will be documenting shortly.

My view at this stage, however, is that it is better to work with Rail Simulator and identify and document clearly all of the deficiencies so that the developers can fix them and so that Rail Simulator will eventually be what it always should have been from the start than it is to do nothing and hope that it gets better all on its own. RSDL, we have recently been told, is very small, so they probably need all the bug/issue-documenting help that they can get.