TECHNICAL / PERFORMANCE

How to Fish FPS limit not working

First separate a frame cap from a performance problem. A game can respect a 30 FPS minimum cap while still failing to reach a higher target because of GPU load, VSync, resolution, or an external limiter.

Official version note1.0.5 changed minimum locked FPSChecked 25 Aug 2026
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 seeLikely categoryTest
FPS never rises above the selected valueCap or VSyncChange only the in-game cap and repeat the same scene.
FPS stays below the selected valuePerformance loadLower resolution or effects and check whether the ceiling moves.
FPS changes after opening an overlayExternal limiter or overlayTemporarily disable one overlay or driver cap, then retest.
Only co-op drops framesSession or scene loadCompare the same location solo and in the same host session.

Safe troubleshooting order

  1. Record the build. Note the game version, display mode, resolution, selected cap, VSync state, and whether the issue happens solo or in co-op.
  2. Update and restart. Do not compare a pre-1.0.5 guide with a current build without checking the patch boundary.
  3. Set a 30 FPS baseline. This tests whether the game accepts the new minimum range before you chase a higher target.
  4. Change one variable. Test the same scene after changing only the cap, then only VSync, then only resolution or effects.
  5. Check the external layer. Driver-level caps, overlays, capture tools, and laptop power modes can limit or destabilize results outside the game.
  6. 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.
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 →