Project P.I.T.T. Turns Rubber Duck Hoarding Into a PC Stress Test

Project P.I.T.T. is built around a simple, deliberately ridiculous corporate assignment: manufacture things, move them through an empty facility, and feed them into a massive hungry pit called the Maw. That premise places it comfortably beside automation games, but developer Froke approaches the genre as a parody. The goal is not merely to build an efficient production line. It is to create a system so efficient, so self-sustaining, that the player eventually has as little to do as possible.

That is a funny idea on its own. It becomes even funnier when the tools designed to create an elegant automated factory are instead used to construct an enormous rubber-duck holding pen capable of bringing a high-end PC to its knees.

In one particularly ambitious experiment, thousands of rubber ducks were manufactured and stored near the Maw before being released together in pursuit of a massive score combo. The plan demonstrated both the gleeful freedom of Project P.I.T.T.'s physics systems and the potential cost of asking them to simulate a small ocean of bouncing plastic birds at once. What began as an optimization strategy became a personal benchmark test, complete with collapsing framerate, screaming PC fans, and motion sickness.

A factory game about becoming unnecessary

Project P.I.T.T. gives players a facility, a selection of products, and an all-consuming central pit that demands an endless stream of goods. The Maw can be fed rubber ducks, cash registers, piñatas, and other intentionally strange inventory. Corporate pressure supplies the broad motivation, while the real challenge comes from figuring out how to move huge numbers of objects into the pit as efficiently as possible.

For useful background on this topic, read White House Pulls 'Build the Wall' Tetris-Style Game After Tetris Company Copyright Warning.

Rather than relying solely on conveyor-belt logic, the game emphasizes physical contraptions. Players can assemble magnetized slopes, fan-driven corridors, and other devices that manipulate objects through momentum and environmental forces. The result is an automation sandbox where every production line can become a Rube Goldberg machine, and a minor mistake can turn a carefully planned route into a pile of loose merchandise ricocheting around the room.

That reliance on physics is central to the joke. The ideal Project P.I.T.T. facility removes the player from the process. If the products are being crafted, routed, and delivered without intervention, then the player has successfully automated their own role away. It is a fitting satirical endpoint for a game about corporate productivity: victory means standing aside while the machinery does everything.

But an automated trickle of products is not necessarily the best possible scoring method. Project P.I.T.T. also uses a combo system that rewards goods fed to the Maw in rapid succession. Bigger bursts mean better multipliers, yet the combo deteriorates more quickly as it grows. Even a highly polished factory will eventually see its streak expire if deliveries are too spread out.

That mechanical wrinkle creates an incentive to reject the sensible approach. Instead of delivering ducks continuously, why not collect an overwhelming quantity of them, then unleash the entire stockpile into the Maw at once?

The rubber-duck warehouse strategy

The setup was straightforward in concept, if increasingly dangerous in practice. The Maw was blocked off from every side, creating a makeshift enclosure where products could accumulate. Rubber ducks were produced in enormous numbers and held in place until the moment arrived to open the barrier and let the whole swarm tumble into the pit.

For a while, the strategy appeared sound. A broom was occasionally needed to push wandering ducks back toward the group, but the stockpile continued to rise. Project P.I.T.T.'s low-poly, PSX-inspired visual presentation also makes it seem like the kind of game that should run comfortably on most modern hardware. During nearly all normal play, performance remained smooth.

The machine running the experiment was far from underpowered: a Ryzen 7 7700X processor, an RTX 4080 graphics card, and 64GB of RAM. Yet graphical detail was never really the issue. Thousands of individual objects packed into a confined space present a different kind of problem. Each duck may need physics calculations, collision checks, and responses to nearby movement. As the number of ducks grew, the facility became less of a factory and more of a simulated disaster zone.

At around 3,000 ducks, warning signs began to appear. PC fans accelerated noticeably, and small performance dips started to interrupt the otherwise smooth experience. By the time the collection reached roughly 5,000 ducks, the game was reportedly operating at around 10 frames per second.

