Rail Route

Rail Route

View Stats:
I cannot make shunting/stabling to work
I just don't get it. Shunting and stabling is working very unclear.

I have issues with the freight trains - I just tring to reverse them using shunting sensor and side track in T-shape. It's going to side track, reversing, then going to another branch, but when passing last shunting signal it's still staying in "shunting mode", it's not finishing it. And then it's driving further fine, but staying in "shunting" mode with 30km/h forever...

Ok, I have workarounded that. The last shunting command is reverse and then it's going ok out of shunting mode - I'm just using routing sensor to direct to proper line.

But then another problem and I don't get it. I have regional trains with a few legs. I have created shunting groups and using stabling sensor to send there trains, wait 15 minutes, then get back. But the trains are just skipping 15min wait time as it's not in the commands and immediately going to wait on the platform. I've tried to use wait before reverse, after - no matter.

Can someone help to understand, what's wrong? Here's short video:
https://cdn.steamusercontent.com/ugc/9429400190744488930/8E419894D5E02BA7AF42D0672CA0C746B0C737E8/
Last edited by LbISS; 18 May @ 3:41am
< >
Showing 1-2 of 2 comments
LbISS 18 May @ 4:07am 
Finally have got it... The timer is not "how long to wait", but "how long before the next leg". Have spent probably an hour trying to understand how it's working...

Similarly I have spent 15 minutes trying to understand why regional trains are not going to coach yards. Yeah, it's separate techonology.

Might be I dumb, but I played a lot of OpenTTD and NEVER had such kind of issues trying to understand how to build intersections/signals/etc. I think a lot of stuff needed additional tooltips "why it's not working", "why the train stopped", etc.
Last edited by LbISS; 18 May @ 4:08am
Mišo  [developer] 23 May @ 11:37am 
The "Time in Advance" is covered in the Shunting Commands tutorial:

After reversing, the train should be stabled until it's time to prepare for the next leg and then be reused (renumbered) for it.

Let's add the [Reuse] command to the [Shunting Queue].

It has a configurable [Time in Advance]. It is the time [before] the next leg's schedule start when reusing should happen.

And then the subtask instructs you to
Change the Time in Advance of Reuse command to 3 minutes.

And the tooltip for the command says:
'Time in Advance: Time before the next leg's schedule start when reusing is performed.

However, I realized recently that because the most recent value is pre-set, the subtask may be instantly marked as done in the subsequent passes through the tutorial (because you set it to 3 so it was already pre-set to 3 when you start the tutorial again. So I made a change recently:
UPDATE: Set last used Time in Advance to 6 for ChangeReuseCommandTimeSubTask to require interaction BUILD:2.3.19

It was rolled out on May 14.
Last edited by Mišo; 23 May @ 11:37am
< >
Showing 1-2 of 2 comments
Per page: 1530 50