1 Overflow is a design problem
The store names overflowing conveyors and scattered parts as things that happen as the factory grows. In a physics game those are not cosmetic, because loose parts remain in the world and continue to be simulated.
| Cause | Fix |
|---|---|
| A machine outproducing the next stage | Match rates rather than maximising the first stage |
| A long belt acting as accidental storage | Shorten it. Belts full of waiting parts are the worst kind of storage here |
| A junction that cannot keep up | Split earlier, so pressure never builds at one point |
| Mining faster than you can consume | Throttle the source. Extraction with nowhere to go is pure waste |
2 Protecting the object budget
With the minimum processor supporting roughly 2000 objects at once, capacity is a resource you spend rather than a limit you meet at the end.
3 When the frame rate drops
The requirements table tells you where to look. The graphics requirement is a GTX 950 at minimum, which is very low, while the processor requirement is a Ryzen 5 3600 or an i5-10400.
That means slowdown is almost always the simulation, not the rendering. Lowering graphics settings will do very little. Reducing the number of loose objects will do a great deal.
4 Expand by module, not by sprawl
Twisting mineshafts encourage building wherever there happens to be room, which produces a base nobody can maintain, including you.
| Principle | Why it works here |
|---|---|
| One product per area | When something spills, you know immediately which line failed |
| Repeat a proven layout | A shape that behaves well once will behave well again. Novelty is risk |
| Keep a walkway | You will return to fix this. Access is worth the space it costs |
5 Working with the chaos
The store frames unexpected physics mishaps as part of the entertainment, and asks you to find creative solutions rather than perfect ones. That is a different mindset from the calculating tradition of factory games.
Practically, it means a design that mostly works and recovers gracefully beats a design that is theoretically optimal and fails badly. Build in slack: a little spare capacity absorbs the moments when physics does something you did not plan for.
6 Playing an Early Access sandbox
Two consequences follow from the Early Access tag on a game of this type, and both are worth planning around rather than discovering.
7 Mistakes that cost the most time
| Mistake | Fix |
|---|---|
| Maximising extraction first | Match your mining rate to what the factory can actually consume |
| Using belts as storage | Every waiting item costs simulation. Keep belts moving |
| Lowering graphics to fix slowdown | The load is on the processor. Reduce objects instead |
| Ignoring spilled parts | They stay in the simulation. Clear them |
| Building a huge base before testing one line | Prove a module, then copy it |
Treat overflow as a balance failure rather than an accident, match production rates instead of maximising them, and clear spilled parts because they keep consuming simulation. Spend the object budget wisely by moving fewer items faster and by processing near the source. When performance drops, reduce objects rather than graphics settings, since the minimum graphics requirement is very low while the processor requirement is not. Expand by repeating a proven module with room to walk through it, build in slack against both physics surprises and Early Access balance changes.
Comment
No comments yet. Be the first to post one.