[kovarex] [0.17.3] Train leaves disabled station

[Teraka]

Here is a gif of the bug in action:



As you can see, those trains are all partially filled, set to leave the station when completely full, and yet they're leaving as soon as they touch down on the station (the gif doesn't show it, but those trains' inventories are not limited). Emptying the inventory manually and removing/re-adding the "wait until inventory full" condition didn't fix the issue, and other identical trains on this network are working properly.

The circuitry is a bit involved but basically just disables the station when the train arrives. This however shouldn't allow the train to leave before its conditions are filled, since it worked that way in 0.16 (and separate tests showed it working properly in 0.17.0 with the same conditions).

Link to the save file: https://www.dropbox.com/s/tpkp4a07sjs5c ... 1.zip?dl=0

Edit: From further looking at other trains in similar networks, it looks like stations enabling and disabling themselves causes trains to re-path even if they're already stopped at a station without their conditions being met.

[SeikakuOtosan]

can confirm [0.17.2] i also am experiencing this bug. where trains are leaving stations before they have met their conditions. while looking at the train planner, it appears that the train will wait at the station and do what its supposed to do, until for some reason the station will flash closed to the stopped train. for 1 tick. and that will cause the train to leave the station.

i have seen this bug present itself where in the AI will both either path right back to the station it just left. (it does not need to physically go through another station to loop around) and also advance the AI to the next station ( when the train would have to physically path through another station if it were to loop around)

[kovarex]

Can you reproduce it with a station that isn't connected to circuit network with enabled/disabled controled by it? When I removed the condition I couldn't reproduce it.

[Teraka]

No, the bug is linked directly to stations enabling/disabling.

Here's a blueprint that reproduces it reliably:

0eNrNmt9uozgUxl9l5WsYYf4TaV9gpb2avVuNEAEntZaYyJjMRlXffW2gSZqcTH0suuKmbWr42T4+34djzivZtgM7Si4U2bwSXneiJ5u/X0nP96Jqzf/U+cjIhnDFDsQjojqYT7LiLXnzCBcN+5ds6NsPjzChuOJsun/8cC7FcNgyqS+43FkP8sQafwR45Nj1+p5OmI40x088cta/wkSzGy5ZPTWmb94DMrRDRjAxAojRhdgrDdu/qGfDzGdo+BGaAdDYFprCTAowE8toUjoxafE5M7VjFhciwMisA0jDmRNDnPzCabu6O3SKn9gjhAYzQ0+HdJJrSDU16waTrr25UAx1yyrp7wam0zmEuitsh33pERy1aZ05BiP8XnVHAHKduqc7nIdMvnP5/TDs961GQXCKjy04WRqiZwtzIvyAAhAUowcEcxL0gHKQk2LHA2PwYkhBzlUM/bB9z5dnNpeAiNsEr+p/fC56JpVuesDk32YHTr/dGWYIWXCABydW4Gu2c7HjQrf59Qvr1SM4+wh+v7zsmVJc7EcPkOzQnVg56LZWj4415WwPSg4MilgY4vtPl+z/Kq66kvvO/1ntoVV/z8D4wQEhKFpoYEKGifWiU/p01cEneupATq3ImfV60vBLFjR3GMCiGV2g7Qh8yEVXybNWh1zy2meCyf1Zr5Yeya6q2fN9Xfy59COK95TYxlOiEA+OrMAR3iyiBZc2ivH9x0v2n2B9Bc4sF/VHNuqPMgdybEV2kfWisS8cBrBk8sUB2lfA7WTsIPvQRp2xg+ypFdhB9nTJyDvIPlyyf7Ts4YV3kT21EWfsIvvQiuwi+0Vj7yL7JZMvsd/5+zSaRxDYxDahDmTfDm2/q9ffzj+icWHbVW3PPDL9ezoQe+9YdsLvpNkj1d1gTt1MKA9dYxor5besGsdzPVgDwx85zGSVE4mxjw/wu3+S2MejWHM4Uvw81pmgGULFwVMVQ8/dJHdA25GxB4FgLqYu1mj12EldrNHqUZm6OCNdYd6lLsYYrnEiaGMEd1epgzGuMhwOxrjK/HTxRauvI6mLLVp9g0qxtghmYuZii1ZfwjMXW7Q6OMhcbDFaYdplLrYYr3EiaFsEz5oyB1tcZTgcbHGV+elii1aHs5mLLVqdJ2dYW4RfdaPPz8CXMjm1ekvoT6/vMxCBfTEMDwT9Whh8e5pj31XBFPQrYfjVcn5THNEJHV2h/Lo7bLmoVCd/tQV5PJcwOhFKdm25ZS/Viev79U23ynoovTlxqYaqvVbfTFf4ganAmVVHP9bi8L40vY26HS8SYhrBqHNqfuwlY+K2Voc3eqa5ESgUggy5IE8imVvVSPimKMBA7ophYjh6NZf1wFWp25oLZsdlr0rrYP41BXNa3bGERK/wsZLjCm/I72Pz3A8T1bZlZcN783s6JfNIz0RTqq4cJ3bxTMmqpjSzPGo7nZum68cPlybMQFErmo6We1Np8oe+9fzbn1CVSY5+SwgXhxQBTjDpu14et7rr1ksRPtFLQbF6gQMZYmqKRrl8lUDYicmzetF7hS9Syv+jhyJA6KGIcJV2NLvzK4gZYyrt7okJREyQhYthYAFNUSWbYfR5KWSRYUo274nQHqzIcdWV9xOPjPZ7vWNuhnYuXL1WHJrP+U37ZDYPaeORn9WttCbMJAlWzsk7mt78925oW6KT0Ht9Uv6HJrLDUZ0N8sfoZaZSd3NT2OsRLd1+WpYooHGSJTTQG6b/AL5Swy4=