That is the point at which an elaborate score strategy stopped looking clever and started looking medically inadvisable. The slow, stuttering view of thousands of clustered ducks caused video game-induced motion sickness, despite decades of prior gaming without that particular problem. The combination of heavy slowdown, shifting physics objects, and constant visual noise made simply looking at the facility uncomfortable.

Releasing the ducks made everything worse

With performance deteriorating, the obvious answer was to tear down the walls around the Maw and finally cash in the enormous hoard. In a normal factory game, opening the floodgates would be the triumphant conclusion: an avalanche of products, a spectacular combo, and a satisfying jump in the score counter.

Project P.I.T.T. had other ideas.

Deleting the walls disturbed the duck mass and pushed the simulation even harder. Instead of immediately restoring performance by reducing the number of active objects in the room, the initial release created a chaotic cascade. Thousands of ducks began spilling toward the Maw while the game struggled to process the consequences. Navigation through the facility became slow and painful, and the mass descent unfolded at an almost frame-by-frame pace.

Eventually, more ducks entered the pit and the strain began to ease. The pile was gradually removed from the world. But the grand score payoff never materialized at the level hoped for: the combo counter barely reached 1,000 before the opportunity had effectively passed.

After all that setup, all that hardware stress, and all those plastic birds, the result was not a record-breaking display of automation mastery. It was a stalled computer, a painful cleanup process, and an excellent lesson in how physical simulation can turn a joke into a performance nightmare.

Is this a performance problem or player-created chaos?

PC performance discussions often focus on optimization. That makes sense: PC configurations vary enormously, and technical problems can be difficult to diagnose. When a game runs poorly, players have every reason to ask whether its settings, engine, drivers, or underlying code could be better tuned.

But Project P.I.T.T. presents a more unusual scenario. It ran perfectly for the overwhelming majority of play on powerful hardware. The serious slowdown emerged only after the game was intentionally pushed into an extreme condition: several thousand loose, physics-enabled rubber ducks jammed together in a custom-built enclosure.

There is a reasonable argument that sandbox games should account for wild player behavior, particularly when they hand players the tools to create it. Physics sandboxes are, after all, partly about experimentation. If a game encourages people to build absurd contraptions, it should not be surprising when someone decides to test its limits with mountains of objects.

At the same time, there is a practical limit to what developers can anticipate and optimize. No game can flawlessly handle every possible self-inflicted catastrophe. Players have been using open-world and sandbox games to overload physics engines for years, whether by dropping huge piles of items in one place, spawning too many vehicles, or covering a town in thousands of identical objects. One memorable Skyrim stunt involving 5,000 cabbages showed long ago how quickly a harmless object can become computationally expensive when multiplied into a virtual landslide.

Project P.I.T.T. did not instruct anyone to build a duck warehouse beside its central pit. It supplied magnets, fans, walls, a broom, and a steady flow of products. The decision to turn those tools into a high-end GPU stress test belonged to the player.

The best kind of sandbox failure

There is still something appealing about this kind of failure. A rigid automation game might prevent players from creating such a mess in the first place. Project P.I.T.T. apparently allows enough freedom for a workable factory to become an absurd experiment in object accumulation. The resulting crash in performance is not ideal, but it also proves that the game's systems can be pushed in unexpected directions.

That freedom suits a parody of automation perfectly. The sensible worker builds a reliable machine, satisfies the Maw, and makes themselves obsolete. The less sensible worker finds a scoring loophole, manufactures a ridiculous surplus of rubber ducks, creates a physics nightmare, and discovers that capitalism may survive--but the framerate will not.

For most players, the practical takeaway is simple: feed the Maw steadily, keep the facility tidy, and avoid storing thousands of loose objects in one place. For everyone else, Project P.I.T.T. may offer exactly the kind of sandbox where a bad idea can become an unforgettable story. Just keep an eye on the frame counter, and perhaps do not check the cost of a replacement graphics card until after the ducks are gone.