Hi.
Top start this thread off, Ill tell you a little bit about the story of a train and Ill tell you what the problem is in a bit since this problem that I have got is able to be traced back to about a mile from where the problem occurs.
A train with a default priority 2, traveling off the left (West) of the map is traveling towards the right (East) at a good 70MPH, it passes a signal at green, it passes a track mark shortly after the trackmark, the train then uses a path command which switches the switches between the train's position to the station, which changed the next signal (LF 02 shown on the left side of http://img267.imageshack.us/img267/8449/ben1337201007050003.jpg) to green.
This allows the train to speed happily along its route up until it reaches LF 03 where it starts slowing down.
The train does this up until LF 13 (The signal protecting the center line of the 3 track mainline shown clearly on http://img227.imageshack.us/img227/1636/ben1337201007050002.jpg) which is at red because a set of points are set in the direction. it slows down to 1MPH when it uses a driver path command which sets all of the points till the next checkpoint, which sets the signal to green.
It does this because of many reasons, one of them is that the line for the station divides so late on approach to the station there wasn't really enough distance to put the "LF through" trackmark further away from the signal. And the junctions cant be moved because of the yard.
Another reason is how the driver commands are set up (It's set up to protect the single line from head on train collisions).
From start to finsih for the driver commands: Navigate Via trackmark "Lowfell West Approach" (off the left of the screen), Set priority to 1, Set path to LF Through, navigate to trackmark (LF Through, Trackmark is placed at the same location as the signal, radius is 26 meters because the train needs to stop as close to the signal as possible, moving the trackmark will make the train faster... but at the cost of smaller trains with more possibility of them blocking the station platforms when they arrive), Waite for junction permit (Lowfell Main Reserve, The junction prevents 2 trains going onto the single line) and last of all, Set path to Applesthwaite (Next station along the line).
So... What I figured out is that if I had a trigger that can trigger with a certain priority and not trains with other priorities, I can set it just after "Lowfell West Approach" with time for the train to execute the priority command which sets the priority to 1. All trains with priority 1 goes through the station (Hense why the green tracks (priority 1 tracks) goes through the station) and trains with a different priority doesn't effect anything with priority 1 lines.
This Theory provides advantages that I can activate rules which can get the signals early if any train with the same priority passes the trackmark.
Problem is is that I do not have a priority trigger and I can't find one on the DLS other then specialized triggers meant for ATLS (Which I doubt that they would work as a standalone thing if you know what I mean.)
Other ideas for the route are welcome.
Top start this thread off, Ill tell you a little bit about the story of a train and Ill tell you what the problem is in a bit since this problem that I have got is able to be traced back to about a mile from where the problem occurs.
A train with a default priority 2, traveling off the left (West) of the map is traveling towards the right (East) at a good 70MPH, it passes a signal at green, it passes a track mark shortly after the trackmark, the train then uses a path command which switches the switches between the train's position to the station, which changed the next signal (LF 02 shown on the left side of http://img267.imageshack.us/img267/8449/ben1337201007050003.jpg) to green.
This allows the train to speed happily along its route up until it reaches LF 03 where it starts slowing down.
The train does this up until LF 13 (The signal protecting the center line of the 3 track mainline shown clearly on http://img227.imageshack.us/img227/1636/ben1337201007050002.jpg) which is at red because a set of points are set in the direction. it slows down to 1MPH when it uses a driver path command which sets all of the points till the next checkpoint, which sets the signal to green.
It does this because of many reasons, one of them is that the line for the station divides so late on approach to the station there wasn't really enough distance to put the "LF through" trackmark further away from the signal. And the junctions cant be moved because of the yard.
Another reason is how the driver commands are set up (It's set up to protect the single line from head on train collisions).
From start to finsih for the driver commands: Navigate Via trackmark "Lowfell West Approach" (off the left of the screen), Set priority to 1, Set path to LF Through, navigate to trackmark (LF Through, Trackmark is placed at the same location as the signal, radius is 26 meters because the train needs to stop as close to the signal as possible, moving the trackmark will make the train faster... but at the cost of smaller trains with more possibility of them blocking the station platforms when they arrive), Waite for junction permit (Lowfell Main Reserve, The junction prevents 2 trains going onto the single line) and last of all, Set path to Applesthwaite (Next station along the line).
So... What I figured out is that if I had a trigger that can trigger with a certain priority and not trains with other priorities, I can set it just after "Lowfell West Approach" with time for the train to execute the priority command which sets the priority to 1. All trains with priority 1 goes through the station (Hense why the green tracks (priority 1 tracks) goes through the station) and trains with a different priority doesn't effect anything with priority 1 lines.
This Theory provides advantages that I can activate rules which can get the signals early if any train with the same priority passes the trackmark.
Problem is is that I do not have a priority trigger and I can't find one on the DLS other then specialized triggers meant for ATLS (Which I doubt that they would work as a standalone thing if you know what I mean.)
Other ideas for the route are welcome.
