$dispose Command
#1
Posted 21 May 2020 - 08:42 AM
I've searched a few other forums for a possible solution, with no luck. Here's my issue: There are a few trains on a particular timetable that are intended to "unload" passengers at the final station, then proceed to the "service track" which is located half a mile north of said station. At that "service track," the train is intended to utilize the $form command and form another train, a few hours later. There is a platform marker on the service track, and I have addded it as a stop for the trains in question. However, for some reason the trains will terminate at the final station stop (prior to the service track) and will form at that stop. This causes a big issue due to other trains requiring to utilize that platform during that train's layover. I did read the updated timetable editor user guide, and aftery some trial and error trying a few different commands, such as $stable or $triggers, still no luck. Both the inbound and outbound train's paths extend to the service track. I'm sure there is an answer to this behavior, but not one that is obvious to me. It should be noted that I have several other AI trains performing the same or similar behaviors at different locations along the route, with no issues. Would it be possible that OR is not recongnizing the "service track" as a station stop? Any and all help would be greatly appreciated!
#2
Posted 21 May 2020 - 09:22 AM
Have you look at the log, if a command is not executed, a path could not be created, ... an error is generated. I've solved some problems of that kind on a timetable with the log (consist not executing a task, and locking an entire station). Once the problem is known, it's pretty easy to solve it!
Flo
#3
Posted 21 May 2020 - 09:41 AM
FloBarr, on 21 May 2020 - 09:22 AM, said:
Have you look at the log, if a command is not executed, a path could not be created, ... an error is generated. I've solved some problems of that kind on a timetable with the log (consist not executing a task, and locking an entire station). Once the problem is known, it's pretty easy to solve it!
Flo
#4
Posted 21 May 2020 - 10:07 AM
As last resort, you can always split the train - terminate it at the platform, then form into a new working from platform to service track, then a service from service track to platform where it forms into the required new train.
Regards,
Rob Roeterdink
#5
Posted 21 May 2020 - 11:57 AM
roeter, on 21 May 2020 - 10:07 AM, said:
As last resort, you can always split the train - terminate it at the platform, then form into a new working from platform to service track, then a service from service track to platform where it forms into the required new train.
Regards,
Rob Roeterdink
No, that station names are different. No signals either. I'll have to try the last resort method and see what happens. Thanks for the info!
#6
Posted 21 May 2020 - 12:16 PM
#7
Posted 24 May 2020 - 01:25 AM
- Can you show a screenshot of the trackviewer showing the situation and the path into the siding?
- What is shown in the dispatcher hud for the train when it has formed into the working which is supposed to go into the siding?
- What happens when you run this train as player train? Do you get permission to move or is the path somehow blocked?
Regards,
Rob Roeterdink
#8
Posted 25 May 2020 - 10:35 AM
roeter, on 24 May 2020 - 01:25 AM, said:
- Can you show a screenshot of the trackviewer showing the situation and the path into the siding?
- What is shown in the dispatcher hud for the train when it has formed into the working which is supposed to go into the siding?
- What happens when you run this train as player train? Do you get permission to move or is the path somehow blocked?
Regards,
Rob Roeterdink
Hi Rob, thanks for the reply. Attached below are screenshots of the original path for the service, and then the path for the respot to the layover service track. I will run this service as the player shortly to see how it behaves, and report back.
#9
Posted 25 May 2020 - 10:50 AM
#10
Posted 25 May 2020 - 11:09 AM
I suppose this could be seen as a bug but I'm afraid I can no longer correct such issues as my own 'private' version now deviates so much from the various official versions that it's no longer possible for me to keep track of the official versions.
Regards,
Rob Roeterdink