Quick answer: update past the version that still used a 50 FPS minimum, restart the game after changing the cap, test a 30 FPS baseline, and then isolate VSync, external overlays, resolution, and GPU load one at a time. Do not treat a low measured FPS value as proof that the cap setting itself is broken.
Version boundary
The official 1.0.5 patch note says the minimum locked FPS changed from 50 to 30. That is a change to the allowed cap range, not a promise that every computer will render at 50 or 60 FPS. If an older guide tells you that 50 is the minimum, treat it as version-bound advice.
Cap or performance?
| What you see | Likely category | Test |
|---|---|---|
| FPS never rises above the selected value | Cap or VSync | Change only the in-game cap and repeat the same scene. |
| FPS stays below the selected value | Performance load | Lower resolution or effects and check whether the ceiling moves. |
| FPS changes after opening an overlay | External limiter or overlay | Temporarily disable one overlay or driver cap, then retest. |
| Only co-op drops frames | Session or scene load | Compare the same location solo and in the same host session. |
Safe troubleshooting order
- Record the build. Note the game version, display mode, resolution, selected cap, VSync state, and whether the issue happens solo or in co-op.
- Update and restart. Do not compare a pre-1.0.5 guide with a current build without checking the patch boundary.
- Set a 30 FPS baseline. This tests whether the game accepts the new minimum range before you chase a higher target.
- Change one variable. Test the same scene after changing only the cap, then only VSync, then only resolution or effects.
- Check the external layer. Driver-level caps, overlays, capture tools, and laptop power modes can limit or destabilize results outside the game.
- Report a reproducible case. Include the overlay reading, scene, GPU, resolution, cap, and version instead of only saying “FPS broken.”
Evidence boundary: the 1.0.5 patch establishes the 50-to-30 minimum change. It does not establish a universal FPS fix for every GPU, monitor, driver, or overlay combination.
Related technical checks
Community report
GPU artifacting
Separate game-only visual glitches from driver, overlay, temperature, or display problems.
Open the graphics checklist →Community reportSound duplication
Collect a useful reproduction sequence before changing audio devices or saves.
Open the audio checklist →Official patch boundarySteam News: PATCH 1.0.5 and the minimum locked FPS change.Read the patch note →
Current issue reportsSteam Discussions used for player-reported performance context; reports are not universal fixes.Open discussions →