When having a chest with one input belt and multiple output belts, the inserters have different behavior whether they are placed on chunk border or not.
In the picture below, both configs are identical but.
Left : All goods are placed on the belt below the chest.
Right : Goods are spread across below and right belt.
Identical inconsistencies occur when placed near vertical chunk boundaries.
Attached a save file which uses only creative mod 0.0.32 which sows the issue.
[0.16.51] Inserter/chest behave different on chunk border
[0.16.51] Inserter/chest behave different on chunk border
- Attachments
-
- inserter.zip
- (2.45 MiB) Downloaded 111 times
Re: [0.16.51] Inserter/chest behave different on chunk border
Thanks for the report however this isn't going to be changed. This is a side effect of updating entities per-chunk and last time I asked about removing that I was told it wasn't going to happen.
If you want to get ahold of me I'm almost always on Discord.
Re: [0.16.51] Inserter/chest behave different on chunk border
That is a strange reasoning about this issue : Because it is due to the technical implementation it will not be solved.
The focus should be on functionality, not on internals.
The result of it is an inconsistent behaviour of the game -> Same components not working identical together.
I myself have a technical background in IT and did already private modding so understand something on internals and SW implementations.
Took me quite some time to understand what was happening when I noticed this in my game.
For the "normal player" it will be unexplainable, he/she isn't even aware of chunks.
With this issue existing, a one row shift of components can mean working/not working of solutions.
When this happens when placing blueprints, it it even more hidden.
Hope you will revise your opinion on this issue.
The focus should be on functionality, not on internals.
The result of it is an inconsistent behaviour of the game -> Same components not working identical together.
I myself have a technical background in IT and did already private modding so understand something on internals and SW implementations.
Took me quite some time to understand what was happening when I noticed this in my game.
For the "normal player" it will be unexplainable, he/she isn't even aware of chunks.
With this issue existing, a one row shift of components can mean working/not working of solutions.
When this happens when placing blueprints, it it even more hidden.
Hope you will revise your opinion on this issue.
Re: [0.16.51] Inserter/chest behave different on chunk border
has this something to do with sometimes inserters picking out of assemblers differently as well? that would explain alot - this was always bugging me when i wanted to spread the output of an assembler evenly- sometimes it works sometimes they prefer this chest or that etc its frustrating
Re: [0.16.51] Inserter/chest behave different on chunk border
@dog80
Did a quick check and yes, these issues can also occur with assemblers.
The one in the left is only outputting to left and bottom belts.
The one on the right is outputting on all three belts.
The left one is on a chunk crossing.
Did a quick check and yes, these issues can also occur with assemblers.
The one in the left is only outputting to left and bottom belts.
The one on the right is outputting on all three belts.
The left one is on a chunk crossing.
Re: [0.16.51] Inserter/chest behave different on chunk border
That sounds to me like what is commonly known as a “design flaw” ... you expect certain behavior, the game tells you to expect that certain behavior, but then sometimes it works that way and sometimes, if its on a chunk border, it doesn’t?
“Side effect” is putting it politely.
Re: [0.16.51] Inserter/chest behave different on chunk border
The game does not ever tell you that a specific inserter will be the one that grabs or inserts items next. The fact that the ordering is different between all-on-one-chunk vs not doesn't matter.astroshak wrote: ↑Wed Oct 31, 2018 8:59 pmThat sounds to me like what is commonly known as a “design flaw” ... you expect certain behavior, the game tells you to expect that certain behavior, but then sometimes it works that way and sometimes, if its on a chunk border, it doesn’t?
“Side effect” is putting it politely.
If you want to get ahold of me I'm almost always on Discord.