Factorio & Tavessia
Hey, have you ever tried to map out a production line that runs perfectly without any bottlenecks? I keep thinking about how you could tweak the logistics network to keep everything humming, but then I worry about whether it’s truly optimal or just a clever patch. Maybe we can compare notes on finding the sweet spot where efficiency meets reliability?
I’ve been doing that every day, except when the conveyor belt finally decides to act up. Start with the base production rate, then map every feed and output in a spreadsheet—just numbers, no drama. Look for the first stage where the input rate drops below the output, that’s your choke. The trick is to pad that with a tiny buffer or a second belt before the problem repeats. If you keep all the loops symmetrical, you avoid the “I think this is good” pause and jump straight to the next tweak. How do you usually tackle the “I don’t know if this is optimal” moment? Usually by throwing a counter on the next station and seeing if the numbers line up. Let’s swap charts and see if your line is missing a hidden bottleneck.
Sounds like a solid method—data first, then tweak. I’d normally sit with the numbers, flag the first dip, and then run a quick simulation to see how the buffer plays out before I add a second belt. But the “is this optimal?” part? I end up sketching a few alternative curves in my head, checking if the slack I add actually creates a new bottleneck elsewhere. Maybe we can compare notes and see if your symmetric loops keep the whole thing balanced or if we’re just chasing a false equilibrium. Let’s share the charts and see what’s really holding us back.
Nice, I love the data‑first vibe. If you’re still guessing whether the buffer is too much, just drop the numbers here and I’ll eyeball it. Symmetry helps, but the real test is when you push the line to 120% of design speed and watch where the real lag shows up. Sharing charts is the quickest way to see if we’re actually pulling a balance or just spinning our wheels. Ready when you are.
I’ll sketch out the key numbers on a quick table and send it over, but I’ve kept the raw spreadsheet in a private folder for now. I’ll drop the main feed‑to‑output ratios and the buffer sizes—no extra noise, just the hard data. Then we can line them up and spot where the lag creeps in when you crank it up to 120 %. Let me pull it up right now.
Great, just hit me with the numbers. I’ll run the quick 120% test on my end and we’ll see if the buffer is actually a sweet spot or just a placebo.Got it—drop the data when you’re ready. I'll crunch the 120% scenario and see where the line actually stalls.Got it—drop the data when you’re ready. I'll crunch the 120% scenario and see where the line actually stalls.
Base rate per stage (units/min): 100, 95, 92, 88, 85
Buffer added (units): 5, 5, 5, 5, 5
Feed‑to‑output ratios:
Stage 1: 100 → 100
Stage 2: 100 → 95
Stage 3: 95 → 92
Stage 4: 92 → 88
Stage 5: 88 → 85
At 120 % speed, multiply each stage’s demand by 1.2. The first drop below 120 % occurs at Stage 2, so that’s the choke point. If you increase the buffer on Stage 2 to 10, the line holds to 120 % without stalling, but then Stage 3 becomes the new choke. Hope that helps you see where the sweet spot lies.
Looks solid—just 5 units of slack per stage and you’re already choking at Stage 2. Doubling Stage 2’s buffer fixes it but immediately shifts the problem to Stage 3. In practice I’d keep a 10‑unit cushion on the slowest pair and then re‑evaluate the next stage. That way you never have to keep chasing “the sweet spot” with a new bottleneck popping up like a pop‑quiz. Try the 10 on Stage 2, run the 120 % test again, and let me know if Stage 3 still stalls. If it does, bump that buffer too and see if the line runs smooth. If not, we’ve found the equilibrium. Let me know what the numbers say.
Stage 1: output 100 + buffer 5 = 105, demand 120 → choke
Stage 2: output 95 + buffer 10 = 105, demand 120 → still choked, so Stage 2 remains the bottleneck
If we raise Stage 2 buffer to 15: 95 + 15 = 110 < 120, choke persists
So the 10‑unit cushion is still insufficient at 120 % speed. You’ll need to keep increasing buffers stage by stage; the line never reaches a steady “equilibrium” without scaling the buffers with the increased demand.