Potato Please Guide

Potato Please Guide / Settings & support

Potato Please · Settings & support

Blank objectives or cut-off menus? Identify the display fault

A blank objective, a clipped heading and a frozen opening screen have different documented causes. Match what is on screen before changing your installation.

Empty panels and the Steam warning

Hotfix 1.0.1 added a warning when game data cannot load and menus or objectives are empty. For this case, close the game. Steam Support says to restart the computer, open your Steam Library, right-click Potato Please and choose Properties. Under Installed Files, run Verify integrity of game files and allow it to finish. Launch again and revisit the panel that first appeared blank.

If you reach the game’s Library page instead of the list, the gear at the right opens the same Properties menu. Run verification on Potato Please alone and wait for Steam to complete it. Compare the exact same objective in the same language and save afterward. If the panel is still blank, record the in-game version and whether an unrelated panel (for example the upgrade list) has text. A warning across several panels is much more useful evidence of a data-load problem than a single missing objective label.

Valve’s Steam client screenshot: the Verify integrity button under Installed Files (example game: LOST).
Original source ↗
Valve’s Steam client screenshot: verification in progress (example game: Half-Life: Alyx).
Original source ↗

Text exists but the edge is missing

If you can read only the first half of an upgrade name, take a screenshot that includes the panel edge. The developer corrected both clipped menus on ultrawide screens and long translated objective or upgrade headings. Record your display resolution and chosen language if an updated build still cuts words off. Steam notes that some local configuration files may fail verification normally. Judge the repair by reopening the affected screen.

Change a single display variable for a comparison. Capture the whole affected panel at the original resolution, then try a conventional aspect ratio if your display options permit it. Keep the language unchanged for that pass. If the text fits in the second capture, report the two resolutions; if only a long translated line is clipped at either resolution, send that exact line and the language. Preserve your original display settings so you can restore them after the check.

Player screenshot: a complete objective panel at top left and readable quota line at top right. Use these edges when taking a comparison screenshot; the example includes an endgame objective.
Original source ↗

Black screen before the shift begins

Pressing Escape during the opening black screen could freeze older builds. The developer lists the fix in 1.0.2. Record whether the freeze happens with no input or specifically after Escape. That distinction identifies a startup issue which verifying missing objective text alone cannot diagnose.

On an updated build, let the initial black screen pass without pressing Escape and record whether you reach the main menu. Compare this with the old failure only if it is safe to reproduce. If the program closes completely, note the time, collect Player-prev.log and include the version you last saw. A freeze that only occurs before the main menu and a panel that is blank after the menu loads belong in separate reports.

Sources

Related field notes