FUDE activities documentation

These are paths and corresponding services which form the basis of any web•TrainSim activity on FUDE.

The first task was to look at available platforms for departing and arriving passenger services and then sidings and terminals for freight operations.

Paths were created by:

• opening the Activity Editor and creating a new activity with the name junk since there was no intention of saving it;
• a new Player service was created, once again using junk as a name since this service would not be saved;
• in the junk player service, a new path was created and this involved the real work;
• both the path name and display name of the path were set to be the same, using abbreviations for the departing and arrival destinations combined with platform or siding number (if there was an alternative route to a destination, a prominent way station name was included);
• in creating each path, the track followed was carefully determined to allow passing of a slow service by a faster one;
• no path was allowed to begin on a track at a station or siding when there was the possibility of that track being used by a through service;
• destination and departure platforms and sidings were only assigned one function, departure or arrival;
• platform numbers were assigned at London with express services departing/arriving at the middle platforms with direct access to the main line:
• services in decreasing importance were assigned platforms fanning out from the main centre express ones.
• after the path was saved, the junk service was Cancelled and another new, junk player service created to begin making the next path;
• web•TrainSim has found that the method above best suits his way of working: there's only one job at hand and the player path being set up is clearly visible and not cluttered with other traffic paths. Note that this player path can of course be used by traffic.

Paths

Services (traffic)

Learning from earlier experience, particularly after realising when looking at LGV Med activities that all that's required is a service for each path, the whole job of creating services is much simpler.

So for each path above, there is a corresponding service.

You'll recall that a MSTS service has two main elements, a path and a consist to travel that path. Having decided on the paths, you'll really decided on the type of service as well, whether it be express passenger, local passenger stopping all stations, or a freight.

Thus, services for web•TrainSim's activities on FUDE are named as above.