Rail waypoint grouping in the station list, or waypoints applying to all incoming forks?
my post from the steam forums and two followups to help clarify.
The way I've figured it out so far, if you want to make a stacker to get trains out of the system temporarily you have to make stackers with waypoints on each lane of the stacker. And even if you name all the waypoint stations the same thing you have to point at each individual waypoint to add it to the list of stops. After a few days of setting up dozens of trains with dozens of waypoints, I got the bright idea of setting a single waypoint on the outbound track that they all have to funnel out of anyways.
The problem with this idea seems to be that there is a permanent right-of-way segment there that you cannot designate as a no-stop zone. So trains will nose up to the waypoint and sit there blocking the entire stacker, even if the waypoint is surrounded by no-stop zones.
The idea or question in my head is can the waypoints be designated as a no-stop zone so that they'll only approach them when the criteria for the subsequent station has been fulfilled, after going as close to them as allowed by the no-stop zones? Or if anyone else has a more elegant solution to this minor inconvenience I've burdened myself with I'm all ears.
Pic of what I'm talkin about at an awkward view because trees. One train blockin the rails, three others waiting behind it even though the one blocking the rails is sitting on no-stop areas, but the waypoint itself is not a no-stop area.
https://steamcommunity.com/sharedfiles/filedetails/?id=3705325212
--
as summarized by another person: smart waypoint that acts as a group for all incoming forks, to avoid configuring each station waypoint groups over and over again.
--
that or a way to group waypoints once and apply the group to train scheduling. Either of these I think could accomplish the end goal of making things a bit less tedious?