Max Frame Rate cannot be turned off

ISSUE DESCRIPTION

Using SU7 beta 2, I can no longer disable Max Frame Rate option under Settings, General, Graphics.

FREQUENCY OF ISSUE

Always.

REPRODUCTION STEPS

  1. Starting with setting ON

  2. Try to toggle off.

  3. It does toggle from on to off when clicked, but after save and reentering settings, it is still left on.

YOUR SETTINGS

PC, MSFS 2024, RX 9070 XT.

Yes I see this behaviour too. Turn off Max Frame Rate then returning to sim has zero effect and can be confirmed by going back into settings.

I see the same, you can’t disable it if already set via UI - as workaround you can shutdown MSFS2024, set framelimiter to 0 in the UserOpt.cfg file and start again. It will stay unlimited until you touch it in UI…

Can confirm.

I typically have Max Frame Rate set to 30, with Frame Gen x2.

Test 1

  • I turned the FPS overlay on
  • I turned Frame Gen off, to see MSFS native FPS
  • I have Max Frames set to 30
  • I entered a flight (parked)
  • It shows 30 FPS as expected

Test 2

  • I opened Settings and disabled Max Frame Rate …
  • … while still in Settings, the FPS increases as expected
  • … but as soon as I Save & Exit back to the flight, it returns to 30 FPS
  • … and opening Settings again, Max Frames is ON again, so the Setting does not save.
  • … quiting and restarting MSFS does not fix it.

Test 3

  • The above happens even when not in a flight
  • Restarting MSFS, disabling Max Frame Rate, then Save & Exit back to main menu does not save the setting.

Asobo, you have a chronic issue of not being able to save settings reliably.

Can a forum mod, or forum user, confirm this will count as a bug report, waiting to be bug-logged? Is that how it works? Or does it need other kind of reporting to be seen/worked on?

Same issue very annoying as it affects my performance somehow

Hi @Hemish9947
Your post is in the right bug category. Once the bug has been entered into the internal bug-tracking system, the feedback-logged tag will be added. If the test team can repro the issue, that tag will be replaced with bug-logged .

Users can continue to add comments confirming that they can repro the issue (or not, as the case may be), as well as add their vote to the vote tally at the top of the post:
Vote Tally

I can also confirm this.

This topic has now been updated to bug-logged after successful internal reproductions. Please note that we do not provide estimated timelines for bug fixes to be released.

Thanks for helping us to identify this issue by creating a Bug Report.

Bug confirmed.