Project P.I.T.T. Panel vs Cushion
Panel vs Cushion: A wall geometry problem and an unstable landing need different observations.
A wall geometry problem and an unstable landing need different observations. The Cushion patch does not promise a universal bounce coefficient.
When to investigate Panel
Use the Panel record to inspect the shape and physical support of the intended path.
Choose by the observed task, not a tool name that merely sounds stronger. Retain the source scope when applying this comparison.
Evidence for this section (2)
OFFICIAL CURRENT · checked 2026-09-26
Officially named surface tool used in production-line planning.
Build relevance: Official store names the tool
Limit: A panel needs Sticky Tools to remain in place under the official demo FAQ guidance.
OFFICIAL HISTORICAL · checked 2026-09-26
Update 1.0.7 says Cushions were made more reliable; it does not publish a physics coefficient or universal layout.
Build relevance: Patch-dated behavior, not an independent replay
Limit: No bounce coefficient or universal layout is claimed.
Sources: Official Steam store page ↗ · Official Steam Update 1.0.7 — 30 August 2026 ↗
When to investigate Cushion
Inspect the Cushion landing candidate when the first contact is the failure; compare the same entry direction and product.
Keep the input and destination constant when comparing the alternative; a different product or target makes the result a different test.
Evidence for this section (2)
OFFICIAL CURRENT · checked 2026-09-26
Officially named surface tool used in production-line planning.
Build relevance: Official store names the tool
Limit: A panel needs Sticky Tools to remain in place under the official demo FAQ guidance.
OFFICIAL HISTORICAL · checked 2026-09-26
Update 1.0.7 says Cushions were made more reliable; it does not publish a physics coefficient or universal layout.
Build relevance: Patch-dated behavior, not an independent replay
Limit: No bounce coefficient or universal layout is claimed.
Sources: Official Steam store page ↗ · Official Steam Update 1.0.7 — 30 August 2026 ↗
Decision record
A wall geometry problem and an unstable landing need different observations. The Cushion patch does not promise a universal bounce coefficient.
| Option | Use case | Not established |
|---|---|---|
| Panel | Use the Panel record to inspect the shape and physical support of the intended path. | Universal optimum / exact throughput |
| Cushion | Inspect the Cushion landing candidate when the first contact is the failure; compare the same entry direction and product. | Universal optimum / exact throughput |
Evidence for this section (2)
OFFICIAL CURRENT · checked 2026-09-26
Officially named surface tool used in production-line planning.
Build relevance: Official store names the tool
Limit: A panel needs Sticky Tools to remain in place under the official demo FAQ guidance.
OFFICIAL HISTORICAL · checked 2026-09-26
Update 1.0.7 says Cushions were made more reliable; it does not publish a physics coefficient or universal layout.
Build relevance: Patch-dated behavior, not an independent replay
Limit: No bounce coefficient or universal layout is claimed.
Sources: Official Steam store page ↗ · Official Steam Update 1.0.7 — 30 August 2026 ↗
Evidence and verification limits
DEFERRED — EVIDENCE INSUFFICIENT. This page documents what is known and what remains unresolved; it is not a verified complete solution.
Evidence for this section (2)
OFFICIAL CURRENT · checked 2026-09-26
Officially named surface tool used in production-line planning.
Build relevance: Official store names the tool
Limit: A panel needs Sticky Tools to remain in place under the official demo FAQ guidance.
OFFICIAL HISTORICAL · checked 2026-09-26
Update 1.0.7 says Cushions were made more reliable; it does not publish a physics coefficient or universal layout.
Build relevance: Patch-dated behavior, not an independent replay
Limit: No bounce coefficient or universal layout is claimed.
Sources: Official Steam store page ↗ · Official Steam Update 1.0.7 — 30 August 2026 ↗
Primary source: Official Steam store page ↗. Scope: full game.
A source-check date is not an in-game test date. Historical fixes and community observations retain their stated scope.