The reported starting configuration
| Setting | Waldherz's report | How to use it |
|---|---|---|
| Resolution | 720p | Check that the HUD remains readable. |
| Preset and upscaler | Low, FSR3 | The FSR quality mode was not specified. |
| Frame-rate limit | 45 FPS | A target, not a guaranteed result. |
| Vegetation | One step above Low | Return to Low first if performance suffers. |
| Bloom / spotlight shadows | Enabled | Optional visual preferences to compare separately. |
Steam user Waldherz posted this on October 14 for the released game. Exact build, SteamOS/Proton versions and a measured route were not supplied. The OLED observation is not evidence of a locked 60 FPS throughout the game. [1]
Check the result on your own route
- Record your Deck model, game version and current compatibility setting before changing anything.
- Apply the baseline and drive through vegetation, turn the camera, then cross an area boundary. Use the performance overlay rather than judging a stationary scene.
- If the frame-rate target is not sustained, lower vegetation first and compare the same route. Then compare the optional lighting effects separately.
- If needed, choose a lower frame cap that remains consistent on that route. Keep the original values so you can undo an unhelpful change.
This is a tuning method, not an additional benchmark. It separates a sustained low frame rate from the short area-entry and camera-turn hitches the source described. [1]
Keep Demo reports out of the comparison
The launch announcement explicitly lists Steam Deck support. Older Demo reports describe an earlier build and cannot settle the performance of the released game. Compare the same device, game build and scene when deciding whether an update helped. [2]
Do not compare a short LCD report, an OLED report and a desktop result as if they were one benchmark. Battery duration also depends on brightness, battery state and settings; there is no site-tested battery-life figure here.
If the problem is more than low FPS
Missing terrain is a different symptom from an uneven frame rate. A controller that moves the menu but cannot drive is different again. Use the specific guide for that symptom before changing unrelated graphics settings.
For a reproducible performance problem, send the model, game/OS version, settings, location and whether it was solo or online to Steam bug reports ↗ (opens in a new tab). Include the short route that exposes it.