Description of the issue:
In SU5 (1.7.6.0) some Settings are not being saved correctly.
One example is General > Graphics > Frame Generation
If you set “FSR3”, it actually applies “DLSS”. This was discovered by noticing that Frame Generation was only being applied on 1 of 3 screens (which is the limitation of DLSS).
Users have to go back in to Settings and change Frame Generation several times with trial and error to see if their selected choice (FSR3) “sticks” by observing behaviour.
Users with only 1 screen may THINK they have FSR3, but in fact it is DLSS, and it won’t be as apparent and thus much harder to troubleshoot a problem.
This indicates the Saving and Applying of Settings is not consistent or reliable
If THIS setting is not being saved correctly, what OTHER settings are not being saved correctly and causing issues and confusion?
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every Time
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
You might need multiple screens to see this particular example - establish 2 or 3 screens for MSFS
Set a Frame Cap of 30
Set Frame Generation to FSR3 x2 (targeting 60 FPS)
Load in to a flight, and pan the camera around.
Notice how the main window is smooth at 60 FPS, but the side windows have a consistent “jitter” and are obviously only 30 FPS, with no Frame Generation applied - because the Settings have set “DLSS” instead of “FSR3” for Frame Generation
Go back in to Settings and toggle Frame Generation to DLSS, save
Go back in to Settings and toggle Frame Generation to FSR3 again, and save.
Load back in to the flight, pan camera around, and notice that this time, maybe if you are lucky, FSR3 Frame Generation is now being applied to all 3 screens?
What OTHER settings are not being set / saved correctly? Is there any verification process or error correction?
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
Keyboard, mouse, xbox controller
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC Only] What GPU (Graphics Card) do you use?
RTX 5090
[PC Only] What other relevant PC specs can you share?
9800X3D
I am confirming that even with the above example - setting Frame Gen to FSR3 - this setting does not survive a shutdown and reboot of the PC. Frame Generation has reverted to DLSS upon reboot - even though it still shows as being set to FSR3.
Every time I change the Frame Generation setting in MSFS from NONE to AMD FSR3 and save the changes, the line in the UserCfg.opt file also updates from FrameGeneration NONE to FrameGeneration FSRFG which corresponds to AMD FSR3. So in my case, the changes are being saved correctly…
I’ll check - but it isn’t being retained or applied somehow to the additional monitors (as one example of settings not being saved or applied). Regardless of what the setting says, the behaviour is that FG is either not being applied, or is loading DLSS instead of FSR3, which is clear by the lack of FG on the side monitors. Going in and toggling it to DLSS, saving, toggling back to FSR3, saving again, retains it for the flight… but then when you reboot it’s gone back to either no FG, or DLSS FG, regardless of what settings say.
Edit - yes, can confirm, the “usercfg.opt” file and the Settings > General > Graphics > Frame Generation both indicate “FSR” … And the MAIN window does indeed seem to have Frame Gen enabled,
BUT… the additional windows either have NO FG, or, it is set to DLSS (which only works on the main window). In order to get Frame Gen working on the additional windows, users must toggle Frame Gen to another setting (OFF, or DLSS), then save, then toggle back to FSR3, save, and return to flight.
One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue: After changing settings within Microsoft Flight Simulator 2024, the changes do not appear to save. When MSFS 2024 is closed and restarted, the settings revert to their default values.
Expected Result:
Settings changes should persist between sessions and remain applied after restarting the simulator.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Everytime
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Launch Microsoft Flight Simulator 2024.
Navigate to Options → General / Graphics / Controls (or any settings page).
Modify one or more settings (e.g., graphics quality, key bindings, controls).
Save and apply the changes.
Close MSFS 2024 completely.
Relaunch MSFS 2024.
Observe that the settings have reverted to default.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
[PC Only] Are you using Developer Mode or have you made any changes to it?
[PC Only] What GPU (Graphics Card) do you use?
[PC Only] What other relevant PC specs can you share?
MEDIA
Please add a screenshot or video of the issue occurring.
Found the same yesterday but happened two times only, on my end seemingly only after the second build of SU5 beta: DLSS settings are not saved, starting “balanced” all the time despite I set and save “quality”. Also, LODs are not saving (anymore). just started 2024 and now my previous settings were kept. one of these mysteries…
No, I am trying to point out that in SU5 there is a PATTERN of similar issues, all related to Settings not being saved, read or applied correctly. That is the issue I’m reporting. It’s not always apparent, and is either a root cause or significant contributing factor for various bugs being reported. Yes, the FSR3 Frame Gen not being applied to multi-window set ups is 1 example, but there are others. This is why I am attempting to report it as it’s own item (as we are instructed to do…)
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Is anybody still experiencing this issue? Our Testing Team were unable to reproduce this internally, and there has been no new comments recently. We’d love to hear if this has been resolved for you all now!
Which one of the referenced issues did you try to replicate? This thread is showing a pattern where settings are not saved or applied correctly, across many different specific settings. Did you check all of them?
The one that affects me the most is FSR3 Frame Generation not being applied to multiple monitors (which is a regression, this worked all the way up to SU4, and was broken in SU5).
I can confirm that the Visual Effects Particles Quality (VEPQ) is still resetting to Low on Xbox every new session.
Steps:
On Settings/General/Graphics set the VEPQ to HIGH (Only options are LOW/HIGH)
Exit Settings
On Xbox Home Screen quit MSFS 2024
Restart MSFS 2024
Check Setting/General/Graphics VEPQ and it’s reset to LOW
Hope this helps.
Also Landmark Markers etc. are mentioned in this thread.
Observed Issues
Landmark Markers in close proximity stay visible even when Visual Assistance are toggled off. Some markers in the distance do disappear although in the opposite sense. When Airport and City/Town markers toggle OFF the Landmark Markers toggle ON.
Airport and City/Town markers toggle ok but using Visual Assistance ON/OFF operate in the opposite sense. Note that the distant markers mentioned in “1” do work in the correct sense.
There is no key bind available to control Nautical Traffic markers. Please don’t combine it with Air Traffic again, it needs its own key bind to allow only one or the other type of marker to be displayed at a time.
This is a separate issue, which has already been bug logged as per the forum thread which you are active in. If we could try to keep comments and reports about particular issues to their relevant threads, that would be really helpful. Thanks for understanding!