Copy blueprint

Let the train run, then disable the left station by enabling the constant combinator, and enable the right one by disabling its constant combinator. The train will immediately repath and leave the station without first waiting to fill its conditions.

This is contrary to how it worked in 0.16, and breaks a lot of behaviors linked to managing more complex loading/unloading bays, like the ones in the save I linked above.

[SeikakuOtosan]

i tried to upload a video yesterday, but youtube logged me out before it got all the way uploaded. so it failed. made a different, shorter video today, not the best frame rate, but hopefully clear enough to see what is going on. also more details are in the video description. and i will paste them here as well.

https://youtu.be/aiaGWpSsooM

in this video we can see the first train leaves the drop off station before meeting either the inactivity condition, or the empty condition. also note the station is not full of resources.

additionally instead of returning to a drop off station the train advances to the next station, instead of going back through my (staging) station right before the drop off station. which it would have to do if it were to loop back.

after the cut we see a train at a materials pick up station, again the train leaves before picking up a full load of materials, or being inactive for 5 seconds. which are its leave conditions. when it does leave though it paths right back to another station with the same name. (in this case the same station) but it does not have to go through another station to reach it. as it did before. and so does not advance the planner to the next stop, once the train is full though the planner advances to the next stop. this only happens on stations that are setup to close when a train is present through the logistic system.

i tried to show off how my stations are wired as well, and i hope one can get a grasp of how they are wired by looking at the tool tips on the left side when i open up and hover over the logistic buildings.

[zignotzag]

I also had this issue.

In my case it was related to multi-station pickups that all had the same station name. I had a circuit setup so that when a train arrived at one of the stations it would disable that station and enable the next station in the setup. This way the next train seeking that station name would proceed to the stations in a sequential order to balance output of the factory and maximize the loading speed, giving stations time to buffer a bit before the next train arrived. In 1.6 the trains did not leave the station until the conditions were met, regardless of enabled/disabled status. In 1.74 the train leaves the station as soon as it becomes disabled AND the next station with same name becomes enabled. I have already corrected this behavior by modifying the circuit to not disable the station until the train leaves, which is actually a little bit of an improvement to my setup as sometimes I could get constant re-pathing when all the stations had a train at them, thus all disabled.

