Drive to station -- once only?
- Thread starter Rik81
- Start date
cascaderailroad
New member
Perhaps in the CM "DRIVE TO STATION" command rule has been updated or disabled ?
ColPrice2002
Well-known member
Check that you have compatibility mode turned on.
Some of the older commands may cause problems...
The "Navigate to" command does work repeatedly...
Colin
Some of the older commands may cause problems...
The "Navigate to" command does work repeatedly...
Colin
If you haven't found it, it means you haven't touched it.
It's one of those things not to touch otherwise other bad stuff happens - this sounds like a bad scene in a movie when the lead actor reaches for that red button with a warning over it!
When you say doesn't work, do you mean you can't add in a destination to the industry?
The method is a bit different now, but the end result is the same.
Click on Navigate to and in the open space start typing the destination, meaning station or industry.
Click on the one you want, which will put it in place.
You can also scroll if you want, but typing the name in the search area is so much faster.
You then choose, in the bottom part of the same interface, which platform, bin, track, or whatever you are supposed to go to.
The rest is the same, add in Load, etc. in your command line and continue on to the next destination.
Recommend using the 'Navigate to...' driver command and NOT the 'Navigate to Station' alternative.
You can add this command to the Driver List in Surveyor Session Edit, Edit Driver Rules, Add Driver Command mode.
The icon looks like a pointing hand.
When you use this particular driver command, you can choose the name of the station and then the desired platform number so that the driver navigates to the correct platform as well.
If the name of the target station does not appear on your list after adding the 'Navigate to...' command to your driver's schedule, then you need to check the track connections for that particular station in Route Edit mode.
Be on the look out for double connection spline joints where the station connects to the lead-in track. If these are duplicated, then there is a problem.
Best way to fix that situation is to delete the station and then to replace it with another one, renamed and configured appropriately as your session requires.
You can add this command to the Driver List in Surveyor Session Edit, Edit Driver Rules, Add Driver Command mode.
The icon looks like a pointing hand.
When you use this particular driver command, you can choose the name of the station and then the desired platform number so that the driver navigates to the correct platform as well.
If the name of the target station does not appear on your list after adding the 'Navigate to...' command to your driver's schedule, then you need to check the track connections for that particular station in Route Edit mode.
Be on the look out for double connection spline joints where the station connects to the lead-in track. If these are duplicated, then there is a problem.
Best way to fix that situation is to delete the station and then to replace it with another one, renamed and configured appropriately as your session requires.
Last edited:
Hi.
NavigateToStation and DriveToStation have not been already rewritten to use new Tane SP2/SP3 and TRS2019 script API and new techniques to avoid script timeouts on big size routes. They are on my to do list, and will certainly be upgraded in October or November in my planning.
Currently they should work in Tane SP2/SP3 and TRS2019 with compatibility mode active if your route is compact or medium size (less than 50 industries on the route - NavigateToStation or DriveToStation may currently encounter script timeouts when there are too many industries on the route).
Sorry for the delay but with the new script APIs and also the new performance optimisation modes (object streaming and maximise performance option) there are quite a lot of tests and updates to be made to many of my assets available on DLS, and this needs a certain amount of weeks to be fully done … Thanks for your patience. But all scripted assets should be updated and ready for use before the end of the year.
Regards.
Pierre.
NavigateToStation and DriveToStation have not been already rewritten to use new Tane SP2/SP3 and TRS2019 script API and new techniques to avoid script timeouts on big size routes. They are on my to do list, and will certainly be upgraded in October or November in my planning.
Currently they should work in Tane SP2/SP3 and TRS2019 with compatibility mode active if your route is compact or medium size (less than 50 industries on the route - NavigateToStation or DriveToStation may currently encounter script timeouts when there are too many industries on the route).
Sorry for the delay but with the new script APIs and also the new performance optimisation modes (object streaming and maximise performance option) there are quite a lot of tests and updates to be made to many of my assets available on DLS, and this needs a certain amount of weeks to be fully done … Thanks for your patience. But all scripted assets should be updated and ready for use before the end of the year.
Regards.
Pierre.