Using the 'Call At' driver command

[mawsoft]

I've tried grouping station objects together with AJS Invisible stations but can't get passenger trains under AI driver control to react to the "Call At" command. Any advice please.

mawsoft

 

[schweitzerdude]

Use "navigate to" (and then "load") instead.

 

[kwheng]

Hi mawsoft,

If you mean that you can't get the command to work properly, first check that you are naming the station objects correctly. i.e. adding brackets after the station name with a different character between them. If you still have trouble let me know and I can give you more detailed help.

 

[mawsoft]

Thanks for that tip. I'll try that if all else fails.
mawsoft

 

[mawsoft]

Hi kwheng

I think I have named the stations correctly - in the form York[2:Northbound]. I then allocate say '2' as the first platform number and alter the platform properties as required but when I use the 'Call At' command in an AI driver schedule, the train slows down into the platform but immediately speeds up again. I'm obviously doing something wrong so would value your further help. Thanks.

mawsoft.

 

[kwheng]

Hi mawsoft,

It appears you are naming your stations correctly. However I have not experienced the problem you are having so probably cannot help you. The only thing I can suggest is to try using the 'Navigate To' or 'Drive To' commands and if the trains behave the same way then the problem is probably not the Call At Command.

kwheng

 

[JohnnyC1]

I think there is a bug in the script. I had several AJS Invisible stations and getting the trains to stop was a hit and miss. Some times a train will stop, other times it will pause and speed off. This occurs after the Call At, Navigate To, or Drive To, commands were issued. The next command was not carried out, usually a load command and any other command which followed, if it was track mark that was passed, the train would stop, back-up, and then carry-out the next command, sometimes!

John

 

[schweitzerdude]

I just experimented and if you don't have a "load" command after every "navigate to" (this also applies to "drive to" and probably "call at"), the train slows down but doesn't stop. I use AJS invisible stations almost exclusively so I know that's not the problem.

 

[JohnnyC1]

What build are you using it on?

John

 

[kwheng]

Hi all,

Have finally got it through my head that you are having the same problem I used to have. The problem is not the command used but the speed of trains as they approach the station. Why this only happens with AJS stations is a mystery which has been well and truly discussed on this forum. The most practical solution is to use speed signs to limit the speed of trains as they approach the station. Some experimentation is needed to decide what speed to use and how far before the station to place the sign. I started with a limit of 40 kph (25 mph) which partially solved the problem (anything less than 40 I thought was prototypically unrealistic).

Hope this helps

kwheng

 

[mawsoft]

Thanks to all for discussion & advice. However after several attempts using that various advice it's still not working entirely satisfactorily so I've decided to use schweitzerdude's original advice and 'navigate to ... ' etc.
Thanks again. mawoft.