Page 1 of 1

[0.13.3] [kovarex] Two-length trains end sometimes not unloadable

Posted: Sun Jul 03, 2016 7:45 am
by PKing Zombie Spy
In 0.13 we had the absolutely lovely enhancement that cargo wagons were unloadable in six positions per side. This normally works great, but for reasons I find difficult to comprehend, my two length trains will sometimes not be "unloadable" from the sixth position of the second car.

On the other hand, if I "touch" the train in some ways, it will "fix" itself. See this animation of a train with this problem: observe the following:
  • I have a cargo wagon with coal,
  • I have only one inserter arm unloading the wagon into a chest at the offending position,
  • This insert is not working
  • I place a third wagon,
  • The second wagon magically starts to be unloaded again.
Image

I could not find a reliable bullet proof repro -- it appears to be something that happens "sometimes." Because this event happening is somewhat unpredictable, please see this link to a save game file. The player character is near the two trains exhibiting this behavior (the coal and stone train). The only thing unusual about these trains I can see is that it has only one stop (the "unload" station), since the resource patch it was transporting material for had the resource exhausted.

Re: [0.13.3] Two-length trains end sometimes not unloadable

Posted: Sun Jul 03, 2016 1:47 pm
by Klonan
Thanks for the report,

I can confirm the behaviour, its seems to only be on horizontal stations and the north inserter, all my others are fine, and it only seems to happen every so often

Re: [0.13.3] Two-length trains end sometimes not unloadable

Posted: Sun Jul 03, 2016 11:01 pm
by Unic
Hi, this is increbible off topic, but how do you create this animated gifs ?

Re: [0.13.3] Two-length trains end sometimes not unloadable

Posted: Mon Jul 04, 2016 7:55 am
by siggboy
LICECap is great for making animated GIF from game footage.

Re: [0.13.3] [kovarex] Two-length trains end sometimes not unloadable

Posted: Mon Jul 04, 2016 11:09 am
by kovarex
Thanks for the report, it is fixed for 0.13.5 now.