The Asobo team did say at one point they had a fix, and would include it in a future beta update, but we’ve had two updates since then without the fix.
And the most recent info from the team does not look promising:
So promising an update on the status, but no fix.
This is most annoying. If they do not have a fix for saving/loading from the cloud, they should just let us save the settings locally, as has been suggested several times above. This would be quick and easy, with none of the complications inherent in logging in to the cloud.
This really does not bode well for FS2024, which will be even more internet-dependent.
well i suppose they are putting all there efforts into MSFS2024 Then
i dont know why they bother with beta testing (us) ,if they cant fix the bugs and put them in their beta releases in the first place GOD it is sooo annoying
If this Beta is following the pattern of previous betas, we will get the final version within the next few days and this version will be the one that will release as final build in 2 weeks.
So if they dont want to port the issue to the live version and the bug is not caused by the server limitation of the Beta, we should see a solution soon.
This is what I’ve been offering them for a year, I’ve been constantly writing to tech support to make a local save to a file, as it was in P3D, but they stubbornly ignore it. They refer to what they will add to the wish lists, but things are not moving.
Did they actually say this? I skimmed back over the mod posts in this thread and didn’t see a fix being announced. The closest I saw was that a fix is coming, but that it’s still under investigation and not to expect it in the beta updates yet.
Comment 321 is what one can expect to be a confirmation that the fix has been found and only needs to be forked to the published build.
Of course that is not what it says exactly and it can be as well interpreted as just a general assurance that this bug will be fixed.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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 Community Support section.
Brief description of the issue:
Assistance options reset to EASY every time I open MSFS 2020
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Open MSFS and the assistance options have resetted to EASY
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
1.35.18.0
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
On the 2nd November dev blog update they said they identified the cause of the bug:
The dev team has identified the cause of this bug and will resolve it in a future SU_14 beta build.
Obviously this means they know what causes the bug and that’s why some people (me included) thought they would have fixed it by now.
They also said:
The biggest issue we have noted from SU_14 testers so far is a regression that was causing Assistance settings to reset to default whenever launching the sim.
That makes it look like they already had a fix, otherwise they should have said:
The biggest issue we have noted from SU_14 testers so far is a regression that IS causing Assistance settings to reset to default whenever launching the sim.
It’s just strange they say they have a fix but then have put two more beta builds without the fix. Speaking as a software developer, that’s an odd thing to do.
In none of our previous messages about this did we say that we had a fix ready for release to public testers. We said that this bug would be resolved in a future SU14 beta build, and this information is still accurate.
Can I ask why is this fix taking so long? This is fundamentally a very similar issue to bugs in the past so I’m troubled as to why it continues to go unfixed for this period.
Based on your answer, can we say that with each update we will always have a complete mess due to these unforeseen events? I think this is completely out of control and disrespectful to the community IMHO.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template: