First of all, why don't you throttle the max throughput of a segment by a factor proprotional to it's length? Yes, I proposed the same thing above. This would make the optimisation less apparent. Without this a long segment would allow 'teleporting' fluid over a long distance at zero cost in throug...

@TheYeast : Maybe I'm mistaken, but your model sounds very similar to Factorio's current model ? (Except that you fixed the update order issue, and want to potentially introduce a more complex pressure system / compression of fluids.) It may very well be quite similar. I could not fully deduce what...

Physicist here. I happened to bring up the wonky fluid behaviour about a year ago, but it didn’t seem to be a high priority at the time. Back then I came up with some alternative algorithms and ran some simulations in an Android app I hacked together for this purpose (can send APK+source if interest...

In the real world, belts would beat flying bots because of the insane power required for lifting and carrying heavy loads through the air. Greatly increasing power consumption and factoring in weight would make the belt vs. bot trade-off more fair. Power efficient yet complex design vs. simple desig...

I wondered about that too, but it might just mean that they collect it as a fun usage statistic. Who is going to notice a deleted blueprint, not blame it on their own stupidity, and then go through the trouble of filing a bug report about it? https://forums.factorio.com/50709 And now we know. The a...

This. An algorithm with 64-bit word size will likely be faster than one with 32-bit word size, if only because you only have half as many input words. The size of the output hash (32 bit in this case) is not necessarily related to the word size used during its computation. I'm no expert, but from a...

That's true, but from this line: Lets wait if it happens or not :) it sounded to me like they weren't doing this. I wondered about that too, but it might just mean that they collect it as a fun usage statistic. Who is going to notice a deleted blueprint, not blame it on their own stupidity, and the...

At first I (like some others) thought 9% (or 4.3%) ??? That can’t be right! It is almost certain there will be collisions with these numbers. But the fallacy is assuming that all these 20,000,000 blueprints are in the same pool. They are not. It’s about the change of one player having a collision in...

There are many random things going on on forums but every 100th post has something in it that we can use. So keep it up :) If you think it is worth sifting through the other 99 posts, then I will :) That's exactly how it works :) Before belt segment is updated, belt piece that it leads to is update...

Actually inserting virtual item instead of gap is an interesting idea. It will complicate things though when dropping items, but probably not much. I think I'll try that. Cool, I may have contributed to Factorio development. I would love to hear if this made a difference! Thinking about belt optimi...

ratchetfreak wrote:Are the segments implemented as a circular buffer?

Yup, he said so earlier on this thread

Harkonnen wrote:The new implementation has linear ring-buffer.

viewtopic.php?f=38&t=40790&start=40#p241268

Thank you for the reply Harkonnen! Yes, I figured we both had to do exactly one iteration for removing an item. You to find it, me to migrate items back to range0. I don't see why my iteration is more expensive than yours but I'll take your word for it :) But then again, I assumed that removing an i...

Let me clarify the belt algorithm I posted earlier. Since no one commented I may have failed to explain it clearly. We would like to retain the ability to quickly check a specific region of a belt segment for items. If we can store the position of an item, we can apply a binary search on the item bu...

It sounds like you could add a few "detection regions" [...] This would let circuit detection not influence the segment sizes. I don't know whether others do but I rarely use circuit detection. If my factory uses 10 at a time it is a lot. But even a few hundred extra belt segments due to ...

Like Lilly, I don't see the need to lose the position of items. Consider the following algorithm: Every belt segment gets a belt.shift variable, which is incremented at every tick. Items entering the belt will be assigned the static relative position item.x0 = - belt.shift; At a later time, its posi...