Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Browser-local calculator · your current info-panel values

Shapez 2 full-belt building count

Read how many selected buildings process one full belt from the in-game info panel, then compare your plan. The example values are placeholders, not a recipe recommendation.

Short by 1 building against your own info-panel rate.

4 buildings implied by these inputs · 75.0% of the planned count

Arithmetic only: it does not read a save, identify a machine, model recipes or prove throughput. Check the live build's info panel and observe the belt.

Use the belt as a boundary marker, not as a diagnosis

The official troubleshooting note recommends watching the Space Belt before and after each platform. If the stream is continuous entering a platform but becomes thinner after it, the responsible constraint is narrowed to that platform. That observation alone does not say whether the cause is input starvation, a machine count, recipe mismatch or an output that is not being collected; inspect the platform itself before rebuilding the whole route.

What you observeNext place to inspectDo not assume
Flow is already thin before a platformEarlier source, splitter or previous platformThat the next platform caused the shortage
Flow enters a platform full and leaves thinnerThat platform's inputs, selected machines and outputsThat one universal machine ratio applies
Flow remains full but the target still stallsTarget port, shape identity and downstream connectionThat throughput is sufficient for every recipe
Only occasional output is wrongTrace the shape from destination toward the first platform where it differsThat the last machine is necessarily the source of the error

References: Official Shapez 2: Troubleshooting your factory

Walk the chain in a repeatable order

Keep one observation per boundary. The practical aim is to find the first transition where the result changes, then inspect that short segment rather than redesigning an entire multi-platform factory.

  1. Choose one destination that is visibly short or stalled and note the exact requested shape or material.
  2. Follow its incoming Space Belt backward one platform at a time; record whether the belt looks full immediately before and after each platform.
  3. At the first platform where flow changes, select each relevant building and read the current info panel's full-belt processing count.
  4. Compare the platform's actual incoming belt layers, machine count and outgoing ports with the shape sequence the destination needs.
  5. After changing one identified fault, observe the same belt boundaries again before making another change. If the shape itself is wrong, continue the backwards trace to the first platform producing the wrong intermediate.

References: Official Shapez 2: Troubleshooting your factory

Count machines from your own rate display

The developer's example method is to use the selected building's info box, which reports how many of that building process a full belt. Different building rates can make a mixed platform harder to reason about. This calculator multiplies a value you read from the current info panel by the number of full belts you plan to process; it does not know which building or recipe is selected.

InputExample valueMeaning
Buildings per full belt4 (illustrative only)The count shown for the selected building in your own current info panel
Full belts planned2How many full input belts your plan intends to process
Buildings installed7Your placed count to compare with the calculated 8
ResultShort by 1Arithmetic discrepancy; still check supply, recipe and observed flow

References: Official Shapez 2: Troubleshooting your factory

Limits and version context

Update 1.2 was announced on August 13, 2026 and includes engine, performance/stability, blueprint migration and mod-support changes. Those broad release notes do not establish a fix for every belt or throughput symptom. Check the installed build and live Codex/info panel if your UI differs; do not treat this dated guide as a benchmark or a claim that GamerWin tested the current factory.

References: Official Shapez 2 Update 1.2 announcement · Shapez 2 player discussions

Before you play

  • I identified the exact output that is short.
  • I compared Space Belt flow before and after each platform.
  • I read the selected building's live full-belt count instead of assuming a fixed ratio.
  • I changed one bounded fault and rechecked the same boundary.

Frequently asked questions

Does a thinner Space Belt prove that the platform has too few machines?

No. It narrows the investigation to that platform; check incoming shapes, building settings, output routing and the building count in its info panel.

Can I use the calculator's default value as a machine ratio?

No. The number is only an example. Read the selected building's current info panel and enter your own value.

Was Update 1.2 tested here for throughput changes?

No. The cited announcement describes broad engine, performance/stability, blueprint and mod updates. No factory or benchmark was tested.

Sources & revision notes

Editorial revision: November 5, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. Official Shapez 2: Troubleshooting your factory (Official)

    Developer-published Steam announcement dated July 9, 2026. Explains using each building's info panel for the count needed to process a full belt, tracing an incorrect shape from output backward, locating a flow change on Space Belts, avoiding mixed shapes on regular belts and using separate Space Belt layers.

  2. Official Shapez 2 Update 1.2 announcement (Official)

    Developer-published Steam announcement dated August 13, 2026. Describes Update 1.2's Unity 6 move, performance/stability improvements, blueprint migration, mod support and other fixes. This guide does not infer a mechanic fix from those broad notes.

  3. Shapez 2 player discussions (Community)

    External, player-run Steam discussion forum. Individual reports may describe different versions, modes or factory layouts; none are copied or treated as a universal diagnosis.

What changed in this revision

November 5, 2026: added a boundary-by-boundary flow diagnosis and a browser-local calculator that uses only player-entered info-panel counts. No save, blueprint, machine ratio or performance result was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.