ValveSoftware/SteamOS

Game performance profiles: TDP options not saved, FPS cap ignored/resets for Steam and non-Steam games

Closed this issue · 5 comments

Alex0007 commented

Your system information

  • Steam client version: 1756942958
  • SteamOS version: 3.7.14
  • Opted into Steam client beta?: Not sure
  • Opted into SteamOS beta?: Yes
  • Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

Expected behavior: Game performance profiles should properly save and apply TDP settings and FPS caps for both Steam and non-Steam games. FPS caps should be respected immediately when set and persist between game restarts.

Actual behavior:

  • TDP options are not being saved in performance profiles
  • FPS caps are being ignored and not saved for manually added games
  • For Steam games: FPS cap displays correctly in the SteamOS UI but the game doesn't respect it after restart until the profile value is manually changed
  • For non-Steam games: FPS cap resets to 90 FPS between game restarts, ignoring the previously set value

This issue affects both Steam and non-Steam games but manifests differently for each. The problem appears to have been introduced in the SteamOS beta branch within the last ~30 days.

Steps for reproducing this issue:

  1. Open Steam Deck settings and navigate to Performance
  2. Create or edit a game performance profile for any game (Steam or non-Steam)
  3. Set a custom TDP limit (e.g., 10W) and FPS cap (e.g., 40 FPS)
  4. Save the profile and restart the game
  5. Observe that the FPS cap is not being applied (game runs at higher FPS than set)
  6. For Steam games: Manually change the FPS cap value in the performance overlay, then the cap starts working
  7. For non-Steam games: Restart the game and observe FPS cap resets to 90 FPS
  8. Check that TDP settings are not being saved by setting profile value and verifying TDP resets to default after restart
kisak-valve commented

Hello @Alex0007, this issue is already being tracked at #2060. Closing as a duplicate.

lostgoat commented

This looks like it might be different than #2060 as it is framerate related. Re-opening and re-checking.

  • 👍1
lostgoat commented

@Alex0007 this should be fixed in today’s client beta update

  • 🚀1
Alex0007 commented

Today's update fixed the issue. Thank you! 🙏

lostgoat commented

Great, thanks for the report.