[Loewchen]

Ref.: viewtopic.php?f=7&t=66435

[wakjah]

I am having this issue as well.

As far as I can tell it only happens when you have multiple stations named the same thing.

Here is a minimal blueprint that reproduces the issue for me

0eNrtVsGO2jAQ/ZVqzmGFIYGSQ6X+QQ+9VSgyyYQdydiR7dAilH/v2NkFWpmWrPZSqZdE9njezLynGfsMO9VjZ0l7KM9AtdEOym9ncLTXUoU9f+oQSiCPB8hAy0NYWUkKhgxIN/gDSjFkf3VRpjYH4+mIN46LYZsBak+ecAwcF6dK94cdWka++DvPQffPfhZjZ9AZx15Gh4CMNFtkcOJfPoRcfkNZPIqy+gPIMlXKvTyYETCWGEKOxvlTkUVGXDj43ZgGynyTipNPLXmRQikeynb1eLLFPBVmNZHZZK7riRUnM/k4LZMkxuaCERrBS+1nzN2OtPTGJtJZBZ4YbPFUMIUNWaxHM+fJCN4aVe3wWR6J3dmnJeXR3umwI1nfS3XtmPHEbG8RdeiZ2vShTcVN223jttZj3KiWCJ/R56afiBUUSz6fKlvMJwqQVFGIaeyJf4u84h55E4dLmrvrcAkYeua86RL05xEi/5WvPM1XTbbuyVdsay4gLVnnq7fQNyrKjRMWh07aqGoJn6L5JRZquVNYNeTCH0pve8zAoW4qb6pYGpStVI53LcqmCnV22LyaxvNxcTE9nOxXGKYougmCcnKvQw8+e09KfvjSIrUtq5LSaepwTt4konhI7f9iv5/YQrxF7Ym3G4vNzxlXP2PTq5f3zPX2DetlVtycGEfZ/Yy2AS6+osqbd1oGRx6D0WW9nIt8PV+J9XoYfgLME1Wj

Copy blueprint

To reproduce the issue using the above blueprint:

- Set both combinators to off. Both stops will now be disabled. Neither of the trains will be showing "No Path"
- Set one of the combinators to on. The *other* train will now try to path to this stop, even if its conditions for leaving the station haven't been met. It will show "No Path"

As with the other posters, I tried the same thing in 0.16 and this didn't happen.

[TheEightWonder]

Same thing here. I have four trains picking up materials from outposts which all have the same name. When one of the stations changes it's condition (on/off) the trains rerout and go to diferent ones (or sometimes the same).

My entire factory runs of on this system, so it's entiraly broken now. i will post a save game but it has a lot of mods. It probably will do the same thing if all the mods are gone.

[mutemute]

In 1.74 the train leaves the station as soon as it becomes disabled AND the next station with same name becomes enabled.

Was able to reproduce it like this as well. It is like re-pathing logic is applying immediately when the train is at a disabled stop and an enabled stop of the same name becomes available.

[SeikakuOtosan]

In 1.74 the train leaves the station as soon as it becomes disabled AND the next station with same name becomes enabled.

Was able to reproduce it like this as well. It is like re-pathing logic is applying immediately when the train is at a disabled stop and an enabled stop of the same name becomes available.

i have a route setup with trains that have 8 input stations (same name) and 2 output stations (same name) even when i have trains at the output stations and i can 100% confirm that the other station with the same name has not come online they will still leave. it is possible that the input stations coming online are forcing the train to leave, even though it is not going there, even for its next stop, which would be a waiting station.

[struppi]

Same here.

