We always wonder why the AI drivers go to slow and we look at acceleration problems with the engines specs, we check the signaling, play with hidden junctions, and spin our chairs while pulling our hair out in frustration because this doesn't always work! Well, sometimes they're right. Last night I had a meeting with my drivers and apologized to them for blaming the for going too slow. Let me explain...
On the Gloucester Terminal Electric, I added a long, or what seemed like a long, extension from Gloucester to West Gloucester (real places by the way) with stops at Le Page Condominiums, where the glue factory used to be, and one in between on Essex Avenue. There is a long stretch of track running along Route 133. There are a few crossings and a bunch of houses here in their along the marshlands. This stretch is more or less straight as an arrow before it curves and climbs up to the Le Page. I signaled this just as I have my other routes, and to my surprise, the AI refused to go over 25 mph. This was 1/2 of the speed I marked. On either end of the this line are slower sections with one being the return loop, and the other being a drawbridge crossing and a slow stretch through the ocean side park. No matter what I did, they refused to go a bit faster...
Last night I drove the route myself from West Gloucester back towards the downtown. I accelerated right up to the posted speed and then quickly had to go down for the station at Essex Avenue. I then started to pick-up speed again only to have to slow down for the next station at Le Page. Now came the long stretch of open track. I got myself up to speed and couldn't stop in time for the single track at the drawbridge. I ended up derailing at that point because I blew through a misaligned junction -- Another AI driver was heading towards West Gloucester and had control of the junction.
So as I learned last night, we shouldn't always blame the AI for their slow driving. There are some reasons other than the technical ones why they do things.
John
On the Gloucester Terminal Electric, I added a long, or what seemed like a long, extension from Gloucester to West Gloucester (real places by the way) with stops at Le Page Condominiums, where the glue factory used to be, and one in between on Essex Avenue. There is a long stretch of track running along Route 133. There are a few crossings and a bunch of houses here in their along the marshlands. This stretch is more or less straight as an arrow before it curves and climbs up to the Le Page. I signaled this just as I have my other routes, and to my surprise, the AI refused to go over 25 mph. This was 1/2 of the speed I marked. On either end of the this line are slower sections with one being the return loop, and the other being a drawbridge crossing and a slow stretch through the ocean side park. No matter what I did, they refused to go a bit faster...
Last night I drove the route myself from West Gloucester back towards the downtown. I accelerated right up to the posted speed and then quickly had to go down for the station at Essex Avenue. I then started to pick-up speed again only to have to slow down for the next station at Le Page. Now came the long stretch of open track. I got myself up to speed and couldn't stop in time for the single track at the drawbridge. I ended up derailing at that point because I blew through a misaligned junction -- Another AI driver was heading towards West Gloucester and had control of the junction.
So as I learned last night, we shouldn't always blame the AI for their slow driving. There are some reasons other than the technical ones why they do things.
John