Potato Please Guide

Potato Please Guide / Settings & support

Potato Please · Settings & support

How to Read Steam Deck Frame Rates Before a Late Shift

Check what Valve measured on Deck, what the graph says about stutter and how to test an automated Potato Please save on your own handheld.

Open the game-specific compatibility details

Open the Potato Please store page and expand Learn more under Steam Deck Compatibility. Look for the frame-rate row and its chart if Valve has enough samples for this title. The announcement says the data was available on the store and Steam client for everyone by November 11. A PC minimum-spec listing and a player's Deck review provide no substitute for a numerical reading from the panel.

Understand the empty panel before promising a frame rate

Valve requires enough anonymous gameplay samples before it publishes a game's graph. First make sure you opened the detailed panel for the right title. When no number is shown, leave frame rate unknown for this game and test one of your own saves if you already own it. A missing number is neither a zero-FPS result nor a report that the game cannot launch.

Use the distribution to choose a test save

Expand the graph and look at the lower-frame-rate bars as well as the average. They show a proportion of samples arriving at lower rates across players. Valve does not label their location within Potato Please. To check a gantry, run a loaded shift and a quiet one on your own device and compare the same camera turn near the processing room.

Match the frame limit used in Valve's comparison

Valve filters this dataset to devices at their default limit: 60 FPS for LCD Deck and 90 for OLED. If you cap a session at 40 to save power, note that cap with your personal result and do not use it as an equivalent sample of the default-limit average. Check the actual cap on your device before comparing two handheld runs.

Read the display timing before diagnosing a depot hitch

On a 90 Hz OLED, a frame missing one refresh can be presented on the next, giving 45 instead of 90 for that interval. A mixture of the two can average between them even if few individual samples land at the average. Valve uses this as a general example. Read only the bars your title actually displays, then reproduce any felt hitch in your own shift.

Match the hardware and graphics preset before extrapolating

The published Deck chart is built from participating handhelds. Valve does not separate every custom in-game graphics setting in that graph. Compare your laptop's graphics adapter against the Windows store requirements, then test a depot scene at a known preset. A Deck result by itself cannot tell you which Windows preset will hold your target rate.

Measure the scene and progression you actually care about

The histogram aggregates samples from many sessions and excludes idle time. It has no timeline for a particular worker, so an early high average does not predict when three loaded machines will slow down. Keep a manual save before expanding, revisit the same viewpoint after expansion, and record both results with the machine counts.

Late-shift example with three receivers and accumulated sacks
Original source ↗

Change the Steam account's measurement preference

Open Steam Account Settings, Data & Browsing and then Anonymous Game Framerate Data. Review the opt-in setting there. This setting controls sharing performance samples with Valve; to see what happens during your own loaded shift, inspect the local performance display separately. Changing the sharing preference does not change a game graphics preset.

Sources

Related field notes