I also use the same name for all stations of the same ore. So the conditions define which station is enabled (enough ore to pick up) and the trains only go to stations where enough ore is and it's not busy (Read stopped train). Now with 0.17 the train in the station seems to recheck if the station is enabled while standing in it and if disabled it drives to the next one which is enabled. Even if this is the case it should go to the next station in the list, which would be "unload station" but instead it re-evaluates the same station it is actually doing resulting in trains driving around with half empty load.

My blueprint for an iron ore station:

0eNqtWkuPozgQ/isrn2HkFw9H2r3Pefa2akUkcXejJYCM05pWK/99TZhNsgSHKnsvIUD8VX31chXki+yak+5N3Vqy+SL1vmsHsvnriwz1W1s14zX72WuyIbXVR5KQtjpezkzXpp3R5JyQuj3on2TDzsnqMmuquk0H2/V3C/n5JSG6tbWt9ST8cvK5bU/HnTYO+bpe/+yNHoZ06JvaWncvIX03uIVdO8p0YClj37KEfLpvwok41Ebvp9t81G+GzB+QnYbt0HfGpjvd2Kf48lu2LkGgdOdX7HVkGaA7RemePUg4OY+ZN9O547oM8SAjuUZF258sWRCZ40kpLye5IKCIECAgRivxAop7AQuQKgIS5GhGMVFaIhKMsZAYygEh1J2sJ4YYx7DJECnHBN4TOc4TAVktcBIyvASJk5BHcADlGCsiOMAkBKQxbmNgAVnNURI4jeAAshJnERxgEvA7NG6P4wEpjZQgwynAbJRFUIBJwGc0MlTxCY3LNl6GMxCQvoKrcAYgHwh8NgsUA8HCBYBaLxHVbTOQkQLbbQ6Ajuq3YdpnEc0pW+4dRUxHzUFaF3FjAg8YE0RMl81BwRrTdIO8LWlQmwoIVRnXdPOQplvyiNYYZi8R0fQxiM9lTPMNk5BFSADFrcwjrATKd1mEb6UwI0Xs1TAbqfCdDsQgi9irQQyygMb7WkHoXEK+JCEmn2ESbvk82Gr/d1q3gzbPqx9d3uQyCYfKV6BixmMY7xyurFxRtoBDiRWoMqIyUdDTxJiBFyQhjxl4YRIY3ODsucFzDofiK1AifMIEhWwOzy+6omoWXtthqsKza81B8ORa808ZPhvCSCuwqisVpaBgpJWCUuC3KInKxYKHb7IwAfANamV/KvCNZYZTNVt6xbZQk+QFdDZDuJTZd601XbPd6ffqo+7MuGBfm/2ptlt373BFea3NYLcPr/k+amNP7srNYpdfpH+O7/nGl4q2Gt8wsvHk2FemsqMM8vvl9i85uq12jd4e6mE8ko01J52QQbeHre22F15k81o1g7tqdHXYjiR7ffj31vT7y8n1FkbRSdN2ssowrmHjx5vRur1/LVkfnMHzm97jOT+/jOsdzclQ5Lvp2t9+dCez12TEbSabug+XYW9jpOSMFbksuKKcq0IVIhe8ZOPDvN3FUNX4I6lKKhRnmTswmYucCyrzslgOs1vtO+h97Sa+1Fl7V7cXay/N4FM0PJSY5Xj4hXmLh+FJQPhfF9+iQVJKZwHxh1szDZnoGOs/nWan1m5fTXfcTo8OpnBBebakzpUJ4X7XZ6Ovl8x/2zCO+lCfjqlunEhT79O+a/STBwbcUzZKfIfsg7rfIbRu0v27Hp5NCdOcg7Fa8t8LwmOlkgI1ycM0KdRMk3mqMp9iDD9EeKxdcnxf7oMSQHPJ/8lcpS+8S4mfW3ykMiApERiNYk5K+Ujl+IbeR6rAN/Q+qBJoHxZon7nTlTcpoHWDB2qSzT1VejRRFD2DeKyrGIwTDaRUzo3rK4WKYzeMNWbAYhEYNorNmflqhZLo2clHCVgqAuNPzSuF8sYffrD0USrQ05oPCVgnAsuomicno9RnHYWeGz2cGAU2CIEbniofSPmKn7sDUyWwafKbk1FsacjXrIofZr1Q98ntpq23d5u6Q+OfNyF/raIZHJXDUXM4KoWjFmDUEg5agkFzOKgCg8JdxSgYFO4pxqCgcD8xDsVE6CmgmAiDgjMK7nkGzid4iDJwNiGSiYGTyZf3L8n0uGFz92f2hDTVTjcPT2I+tBkuywpBmSxFwaU6n/8BLM6JpA==

