when I set a new waypoint right around the time an autosave is triggered. The already set waypoints get discarded after the autosave finishes. If I quit the game and load the autosave the waypoints are still there

This is constantly happening to me too. Steps to reproduce: shift click to enqueue/chain waypoints for a spidertron on a map and when the autosave is triggered around the moment a next waypoint is being created the entire chain gets cancelled after the autosave finishes ...

This is constantly happening to me too. Steps to reproduce: shift click to enqueue/chain waypoints for a spidertron on a map and when the autosave is triggered around the moment a next waypoint is being created the entire chain gets cancelled after the autosave finishes

... I have a red spidertron with the white and green spidertrons set to follow red. I grab the remote for the green spidertron and send it to several waypoints, holding shift the entire time. After it reaches the last waypoint it returns to following the red spidertron. I grab the remote for the white ...

... I check whether the path end rail has changed since the previous tick. If it has, that's because the braking point passed a scheduled stop. I use waypoints so the trains don't brake, they just go right by, which means the recorded distance is as close as the train got before its braking point ...

... I check whether the path end rail has changed since the previous tick. If it has, that's because the braking point passed a scheduled stop. I use waypoints so the trains don't brake, they just go right by, which means the recorded distance is as close as the train got before its braking point ...

... lengths, but as a way of validating models I thought I'd measure throughput as directly as possible. So I put a train on a long oval loop with waypoints at the end of each straightaway and watched for the train's path_end_rail to change. Each tick I recorded the distance from the train's back ...

... in it to stay at their departure location with the "destination full" message. They would choose the other Elevator (name 2 "waypoints" the same) that has still some room left, even if it's not the closest though. The other points you mention are indirectly related to ...

... and dynamic obstacles allows this. There's no need to check every tick if something got in the way. In fact, the new queueing system literally is waypoints! It's not static, though. Any roboport at any given moment could be destroyed or deconstructed. There's no reason this needs to be handled. ...

... and dynamic obstacles allows this. There's no need to check every tick if something got in the way. In fact, the new queueing system literally is waypoints! It's not static, though. Any roboport at any given moment could be destroyed or deconstructed. I have played this game for hundreds of hours ...

... usually refer to dynamic obstacles and collision detection. Since bots are flying, none of them is applicable. There's just a number of static waypoints. Unlike the true pathfinding, this operation is quite cheap. Waypoints is pathfinding. It was popular with quake bots, for instance. That ...

... usually refer to dynamic obstacles and collision detection. Since bots are flying, none of them is applicable. There's just a number of static waypoints. Unlike the true pathfinding, this operation is quite cheap. Waypoints is pathfinding. It was popular with quake bots, for instance. That ...

... usually refer to dynamic obstacles and collision detection. Since bots are flying, none of them is applicable. There's just a number of static waypoints. Unlike the true pathfinding, this operation is quite cheap. Waypoints is pathfinding. It was popular with quake bots, for instance. That ...

... usually refer to dynamic obstacles and collision detection. Since bots are flying, none of them is applicable. There's just a number of static waypoints. Unlike the true pathfinding, this operation is quite cheap.

... combined with https://mods.factorio.com/mod/lex-aircraft, this would allow to give order to a flying cargo ship to follow waypoints, similar to the dotted lines between robotport, a mix between trains and drones. This makes sure those do not venture in hostile territories. ...

Reading inventory before trains arrive at temp stops is way too much effort to fix this edge case.

Changing temp stops to waypoints has trains overshoot the stop.

Wasn't there an (experimental?) option for LTN to not set a temporary waypoint in the schedule? Without the waypoints there would be a simpler way to implement your setup at the cost of having all stations with the same name act as a single group of stations. Simply place 1 ...

lol

It should not cost anything to give them hints so they don't choose a stupid route through the whole base.

... turned red with combinator. That would trigger revalidation on fewer trains. And if the path were simpler, with less junctions, or maybe using waypoints in some area where it make sense it would make each revalidation take less time. When you have a train selected, you can see its pathing, ...