JonMyrlennBailey
Well-known member
It seems to cause Drive To (track mark) and Move to Train at Track Mark commands on schedules to act stupid.
For example, on my cloned West of Denver route, I ran my my GP-38 engine pair around the passenger train at Union Station in Denver, Colorado. The line terminates there so trains have to go back out the same way they came into the platforms and navigate back to the main line. I used the Change Direction command following the engine runaround to establish the new front of the train. I also made sure the driver was moved to the new lead engine using the Move to Train at track mark commands and these worked there.
This train then drove back to Sulphur Springs via several passenger stops. I used Drive To track mark to stop the trains at platforms at Winter Park, Fraser and Granby. The train stopped at the correct spots at Winter Park and Fraser but oddly stopped way ahead of the platform at Granby. The train oddly stopped so that the arse-end of the train was at the prescribed track marker for this purpose and not so the lead engine was at the track mark as it should have otherwise been.
Then at the staging area at Sulphur, end of route, the driver was supposed to be moved from this train to another passenger train there on a holding track. The Move to Train at track mark failed this time. The driver did not swap trains and the schedule was involuntarily stopped so the Continue Schedule appeared on the drop-down menu. Even when I clicked on Continue Schedule, nothing happened. This Move to Train at track mark command malfunction doesn't seem to occur if there is no run around train operation on the schedule.
I now had to reconfigure my passenger trains so there are engines on either end so the run around operation does not have to be employed at Denver Union Station. Drivers no longer switch passenger trains at the Sulphur holding area to boot. Each train there now has its own driver and trains line up one behind the other on a single holding track and are released one by one every three hours.
For example, on my cloned West of Denver route, I ran my my GP-38 engine pair around the passenger train at Union Station in Denver, Colorado. The line terminates there so trains have to go back out the same way they came into the platforms and navigate back to the main line. I used the Change Direction command following the engine runaround to establish the new front of the train. I also made sure the driver was moved to the new lead engine using the Move to Train at track mark commands and these worked there.
This train then drove back to Sulphur Springs via several passenger stops. I used Drive To track mark to stop the trains at platforms at Winter Park, Fraser and Granby. The train stopped at the correct spots at Winter Park and Fraser but oddly stopped way ahead of the platform at Granby. The train oddly stopped so that the arse-end of the train was at the prescribed track marker for this purpose and not so the lead engine was at the track mark as it should have otherwise been.
Then at the staging area at Sulphur, end of route, the driver was supposed to be moved from this train to another passenger train there on a holding track. The Move to Train at track mark failed this time. The driver did not swap trains and the schedule was involuntarily stopped so the Continue Schedule appeared on the drop-down menu. Even when I clicked on Continue Schedule, nothing happened. This Move to Train at track mark command malfunction doesn't seem to occur if there is no run around train operation on the schedule.
I now had to reconfigure my passenger trains so there are engines on either end so the run around operation does not have to be employed at Denver Union Station. Drivers no longer switch passenger trains at the Sulphur holding area to boot. Each train there now has its own driver and trains line up one behind the other on a single holding track and are released one by one every three hours.