Clear the first obstruction you can see
Look along the current for the first place where potatoes stop moving. In the original discussion one player used a bucket to remove loose potatoes at the corner; another suggested checking for a stray unpeeled potato. If you already have the vacuum, it can help collect the spill. Take away the blockage before increasing the incoming load, then watch whether the next batch travels through the bend.
Begin at the peeler's discharge and follow the current in the direction the potatoes move. The original poster identified the outside bend, while the T-junction was still passing output. Stop supplying the line while you clear enough loose stock to expose the corner. Send one peeled potato through; if it stalls alone, examine that corner. If it passes, send a small batch before resuming full production.
Compare water speed before paying for another machine
The developer adjusted water flow in 1.0.2 and increased the speed of the last two channel upgrades. If drums feed a congested bend, adding another drum increases the amount arriving at the same point. Test one small load after clearing it. A free-flowing line should carry the output away without the heap immediately building back up. One player still reported overflow at maximum speed, so check the corner itself as well.
Watch the exit beyond the bend. If a single batch reaches the exit but a continuous supply builds a fresh heap, reduce the arriving batch size while checking channel upgrades. If all batches stop in exactly the same place, remove the first stationary piece. A photograph of loose potatoes around the drums can help recognize a major spill, but cannot establish which outlet caused it.
Separate lost frame rate from lost throughput
In 1.0.2 the studio addressed severe slowdown and crashes tied to a late-game jam. If performance is still poor, note whether the frame-rate drop starts when the bend fills, and whether it survives clearing the floor and channel. In the performance thread the developer asked for PC specs, both logs and the machines or upgrades owned when it began. That information makes a recurring physics issue easier to reproduce.
For a performance report, photograph the obstruction and capture the same area once it is clear. List how many drums you own, your channel upgrade level, and whether frame rate recovered after new arrivals stopped. A hardware list and the logs from the affected session give the developer more to work with than a screenshot taken after restarting an empty room.
Sources
- Player report • Overflow at the water channel bend steamcommunity.com
- Developer support reply • Performance after full automation steamcommunity.com
- Developer notes • Hotfix 1.0.2 steamcommunity.com