[0.17.74] Fully compressed belt decompresses
Posted: Thu Nov 14, 2019 6:43 am
I've noticed my fully compressed belts decompressing. It seems to happen at transport line boundaries, as well as on the output of a splitter. Obviously a fully compressed line should not decompress, but I believe the way I'm using the splitter should not result in output gaps (more explanation below).
Video:
https://www.youtube.com/watch?v=bXwDYIvPc-I
Screenshot with annotations
![Image](https://forums.factorio.com/images/ext/e44c321145ac3d16166ead8bf778e09f.png)
Save file (I think it is too big to attach):
https://drive.google.com/file/d/1Z0eKs2 ... sp=sharing
Here are most of the instances of decompression I caught:
0:06 - two decompressions at Splitter
0:19-0:20 - two decompressions at Splitter
0:22 - decompression at 2nd Lane
0:28-0:29 - two decompressions at Splitter, two decompressions at Top Lane
0:37 - decompression at Top Lane
0:39 - decompression at Splitter
0:40 - decompression at 2nd Lane
I've loaded and watched this save file run a few times, and the same events happen every single time, so this seems to be deterministic.
Regarding the lanes decompressing: It seems to happen when the starts back up after a halt, but not always. It also seems to happen at internal transport lane boundaries.
Regarding the splitter - I'm using them to generate fully compressed lanes from a few uncompressed lanes. The splitter in question prioritizes the upper input, but always has a fully compressed belt into the lower input, which acts as a "buffer" when there is nothing in the upper input. The upper output is priority, so as long as the buffer is full, there should never be gaps in the upper output. The lower output is "overflow", when the combined input exceeds one belt's capacity.
The splitter gaps are not dependent on the output halting, but they happen when it's "processing" items from both inputs.
Video:
https://www.youtube.com/watch?v=bXwDYIvPc-I
Screenshot with annotations
![Image](https://forums.factorio.com/images/ext/e44c321145ac3d16166ead8bf778e09f.png)
Save file (I think it is too big to attach):
https://drive.google.com/file/d/1Z0eKs2 ... sp=sharing
Here are most of the instances of decompression I caught:
0:06 - two decompressions at Splitter
0:19-0:20 - two decompressions at Splitter
0:22 - decompression at 2nd Lane
0:28-0:29 - two decompressions at Splitter, two decompressions at Top Lane
0:37 - decompression at Top Lane
0:39 - decompression at Splitter
0:40 - decompression at 2nd Lane
I've loaded and watched this save file run a few times, and the same events happen every single time, so this seems to be deterministic.
Regarding the lanes decompressing: It seems to happen when the starts back up after a halt, but not always. It also seems to happen at internal transport lane boundaries.
Regarding the splitter - I'm using them to generate fully compressed lanes from a few uncompressed lanes. The splitter in question prioritizes the upper input, but always has a fully compressed belt into the lower input, which acts as a "buffer" when there is nothing in the upper input. The upper output is priority, so as long as the buffer is full, there should never be gaps in the upper output. The lower output is "overflow", when the combined input exceeds one belt's capacity.
The splitter gaps are not dependent on the output halting, but they happen when it's "processing" items from both inputs.