Project P.I.T.T. Troubleshooting Guide

Every physics sandbox has its breaking points, and Project P.I.T.T. is honest about when you have crossed them. This troubleshooting guide covers the most common problems players hit after the August 19, 2026 launch and the August 22 Update 1.0.5 fixes: crash items, performance drops, stuck objects, Clear Items recovery, and the lag that makes automation feel broken when it is actually just a CPU problem.

Use this page beside Performance Settings for sustained performance tuning and Tips and Secrets for the soft habits that prevent problems before they start.

The Clear Items button: your recovery tool

Update 1.0.5 added a Clear Items button in the pause menu. This is the first thing to try when your facility enters a broken state: objects frozen in geometry, items spawning inside walls, physics pileups that cause stutters or outright crashes.

Clear Items removes loose products from the facility. It does not remove placed panels, tools, or structures. It does not refund currency spent on those items. Think of it as a janitor button, not a reset button.

Use Clear Items when:

• An object spawned inside geometry and cannot be retrieved normally
• Physics simulation is jittering or freezing despite acceptable frame rates elsewhere
• The facility has accumulated too many loose items for your CPU to simulate cleanly
• A crash left the facility in an inconsistent state on reload

If Clear Items does not fix the problem, try reloading the save from a clean point. If the problem persists across reloads, verify your Steam files.

Performance and crash troubleshooting overview

Performance lag: the CPU culprit

Project P.I.T.T. is a physics simulation, not a GPU showcase. The brutalist PSX look is part of the satire and part of the performance budget — fewer polygons means more CPU headroom for rigid body math. When frames drop during heavy automation, the GPU is rarely the culprit.

Before dismantling your factory, try these in order:

1. Turn off the retro effect — the PSX filter adds GPU cost for every object rendered
2. Set graphics to LOW — reduces shadow and lighting calculations
3. Thin the floor — remove loose objects that are bouncing but not feeding The Maw
4. Reduce overlapping magnets — two magnets fighting each other simulate more than they move
5. Fewer simultaneous movers — twelve fans plus twelve pistons plus product streams is a CPU party

If FAST (400 products per minute) is your goal, performance is not a bug — it is a requirement. Thin the simulation until your CPU can keep up with your ambition. See Performance Settings for the full settings walkthrough.

Crash items: when objects break the simulation

Some object placements or spawns can cause the game to become unplayable. This is not a design failure — it is the natural consequence of a physics sandbox with open building. When an object spawns inside geometry or gets wedged in a way that forces constant collision recalculation, the game can crash or stutter badly enough to require recovery.

If a crash item is blocking progress:

1. Open the pause menu
2. Select Clear Items
3. If the problem persists, load a previous save
4. If the problem is in a new save, verify Steam files

Stuck objects: prevention and recovery

A duck stuck under a panel, a box that tipped into a wall, a register that spawned partially inside the floor — these happen. Prevention is better than recovery:

• Leave clearance around panel edges, especially near walls and corners
• Use recovery panels at Maw approach zones so bounced products have a landing shelf
• Test new builds with single products before adding combo streams
• Watch spawn points when new workbenches appear in later phases

Recovery options for stuck objects:

• Clear Items for loose products
• Manual retrieval with grab (F) if the object is accessible
• The golf club or broom for nudging objects that are reachable but not grabbable
• Reload from a previous save if the object blocks a required path

Phase 3 debris: the now-fixed problem

Launch-week Phase 3 included a scripted debris event that dropped immovable rocks onto player automation. This was removed in the first patch after launch. If your old save has wreckage from that event:

1. Update the game to the latest build
2. Use Clear Items to remove loose debris
3. Rebuild any automation the event destroyed
4. Do not expect a second rockfall — the scripted event is gone

See Launch Notes for the full context and Full Walkthrough for how to rebuild after phase shifts.

Steam Deck specific issues

Handheld play hits CPU limits faster than desktop. If your Deck is struggling:

• Play at LOW graphics, no retro effect
• Keep factory density lower than you would on desktop
• Avoid piñata farming on Deck — explosive debris is a frame killer
• Consider playing docked with a cooling stand if handheld frames dip below 30

See Steam Deck for the Verified badge caveats and Performance Settings for the full handheld tuning guide.

Quick reference checklist

• Game crashing: Clear Items → reload save → verify Steam files
• Performance lag: retro off, LOW graphics, thin objects, reduce magnets
• Stuck object: grab, golf club, broom, or Clear Items
• Phase 3 debris: update game, Clear Items, rebuild
• Deck frames: lower density, no retro, docked cooling
• Nothing works: verify Steam files, check Froke’s official patch notes

Keep this page open when experimenting with large builds. Prevention and fast recovery beat rebuilding from scratch.