Copy blueprint
The train has just ore station (full inventory, 10s inactivity) and unload station (empty inventory)

[knightelite]

I reproduced this as well in 0.17.7 and posted about it in this thread: viewtopic.php?f=7&t=66994

I also made this video of it in action, triggered when you enable a disabled station. It also occurs when you place a new station with the same name when all existing ones are disabled. Save is attached in that thread, but I attached it to this post as well.

[barbary]

I have just loaded my 0.16 map into 0.17.7 and have this bug and it's killing me.

I have a 8 stations named 0Copper Plate Unload. 4 of them are set to be disabled if a Train is in the station.

Something happened in the game and all the trains sitting waiting to unload (or in the middle of unloading) just up and leave all at the same time.

[Pay]

Something happened in the game and all the trains sitting waiting to unload (or in the middle of unloading) just up and leave all at the same time.

It seems like if a train sits in a disabled station and a station with the same name gets enabled it repaths immediately, resulting in leaving the station but not advancing its train schedule.

[kovarex]

I wasn't sure whether it is a feature or a bug, but after reading through, the decision is to revert it to the 0.16 behaviour:

- Disabling station with train waiting in it doesn't force the train to departure anymore so it works as it worked in 0.16.
It looked like a useful change for 0.17, but we can control train conditions by circuit network and there are some
nice and simple usecases were ruined by trains being forced to departure when the stop is disabled. (65109)

So fixed for 0.17.9

[knightelite]

Awesome, thank you!

[barbary]

I wasn't sure whether it is a feature or a bug, but after reading through, the decision is to revert it to the 0.16 behaviour:

- Disabling station with train waiting in it doesn't force the train to departure anymore so it works as it worked in 0.16.
It looked like a useful change for 0.17, but we can control train conditions by circuit network and there are some
nice and simple usecases were ruined by trains being forced to departure when the stop is disabled. (65109)

So fixed for 0.17.9

Thank you muchly, Probably the last bug stopping me playing 0.17.

[IV]

I wasn't sure whether it is a feature or a bug, but after reading through, the decision is to revert it to the 0.16 behaviour:

- Disabling station with train waiting in it doesn't force the train to departure anymore so it works as it worked in 0.16.
It looked like a useful change for 0.17, but we can control train conditions by circuit network and there are some
nice and simple usecases were ruined by trains being forced to departure when the stop is disabled. (65109)

So fixed for 0.17.9

I'm a bit sad that this bug/feature had to go. It was the only way to make a train leave without moving forward through the schedule. This allowed for trains to unload partially at several 'unload' stations and then move on to a load station. However, I understand the decision to go back to the old behavior.

[Khaylain]

I wasn't sure whether it is a feature or a bug, but after reading through, the decision is to revert it to the 0.16 behaviour:

- Disabling station with train waiting in it doesn't force the train to departure anymore so it works as it worked in 0.16.
It looked like a useful change for 0.17, but we can control train conditions by circuit network and there are some
nice and simple usecases were ruined by trains being forced to departure when the stop is disabled. (65109)

So fixed for 0.17.9

I'm a bit sad that this bug/feature had to go. It was the only way to make a train leave without moving forward through the schedule. This allowed for trains to unload partially at several 'unload' stations and then move on to a load station. However, I understand the decision to go back to the old behavior.

I'll simply leave this here;
https://xkcd.com/1172/